Ack, no. Apache and o/s's have come a long way since then, and you should really have your value quite a bit higher (couple thousand or even 0). Our main front-end web server is set to 0, and has an uptime of a couple of weeks. Perl scripts don't cause memory leaks in the main code as perl is destroyed every request.
With mod_perl there are other things to consider:
- too low a maxrequests and you negate any benefit of having mod_perl as you need to spawn a new child, load perl, load scripts, quite often.
- too high a maxrequests and you need to make _very_ sure your perl code doesn't have any memory leaks in it. Something as simple as:
push @GLOBAL, "something";
would cause an ever growing array in mod_perl (as the variable never gets destroyed properly). These sort of errors need to be fixed, but other more subtle ones you can live with by setting a not too high maxrequests.
Cheers,
Alex
--
Gossamer Threads Inc.
With mod_perl there are other things to consider:
- too low a maxrequests and you negate any benefit of having mod_perl as you need to spawn a new child, load perl, load scripts, quite often.
- too high a maxrequests and you need to make _very_ sure your perl code doesn't have any memory leaks in it. Something as simple as:
push @GLOBAL, "something";
would cause an ever growing array in mod_perl (as the variable never gets destroyed properly). These sort of errors need to be fixed, but other more subtle ones you can live with by setting a not too high maxrequests.
Cheers,
Alex
--
Gossamer Threads Inc.
