这是indexloc提供的服务，不要输入任何密码
Skip to content

Revert "feat: added pressure metrics section" #5159

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
merged 1 commit into from
Oct 31, 2025
Merged

Revert "feat: added pressure metrics section" #5159

Show file tree
Hide file tree
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
28 changes: 0 additions & 28 deletions sites/platform/src/increase-observability/metrics/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,34 +90,6 @@ and whether a given measurement is normal, something that occurs occasionally, o

To see data over a given time frame, use the date picker to select the range to display.

## Pressure metrics

CPU pressure is available in your metrics dashboard alongside existing resource metrics such as CPU, memory, and disk usage. This metric helps you spot hidden performance bottlenecks, especially in shared environments where multiple containers compete for resources.

### What is Pressure?

Pressure indicates the percentage of time your app’s tasks were delayed due to resource contention. This means they needed CPU, memory, or disk access but had to wait because those resources were fully occupied. For example, 6.8% pressure means that tasks were blocked from making progress for 6.8% of that period of time.

### How to understand Pressure

**High pressure** indicates performance bottlenecks, which means that your app's tasks are frequently waiting for access to resources, even if overall usage appears normal.

**Low pressure with high resource usage** typically means your app is making efficient use of its allocated resources. It's fully utilizing them without significant delays.

#### Understanding the values

- **0% pressure:** No contention - tasks had immediate access to resources.
- **0–100% pressure:** During each second of measurement, the application experienced contention for that percentage of time.
- **>100% pressure:** The app is consistently demanding more resources than are available.

For example, 200% CPU pressure with one CPU already at 100% utilization suggests the app would need roughly three CPUs in total to eliminate contention.

{{< note theme="info" title="Pressure below 100%">}}

Pressure below 100%, especially when it fluctuates, does not cause noticeable performance issues.

{{< /note >}}

## Deployments

Sometimes deployment activities (pushes, merges, syncs) can influence the underlying infrastructure.
Expand Down
28 changes: 0 additions & 28 deletions sites/upsun/src/increase-observability/metrics/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,34 +57,6 @@ You can access historical data for up to 30 days. These data should help you und

To see data over a given time frame, use the date picker to select the range to display.

## Pressure metrics

CPU pressure is available in your metrics dashboard alongside existing resource metrics such as CPU, memory, and disk usage. This metric helps you spot hidden performance bottlenecks, especially in shared environments where multiple containers compete for resources.

### What is Pressure?

Pressure indicates the percentage of time your app’s tasks were delayed due to resource contention. This means they needed CPU, memory, or disk access but had to wait because those resources were fully occupied. For example, 6.8% pressure means that tasks were blocked from making progress for 6.8% of that period of time.

### How to understand Pressure

**High pressure** indicates performance bottlenecks, which means that your app's tasks are frequently waiting for access to resources, even if overall usage appears normal.

**Low pressure with high resource usage** typically means your app is making efficient use of its allocated resources. It's fully utilizing them without significant delays.

#### Understanding the values

- **0% pressure:** No contention - tasks had immediate access to resources.
- **0–100% pressure:** During each second of measurement, the application experienced contention for that percentage of time.
- **>100% pressure:** The app is consistently demanding more resources than are available.

For example, 200% CPU pressure with one CPU already at 100% utilization suggests the app would need roughly three CPUs in total to eliminate contention.

{{< note theme="info" title="Pressure below 100%">}}

Pressure below 100%, especially when it fluctuates, does not cause noticeable performance issues.

{{< /note >}}

## Deployments

Sometimes deployment activities (pushes, merges, syncs) can influence the underlying infrastructure.
Expand Down
Loading