Failed after FFlo
View latest

fix(router-core): harden lane loading lifecycle (#7869)

78051f27102Open on GitHub

Resource usage

Average and peak CPU and memory per agent, against its launch template's capacity.

By launch template

  • avg
  • avg → peak
  • over capacity
  • capacity
Launch templateAgentsCPU (avg / peak)Memory (avg / peak)Filter
linux-medium-js2 vCPU 7 GB1414 over capacity
131.92% / 360.9% (over capacity) of 200%
1.95 GB / 7.72 GB (over capacity) of 7 GB

Agents

Showing 14 of 14 agents

Agent 0linux-medium-js2 vCPU 7 GB
130.38% / 345.41% (over capacity)
2.3 GB / 4.77 GB
Agent 1linux-medium-js2 vCPU 7 GB
117.22% / 315.3% (over capacity)
1.77 GB / 4.93 GB
Agent 2linux-medium-js2 vCPU 7 GB
136.41% / 357.32% (over capacity)
2.01 GB / 5.8 GB
Agent 3linux-medium-js2 vCPU 7 GB
122.99% / 315.97% (over capacity)
1.91 GB / 7.72 GB (over capacity)
Agent 4linux-medium-js2 vCPU 7 GB
145.23% / 335.8% (over capacity)
2.16 GB / 4.63 GB
Agent 5linux-medium-js2 vCPU 7 GB
129.64% / 330.64% (over capacity)
1.97 GB / 5.03 GB
Agent 6linux-medium-js2 vCPU 7 GB
114.82% / 338.96% (over capacity)
2.1 GB / 4.33 GB
Agent 7linux-medium-js2 vCPU 7 GB
121.46% / 340.59% (over capacity)
1.58 GB / 2.88 GB
Agent 8linux-medium-js2 vCPU 7 GB
130.52% / 335.42% (over capacity)
1.77 GB / 4.47 GB
Agent 9linux-medium-js2 vCPU 7 GB
128.42% / 329.41% (over capacity)
1.68 GB / 4.45 GB

Page 1 of 2