I experienced something similar with Clod Run: inexplicable scaling events based on CPU utilization and concurrent requests (the two metrics that regulate scaling according to their docs).
After a lot of back and forth with their (premium) support it turns out there are additional criteria, smthg related to request duration, but of course nobody was able to explain in details.
Often the problem with refactors is that don't come with enough of these new ideas , there's no real progress, it's mostly moving things around.
One of the things that made Rome successful was that they would absorb horrendous losses and still keep going. Their ability to mobilize contributed to their power.
To give an example, at the Battle of Cannae, in a single afternoon, Rome lost an estimated 65,000 men killed. To put this in context, the US lost 58,000 soldiers killed in the entire Vietnam War.
anyone know a similiar tool?
https://www.docker.com/blog/how-to-deploy-on-remote-docker-h...
In practice, as has been pointed out in other comments, they do improve their performance (for competitive reasons) and it does cost them money when they do it.... They did it a couple qtrs ago and left $97 mill on the table.
https://www.fool.com/earnings/call-transcripts/2022/03/02/sn...
I suspect most data warehouses have similar NDRs.
In many companies a data warehouse is the place where you dump all your data and let everyone run poorly written programs against it.
Add to that poor engineering culture in data teams (often lead by non-technical people) and costs are bound to skyrocket.
0: https://en.wikipedia.org/wiki/Willy%E2%80%93Nicky_correspond...
edit: I meant the correspondence between the third cousin, Wilhelm II, and Tsar Nicholas.