Earlier quoted context omitted.
Yes, you want to do more IPC, its basically linear with the increase in performance. So the amount of overhead stays the same basically. At least in IPC benchmarks and those tend to be important. Making that fast is fundamental to any OS.
So for an I/O heavy program like a web browser, what percentage of CPU time is spent in syscalls? Someone must have that data for Firefox. 1%? 10%? And then that moves to 1.1% (or 11%)? And then every other program is even less affected? Curious if anyone is in the know.
Nginx is IO bound in general - for my headless go stateful server, i could get syscall6 up to 20% of the profile time. It was a fight between GC in the gRPC code allocating for headers and the syscall6 for top single profile footprint.