Viewing profile — aybassiouny

I used to think this is where I am heading, until reading “Hunt, Gather, Parent”, and realizing that being a good parent does not mean my existence as an individual needs to stop. …

It is an internal cache implementation. The library writer _thought_ this codepath would never be triggered - or at least very rarely, but that was proven wrong on the new hardware…

I recommend to do more debugging next time and see which process exactly is costing you all this. It sounds like a classic memory leak - those can be triggered nondeterministically…

The surprising part for me is, OS does not recover. As if once it tanks, it becomes more cautious about which memory is paged and which is not, even if there's plenty of free physi…

Lucy, even in a healthy state, already have many page faults. They are just not on the hot path, e.g. logging. They don't affect latency much and nobody cares for them. Turning off…

That is already tracked, but it is not very meaningful. We already have a lot of page faults (and paged memory), they are just not on the hot path.

Totally :) If I had a dime for every one who mixed working set and private bytes because of using Task Manager

Thanks for the mirror! It should be back up now.