|
On 2020-11-22 2:28 p.m., Ben Hutchings
wrote:
On Sun, 2020-11-22 at 13:45 -0800, Flavio Veloso Soares wrote:[Resending: just noticed that the reply I sent on Oct 23 didn't include b.d.o] I don't think the article is about the same thing we're talking here. CONFIG_PREEMPT* options control the compromise between latency and throughput of *system calls* and *scheduling of CPU cycles spent in kernel mode*, not network traffic.The latency of requests to services on a server is affected by both scheduler and network latency. [...] "Services" is a too broad term. Which kind of service are you talking about? For the record, I'm talking about latency of kernel system calls specifically, which happens to be what CONFIG_PREEMPT* controls.
Unfortunately, I couldn't find many comprehensive benchmarks of kernel CONFIG_PREEMPT* options. The one at https://www.codeblueprint.co.uk/2019/12/23/linux-preemption-latency-throughput.html seems to be very thorough,[...] Not particularly. I'm used to latency benchmarks showing e.g. average, 90th percentile, 99th percentile, as well as worst. Ben. Are those benchmarks public? Can you provide links to them?
-- FVS |