Succeeded in
GSGuillaume Da SilvaView latestfix(variables): detect the conflict from the HTTP status and match the variable kind
31417ba6299Open on GitHubResource usage
Average and peak CPU and memory per worker, against its launch template's capacity.
By launch template
- avg
- avg → peak
- over capacity
- capacity
| Launch template | Workers | CPU (avg / peak) | Memory (avg / peak) |
|---|---|---|---|
| linux-medium-js4 vCPU 4 GB | 51 over capacity | 144.69% / 312.8% of 400% | 1.87 GB / 5.2 GB (over capacity) of 4 GB |
Workers
| Worker | CPU (avg / peak) | Memory (avg / peak) | Details |
|---|---|---|---|
156.73% / 293.5% | 2.14 GB / 5.2 GB (over capacity) |
See per-worker resource charts
CPU and memory for every worker and task in your CI runs. Debug out-of-memory crashes and right-size your launch templates.