4 ms·
The kernel scheduler has no idea which application thread handles which socket. You can formulate an application level plan and then enforce your will with soc
by felixgallo 10y ago
The kernel scheduler has no idea which application thread handles which socket. You can formulate an application level plan and then enforce your will with socket and cpu pinning.
- scott_s 10y agoCorrect, but the difficulty is if your application must share the machine with any other application - even short lived ones. That, I think, is what joosters was alluding to. If the assumption that your application is the only consumer of system resources is broken, then you may see pathological scheduling behavior.
- achamayou 10y agoYou can set isolcpus to earmark some cores for your application, and let the kernel manage the rest.