SPUG: mod_perl and fastcgi (was: large-scale projects)
cmeyer at helvella.org
Fri Jun 14 15:43:35 CDT 2002
On Fri, Jun 14, 2002 at 12:18:48PM -0700, Marc M. Adkins wrote:
[ description of FastCGI ]
> Because it is a stand-alone process, the cgi startup time (opening database
> connections and the like) isn't an issue. Because it is a separate process
> (not in the web server process space) you can do things like kill the
> process periodically and let the operating system reclaim the memory.
It isn't relegating the content generation and http serving to separate
processes that gives one these abilities.
When running under mod_perl, it is quite easy to periodically kill off
long running processes, to let the os reclaim memory. For example, see
Apache::GTopLimit, which allows one to set memory usage limits for httpd
The Apache::Resources module allows one to limit the amount of CPU time
(or other resources) that an instance of httpd is allowed to consume.
I'd like to see you accomplish that with FastCGI. ;-)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
POST TO: spug-list at pm.org PROBLEMS: owner-spug-list at pm.org
Subscriptions; Email to majordomo at pm.org: ACTION LIST EMAIL
Replace ACTION by subscribe or unsubscribe, EMAIL by your Email-address
For daily traffic, use spug-list for LIST ; for weekly, spug-list-digest
Seattle Perl Users Group (SPUG) Home Page: http://seattleperl.org
More information about the spug-list