I’m so glad I came across this thread because I’ve been pulling out my hair trying to figure out why I started to see apps break yesterday in my afternoon.
At a high level I think these changes make sense, but I think there’s a critical flaw: Certain apps tend to burst quite a bit at boot due to parsing code (node.js), warming up a VM (node.js/v8,java, etc), and with this change I’m seeing a nodejs app taking 10-20 minutes before it’s useable where previously it took maybe 20-30 seconds, just because the startup sequence is throttled so aggressively out of the gate.
Is it possible to either bless apps with a CPU burst balance right away, or at least honor the balance at a machine level so that a new deployment can come up quickly without starting from a burst balance of 0?
It feels like an anti-pattern to over-provision an app just so it can boot up properly where otherwise the running cpu utilization would fit in a 1x cpu allotment.