Succeeded in NBNicolas Beaussart

fix(ci): avoid reading captured build logs

78330226a7fOpen on GitHub

Resource 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 templateWorkersCPU (avg / peak)Memory (avg / peak)Filter
linux-medium-js2 vCPU 7 GB1616 over capacity
99.22% / 362.04% (over capacity) of 200%
1.85 GB / 5.88 GB of 7 GB

Workers

Showing 16 of 16 workers

Worker 0linux-medium-js2 vCPU 7 GB
121.65% / 320% (over capacity)
1.9 GB / 4.82 GB
Worker 1linux-medium-js2 vCPU 7 GB
88.89% / 313.78% (over capacity)
1.82 GB / 4.71 GB
Worker 2linux-medium-js2 vCPU 7 GB
98.43% / 310.86% (over capacity)
1.86 GB / 4.84 GB
Worker 3linux-medium-js2 vCPU 7 GB
113.7% / 319.33% (over capacity)
1.82 GB / 3.73 GB
Worker 4linux-medium-js2 vCPU 7 GB
99.02% / 313.42% (over capacity)
1.78 GB / 5.05 GB
Worker 5linux-medium-js2 vCPU 7 GB
85.47% / 314.81% (over capacity)
1.52 GB / 4.89 GB
Worker 6linux-medium-js2 vCPU 7 GB
100.04% / 338.69% (over capacity)
1.68 GB / 5.1 GB
Worker 7linux-medium-js2 vCPU 7 GB
101.44% / 314.11% (over capacity)
1.67 GB / 4.32 GB
Worker 8linux-medium-js2 vCPU 7 GB
97.75% / 340.92% (over capacity)
1.58 GB / 3.61 GB
Worker 9linux-medium-js2 vCPU 7 GB
99.14% / 354.75% (over capacity)
2.05 GB / 5.27 GB

Page 1 of 2