in reply to Catalyst/FastCGI and Perpetually Growing Perl Processes
What's the best approach?
find memory leak and resolve once and for all ( Devel::NYTProf, Devel::Leak Devel::LeakTrace, WeakRef ) ?
Scheduled periodic restart with Catalyst::Restarter or some such?
although it just seems to me that the processes are living a long time and never releasing memory back to the system.
Yeah, that is kind of the point of FastCGI, long lived processes :)
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Catalyst/FastCGI and Perpetually Growing Perl Processes
by jeffthewookiee (Sexton) on Oct 15, 2012 at 13:31 UTC | |
by Anonymous Monk on Oct 15, 2012 at 23:44 UTC |
In Section
Seekers of Perl Wisdom