I run eatmemory and pass it an argument of 10G. I can see the program start to consume memory by using vmstat and top. However, an oomkill happened right when all them memory was exhausted and the eatmemory process was killed.
I didn't notice any effect on interactive performance once the OOM kill happened.
I was unable to reproduce this issue on my machine, which has an SSD drive.
I'm using the eatmemory program found at: /github. com/julman99/ eatmemory
https:/
I run eatmemory and pass it an argument of 10G. I can see the program start to consume memory by using vmstat and top. However, an oomkill happened right when all them memory was exhausted and the eatmemory process was killed.
I didn't notice any effect on interactive performance once the OOM kill happened.