> where lowest latency is needed Not so sure it would even be "the lowest", rather than "low enough, stable and predictable", even if it's higher on average than optimal. For example, comparing a hashtable lookup to a…
Another analogy that comes to mind would be 'going to gym'. Short-term, working out is exactly a heat loss (doing hard work with no useful results). But long-term, it makes you healthier and able to do more things. Back…
> Therefore, under memory pressure (especially if you set swappiness to zero), you will be preferentially swapping out your program code (because it is always clean) in preference to your program data. Regarding systems…
> where lowest latency is needed Not so sure it would even be "the lowest", rather than "low enough, stable and predictable", even if it's higher on average than optimal. For example, comparing a hashtable lookup to a…
Another analogy that comes to mind would be 'going to gym'. Short-term, working out is exactly a heat loss (doing hard work with no useful results). But long-term, it makes you healthier and able to do more things. Back…
> Therefore, under memory pressure (especially if you set swappiness to zero), you will be preferentially swapping out your program code (because it is always clean) in preference to your program data. Regarding systems…