News for hackers. Stuff that matters.
Re:Diagnosing Memory “Leaks” in Python by cheez on Monday September 07, 2015 @03:10PM (#10182622)
Kind of surprised the poster didn't know that operating systems often hold on to memory.

> we noticed that the memory of the celery process was continuing to grow.

Doesn't look like there was any bad outcome related to this observation. Was any process not getting the memory it wanted?

Re:Diagnosing Memory “Leaks” in Python by ldarby on Monday September 07, 2015 @07:33PM (#10183484)
There are in fact bad outcomes of continued memory growth - firstly there is a catastrophic performance degradation when processes start getting swapped to disk, then when swap space runs out Linux's OOM killer starts killing processes in an attempt to free up memory. Kind of surprised you didn't know this.
Re:Diagnosing Memory “Leaks” in Python by cheez on Tuesday September 08, 2015 @03:04AM (#10184385)
Except that didn't happen, according to the post.
Re:Diagnosing Memory “Leaks” in Python by ldarby on Tuesday September 08, 2015 @09:12AM (#10185436)
The post says: "Indeed, the processes grew from their initial size of 100MB, slowly, all the way up to 1GB before we killed them."

The important part is that they manually killed the processes before they let it start swapping.

Re:Diagnosing Memory “Leaks” in Python by cheez on Tuesday September 15, 2015 @11:16PM (#10224465)
Again, they didn't actually have anything bad happen. Bad: processes couldn't get memory. Not bad: I was using 3 GB of memory.
Re:Diagnosing Memory “Leaks” in Python by falsedan on Tuesday September 08, 2015 @02:26AM (#10184314)
buy more RAM

KIND OF SURPRISED YOU DIDN'T BUY MORE RAM