On Fri, May 24, 2019 at 5:07 PM Peter Oskolkov <posk@xxxxxxx> wrote: > Linux CPU scheduling tail latency is a well-known issue and a major > pain point in some workloads: > https://www.google.com/search?q=linux+cpu+scheduling+tail+latency > > Even assuming that nobody noticed this particular cause > of CPU scheduling latencies, it does not mean the problem should be waved > away. At least it should be documented, if at this point it decided that > it is difficult to address it in a meaningful way. And, preferably, a way > to address the issue later on should be discussed and hopefully agreed to. Pursuing reducing tail latencies for our web application is the precise reason I created this patch set. Those applications that previously were responding in 20ms 95% where now taking 220ms. Those were correctly sized applications prior to 512ac999. After which, they started seeing massive increases in their latencies due to hitting throttling with lower than quota amounts of cpu usage. I'll see if I can rework the documentation. Any specific suggestions for how that can be worded would be appreciated.
