Skip to content

Commit 11b866e

Browse files
author
“Kevin”
committed
Make small grammar and style fixes
1 parent a7452fb commit 11b866e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/05-go-client/21-worker-auto-scaling.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ worker.Options{
6868

6969
One of the most common production issues with Cadence workers occurs when compute autoscalers incorrectly scale down worker instances due to low CPU utilization. This creates a deceptive situation where workers appear to be underutilized from a resource perspective, but are actually performing critical work.
7070

71-
Here's what typically happens: Cadence workers spend most of their time polling the Cadence service for tasks. This polling activity is lightweight and doesn't consume significant CPU resources, leading to consistently low CPU usage metrics (often 5-15%). Compute autoscalers like Kubernetes HPA (Horizontal Pod Autoscaler) or cloud provider autoscaling groups see these low CPU numbers and interpret them as a signal that fewer worker instances are needed.
71+
Here's what typically happens: Cadence workers spend most of their time polling the Cadence service for tasks. This polling activity is lightweight and doesn't consume significant CPU resources, leading to consistently low CPU usage metrics (often 5-15%). Compute autoscalers like Kubernetes HPA (Horizontal Pod Autoscaler) or cloud provider autoscaling groups see these low CPU numbers and interpret them as signals that fewer worker instances are needed.
7272

7373
When the autoscaler reduces the number of worker instances, several problems emerge:
7474
- **Reduced polling capacity**: Fewer workers means fewer pollers actively checking for new tasks, which can delay task processing
@@ -160,28 +160,28 @@ Monitor these key metrics to understand AutoScaler performance:
160160

161161
#### Decision Poller Quota
162162
- **Description:** Track decision poller count over time
163-
- **Name:** cadence_concurrency_auto_scaler_poller_quota_bucket
163+
- **Name:** `cadence_concurrency_auto_scaler_poller_quota_bucket`
164164
- **WorkerType:** DecisionWorker
165165
- **Type:** Heatmap
166166
![Decision Poller Quota](img/dash-decision-poller-quota.png)
167167

168168
#### Activity Poller Quota
169169
- **Description:** Track activity poller count over time
170-
- **Name:** cadence-concurrency-auto-scaler.poller-quota
170+
- **Name:** `cadence-concurrency-auto-scaler.poller-quota`
171171
- **WorkerType:** ActivityWorker
172172
- **Type:** Heatmap
173173
![Activity Poller Quota](img/dash-activity-poller-quota.png)
174174

175175
#### Decision Poller Wait Time
176176
- **Description:** Track decision poller wait time over time
177-
- **Name:** cadence-concurrency-auto-scaler.poller-wait-time
177+
- **Name:** `cadence-concurrency-auto-scaler.poller-wait-time`
178178
- **WorkerType:** DecisionWorker
179179
- **Type:** Heatmap
180180
![Decision Poller Wait Time](img/dash-decision-poller-wait-time.png)
181181

182182
#### Activity Poller Wait Time
183183
- **Description:** Track activity poller wait time over time
184-
- **Name:** cadence-concurrency-auto-scaler.poller-wait-time
184+
- **Name:** `cadence-concurrency-auto-scaler.poller-wait-time`
185185
- **WorkerType:** ActivityWorker
186186
- **Type:** Heatmap
187187
![Activity Poller Wait Time](img/dash-activity-poller-wait-time.png)

0 commit comments

Comments
 (0)