3 ms·
This might be the case for some artificial benchmark, but I have never seen such a case in practice. I have run many, many tests on real-world workloads, not a
by jiggawatts 5y ago
This might be the case for some artificial benchmark, but I have never seen such a case in practice.
I have run many, many tests on real-world workloads, not artificial 100% loads of either a single core or all-cores, as you typically get in benchmarks. In all cases, disabling C-states made overall performance at least 20% better, and often 200% better (3x faster)!
There's lots of reasons for this, and I could write pages and pages on how the jitter introduced by the sleeps is murder on TCP throughput, or how the frequency ramp up time is glacially slow, or how most servers are idle most of the time and only the cold-start latency matters to end-users. Then I could keep ranting about the waste of it all, and go on and on about how Californian greenie hippie morons tried to save the planet one database server at a time. Then finish up by showing that 10 Gbps Ethernet's latencies interact with the core sleep timings just so to make things as bad as possible.
But instead of taking my word for it, you could just do your own tests on your own software, ideally in a production system involving n-tier networking instead of some isolated, synthetic benchmark.
PS: By design, power management has no impact on anything running at 100% load for extended periods, so no synthetic benchmark will ever show any impact. That's precisely why very few people are aware of the issue...
- linuxftw 5y agoCan confirm. I've seen C-states absolutely wreck performance on certain low latency workloads. In particular, lots of small random writes on a storage cluster.
- jiggawatts 5y agoUnfortunately it turns out that "low latency workloads" are not some esoteric thing only high frequency traders care about, but is an accurate description of most enterprise software. Anything n-tier, anything with an API tier or an external cache, anything vaguely K8s-like, or even just a database and a chatty ORM.