3 ms·
> a real example: a dev got OOMed after a release that coincided with a flash sale. he increased memory limits, and containers stopped crashing and it was "fixe
by skinfaxi 3mo ago
> a real example: a dev got OOMed after a release that coincided with a flash sale. he increased memory limits, and containers stopped crashing and it was "fixed". Actualy, a newly introduced internal module had a memory leak. adding RAM just hid the leak until the next traffic spike.
Are you saying that hyperprobe would have in fact caught that issue?
- karanraina 3mo agoyes, he'd have to opt in for jfr profiling and our tool would have shown him memory leak candidates