Skip to content

Enhance burstable compute description in concepts-compute.md #368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
v-regandowner merged 1 commit into from
May 4, 2026
Merged

Enhance burstable compute description in concepts-compute.md #368

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion articles/postgresql/compute-storage/concepts-compute.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ After you create a server for the compute tier, you can change the number of vCo
You can select compute resources based on the tier, vCores, and memory size. vCores represent the logical CPU of the underlying hardware.

> [!IMPORTANT]
> Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable.
> Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable. This tier is primarily designed for nonproduction scenarios such as development, staging, or testing, does not qualify for 24/7 support, and root cause analysis (RCA) may not be provided.
>
> For these workloads, it's recommended to:
> - Monitor **CPU Credits Remaining** in Azure Monitor and set alerts for low credits.
Expand Down