Succeeded in

TTkDodo
View latest

fix(query-core): observe streamed fetch cancellation without consuming the signal

124816edae09Open 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 GB55 over capacity
186.09% / 328.37% (over capacity) of 200%
1.81 GB / 5.05 GB of 7 GB

Workers

Showing 5 of 5 workers

Worker 0linux-medium-js2 vCPU 7 GB
195.61% / 328.37% (over capacity)
2.11 GB / 5.05 GB
Worker 1linux-medium-js2 vCPU 7 GB
202.05% / 325.75% (over capacity)
1.88 GB / 4.62 GB
Worker 2linux-medium-js2 vCPU 7 GB
186.88% / 316.13% (over capacity)
1.79 GB / 4.51 GB
Worker 3linux-medium-js2 vCPU 7 GB
141.65% / 317.49% (over capacity)
1.43 GB / 4.38 GB
Worker 4linux-medium-js2 vCPU 7 GB
204.27% / 327.89% (over capacity)
1.81 GB / 4.98 GB