search

amnextking / typhoonae

Automatically exported from code.google.com/p/typhoonae
0 stars 0 forks source link

Dealing with memory leaky applications #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have noticed that, over time, Typhoon uses more and more memory, this is 
due to the modules that I use taking up more and more memory. The cause is 
irrelevant.

Google handles this issue by exiting application instances when they grow too 
big, and creating more when there is demand for them. I suggest that Typhoon 
implements similar functionality.

Original issue reported on code.google.com by Noah.Mci...@gmail.com on 15 Apr 2010 at 11:11

GoogleCodeExporter commented 9 years ago 
Absolutely! Thanks for reporting this. I wonder if this could be plugged into 
the supervisor or if the appserver 
itself takes care about that.

Original comment by tobias.r...@gmail.com on 15 Apr 2010 at 11:39

GoogleCodeExporter commented 9 years ago 
We now use the supervisor plugin superlance for controlling memory consumption 
of our appserver processes. It restarts any process in a given process group 
(app ID) consuming more than 200MB of RSS.

Original comment by tobias.r...@gmail.com on 12 Jul 2010 at 12:18

GoogleCodeExporter commented 9 years ago 
Available with the 0.2.0 release.

Original comment by tobias.r...@gmail.com on 12 Dec 2010 at 11:27