Succeeded in NBNicolas Beaussart
View latest

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
69.06% / 360.78% (over capacity) of 200%
1.57 GB / 5.4 GB of 7 GB

Workers

Showing 16 of 16 workers

Worker 0linux-medium-js2 vCPU 7 GB
50.59% / 331.71% (over capacity)
1.39 GB / 4.67 GB
Worker 1linux-medium-js2 vCPU 7 GB
57.78% / 330.9% (over capacity)
1.44 GB / 3.83 GB
Worker 2linux-medium-js2 vCPU 7 GB
61.29% / 312.54% (over capacity)
1.43 GB / 3.72 GB
Worker 3linux-medium-js2 vCPU 7 GB
54.13% / 321.97% (over capacity)
1.37 GB / 3.22 GB
Worker 4linux-medium-js2 vCPU 7 GB
102.68% / 327.09% (over capacity)
1.71 GB / 5.26 GB
Worker 5linux-medium-js2 vCPU 7 GB
90.78% / 346.24% (over capacity)
1.83 GB / 3.36 GB
Worker 6linux-medium-js2 vCPU 7 GB
63.07% / 314.34% (over capacity)
1.41 GB / 5.13 GB
Worker 7linux-medium-js2 vCPU 7 GB
63.76% / 351.12% (over capacity)
1.75 GB / 4.93 GB
Worker 8linux-medium-js2 vCPU 7 GB
61.29% / 360.78% (over capacity)
1.3 GB / 3.62 GB
Worker 9linux-medium-js2 vCPU 7 GB
72.26% / 312.68% (over capacity)
1.64 GB / 3.88 GB

Page 1 of 2