Succeeded in

NBNicolas Beaussart
View latest

ci: revert E2E scheduling experiment and refresh baseline

8807f793766Open 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
89.09% / 354.9% (over capacity) of 200%
2.49 GB / 7.09 GB (over capacity) of 7 GB

Workers

Showing 16 of 16 workers

Worker 0linux-medium-js2 vCPU 7 GB
105.82% / 323.68% (over capacity)
2.59 GB / 5.16 GB
Worker 1linux-medium-js2 vCPU 7 GB
93.42% / 331.73% (over capacity)
2.52 GB / 5.83 GB
Worker 2linux-medium-js2 vCPU 7 GB
105.82% / 339.54% (over capacity)
2.61 GB / 5.72 GB
Worker 3linux-medium-js2 vCPU 7 GB
86.45% / 330.41% (over capacity)
2.23 GB / 3.97 GB
Worker 4linux-medium-js2 vCPU 7 GB
90.66% / 354.9% (over capacity)
2.46 GB / 4.79 GB
Worker 5linux-medium-js2 vCPU 7 GB
73.61% / 305.45% (over capacity)
2.79 GB / 7.09 GB (over capacity)
Worker 6linux-medium-js2 vCPU 7 GB
85.44% / 325.28% (over capacity)
2.76 GB / 5.51 GB
Worker 7linux-medium-js2 vCPU 7 GB
86.53% / 325.78% (over capacity)
2.3 GB / 4.96 GB
Worker 8linux-medium-js2 vCPU 7 GB
92.01% / 351.26% (over capacity)
2.47 GB / 4.5 GB
Worker 9linux-medium-js2 vCPU 7 GB
103.04% / 331.73% (over capacity)
2.55 GB / 5.25 GB

Page 1 of 2