Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/best-practices/managing-aps-limits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,7 @@ Use Provisioned capacity when the on-demand model can't respond quickly enough:

:::note
When switching back to on-demand mode, your APS limit resets to the running average from the last 7 days.
If Temporal Support has set a custom limit for your Namespace, that limit is preserved across the switch.
Plan for this if your workload is sensitive to the transition.
:::

Expand Down
6 changes: 5 additions & 1 deletion docs/cloud/capacity-modes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ Actions that are external to the core Temporal service do not contribute to your
## On-Demand Capacity {/* #on-demand-capacity */}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'On-Demand Capacity ***************************' should use sentence-style capitalization.


Using On-Demand Capacity, your rate limit grows automatically along with your usage.
Each Namespace has an Actions per second (APS), Requests per second (RPS), and Operations per second (OPS) limit that scales automatically with usage. Your APS limit never falls below its [default limit](/cloud/limits#actions-per-second).
Each Namespace has an Actions per second (APS), Requests per second (RPS), and Operations per second (OPS) limit that scales automatically with usage. Your APS limit never falls below its [default limit](/cloud/limits#actions-per-second). If Temporal Support has manually set your Namespace's limit, that value becomes your floor in place of the default, and it persists across capacity mode changes.

Scaling automatically adjusts based on the lesser of 4 * APS Average or 2 * APS P90 over the past 7 days.

Expand Down Expand Up @@ -180,6 +180,10 @@ For the metrics to watch and how to alert on utilization, see [Provisioned capac
Capacity Modes and TRUs can be set via the Temporal Cloud UI, CLI, or API.
Capacity modes can be set and adjusted by Global Admin and Namespace Admin.

When you switch to Provisioned Capacity, your limit is set by the number of TRUs you select.
When you switch back to On-Demand, your limit is recalculated from the trailing 7-day usage formula and never falls below your floor.
If Temporal Support has set a custom limit for your Namespace, that limit is your floor, so switching to Provisioned and back to On-Demand preserves it.

### Setting Capacity Modes from the UI

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'Setting Capacity Modes from the UI' should use sentence-style capitalization.


You can set Capacity Modes for an individual Namespace by navigating to the Namespace page in the Temporal Cloud UI (`https://cloud.temporal.io/namespaces/<Namespace ID>`).
Expand Down