3 ms·
At the cost of tanking performance for the less frequently used code path. Sometimes it is more important to optimize in ways that minimize worst case performan
by adastra22 1y ago
At the cost of tanking performance for the less frequently used code path. Sometimes it is more important to optimize in ways that minimize worst case performance rather than a marginal improvement to typical work loads. This is often the case for distributed systems, e.g. SaaS backends.
- bayindirh 1y agoYou can request things from Kernel, like pinning cores or telling kernel not swap your pages out (see mlockall() / madvise()). The easiest way affecting everything running on the system might not be the best or even the correct way to do things. There's always more than one way to solve a problem. Reading the Full Manual (TM) is important.