3 ms·
It tells us his workload is more network bound than computationally intensive.
by burnte 9y ago
It tells us his workload is more network bound than computationally intensive.
- therealdrag0 9y agoExactly, in my company's SaaS monitoring, I excluded db/external calls, and I saw a 1-2ms increase (on-top of 15ms), so yeah that's a 10% increase, but with external calls make the overall transaction 50+ms, so 1-2ms is trivial. Similarly, the CPU on our Azure cloud box holding a half dozen dockerized Java apps I can't really see went up at all. Hovering around 10% CPU usage before and after patch.
- em3rgent0rdr 9y agoMore specifically, the meltdown patch primarily affect memory bound applications, not necessarily computations, although those usually overlap for CPU bound applications.