> "Directed to reduce" Cloud spending. That feels like it should be 100%. An engineer should be as aware of their $ costs as they are their CPU load, filesystem I/O, or memory usage. An engineer should know how many instances they scaled to, and when they're going to scale down. In fact, the $ cost should be calculable (to a reasonable indicative amount by napkin math - precision not necessary) according to the facto…
In theory most places are running with slack. In practice they run under capacity, and engineers aren't going to worry about things out of their control.