aybassiouny

4 ms·

1.
by aybassiouny 2y ago
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. Me and my kids can co-exist. I just need to let go of contro
2.
by aybassiouny 4y ago
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. In my uninformed opinion: 1. waiting for 1 second sounds
3.
Livesite by a Thousand Spikes(mahdytech.com)
4 points by aybassiouny 4y ago|2 comments
4.
Profiling Processor Cache Misses with VTune(mahdytech.com)
3 points by aybassiouny 7y ago|0 comments
5.
When Lower Load Triggers Higher Latencies(mahdytech.com)
6 points by aybassiouny 7y ago|0 comments
6.
UMDH: Catching Slow Leaks Red-Handed(mahdytech.com)
4 points by aybassiouny 8y ago|0 comments
7.
Using Async Correctly Increased Throughput by 4X(mahdytech.com)
2 points by aybassiouny 8y ago|0 comments
8.
Not All Async Is Equal: How Using Async Correctly Increased Throughput by 4X(mahdytech.com)
2 points by aybassiouny 8y ago|0 comments
9.
Wielding Debug Builds Against Heap Corruption(mahdytech.com)
2 points by aybassiouny 8y ago|0 comments
10.
Spawning Your First C++ Fleet with Service Fabric and REST SDK(mahdytech.com)
2 points by aybassiouny 8y ago|0 comments
11.
by aybassiouny 8y ago
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. Maybe try some of the tools suggested here https:/&#
12.
by aybassiouny 8y ago
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 physical memory later.
13.
by aybassiouny 8y ago
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 swapping has been a heated discussion, and I am on the
14.
by aybassiouny 8y ago
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.
15.
The Curious Case of the 99.9% Latency Hike(mahdytech.com)
3 points by aybassiouny 8y ago|0 comments
16.
by aybassiouny 8y ago
Totally :) If I had a dime for every one who mixed working set and private bytes because of using Task Manager
17.
by aybassiouny 8y ago
Thanks for the mirror! It should be back up now.
18.
Do Not Use Task Manager for Memory Info(mahdytech.com)
123 points by aybassiouny 8y ago|36 comments