Succeeded in

SSheraff
View latest

test(router-utils): the lazy handler module counts as an importing output in verify (d)

88171e4ceeaOpen 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 GB1818 over capacity
48.71% / 368.89% (over capacity) of 200%
1.73 GB / 8.52 GB (over capacity) of 7 GB

Workers

Showing 18 of 18 workers

Worker 0linux-medium-js2 vCPU 7 GB
40.21% / 306.31% (over capacity)
1.41 GB / 4.55 GB
Worker 1linux-medium-js2 vCPU 7 GB
46.35% / 316.51% (over capacity)
1.73 GB / 5.21 GB
Worker 2linux-medium-js2 vCPU 7 GB
51.24% / 334.51% (over capacity)
1.58 GB / 6.04 GB
Worker 3linux-medium-js2 vCPU 7 GB
44.62% / 311.5% (over capacity)
1.72 GB / 4.4 GB
Worker 4linux-medium-js2 vCPU 7 GB
43.39% / 357.66% (over capacity)
1.41 GB / 4.86 GB
Worker 5linux-medium-js2 vCPU 7 GB
53.8% / 321.99% (over capacity)
1.71 GB / 8.52 GB (over capacity)
Worker 6linux-medium-js2 vCPU 7 GB
45.61% / 326.65% (over capacity)
1.53 GB / 5.65 GB
Worker 7linux-medium-js2 vCPU 7 GB
40.9% / 318.09% (over capacity)
1.54 GB / 4.72 GB
Worker 8linux-medium-js2 vCPU 7 GB
132.24% / 343.09% (over capacity)
4.99 GB / 7.84 GB (over capacity)
Worker 9linux-medium-js2 vCPU 7 GB
44.89% / 324.1% (over capacity)
1.49 GB / 4.45 GB

Page 1 of 2