-
Notifications
You must be signed in to change notification settings - Fork 0
Memory Stress Testing
When stress testing memory we want to move lot's of memory around, a lot and everywhere. To do so we need large objects that can fill up the memory without being to much of a burden to the CPU. Because the more you are of a burden to eat it the more you create a weak link out of it. Which means in case it's not stable it could cause errors or crash and that would leave you there not knowing what exactly crashed.
My solution for moving a lot of data around is creating a large data object.
Successfully allocated memory on the off-heap

Currently having memory leaks...

Fixed memory leaks, and stress test is actually working, no good fail safes yet but we have something
still having memory leaks i think, all instances should be closed, but i am doing the correct error handling in my code, maybe I'm not closing the fibers correctly