Canceled after

Lladybluenotes
View latest

fix: isolate route HMR ownership and await hydration in tests

8277134fd67Open 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
42.94% / 343.14% (over capacity) of 200%
1.15 GB / 6.01 GB of 7 GB

Workers

Showing 16 of 16 workers

Worker 0linux-medium-js2 vCPU 7 GB
3.55% / 312.11% (over capacity)
1.16 GB / 4.69 GB
Worker 1linux-medium-js2 vCPU 7 GB
41.26% / 332.67% (over capacity)
1.11 GB / 4.97 GB
Worker 2linux-medium-js2 vCPU 7 GB
41.18% / 343.14% (over capacity)
1.16 GB / 5.23 GB
Worker 3linux-medium-js2 vCPU 7 GB
45.81% / 338.6% (over capacity)
1.18 GB / 4.76 GB
Worker 4linux-medium-js2 vCPU 7 GB
43.95% / 342.01% (over capacity)
1.06 GB / 4.71 GB
Worker 5linux-medium-js2 vCPU 7 GB
48.71% / 330.77% (over capacity)
1.15 GB / 5.26 GB
Worker 6linux-medium-js2 vCPU 7 GB
64.23% / 337.24% (over capacity)
1.26 GB / 5.24 GB
Worker 7linux-medium-js2 vCPU 7 GB
38.33% / 320% (over capacity)
1.21 GB / 5.12 GB
Worker 8linux-medium-js2 vCPU 7 GB
34.33% / 311.68% (over capacity)
1.1 GB / 5.27 GB
Worker 9linux-medium-js2 vCPU 7 GB
46.78% / 321.95% (over capacity)
1.08 GB / 3.21 GB

Page 1 of 2