Date: Tue, 21 Sep 2010 09:37:40 -0400 From: Alejandro Imass <ait@p2ee.org> To: Michael Powell <nightrecon@hotmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: apache22 and threads Message-ID: <AANLkTi=OGbvqtxoVc1h%2BdH4d_jWh708cRuqav4jGjAfh@mail.gmail.com> In-Reply-To: <i79usq$7h9$1@dough.gmane.org> References: <20100920060811.GA10084@admin.sibptus.tomsk.ru> <i77jch$cee$1@dough.gmane.org> <20100921090316.GA36655@admin.sibptus.tomsk.ru> <i79usq$7h9$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 21, 2010 at 5:48 AM, Michael Powell <nightrecon@hotmail.com> wrote: > Victor Sudakov wrote: > > [snip] [...] > > The prefork mpm without threads and mod_php is a safe bet for a server that > will not be hitting the wall, traffic volume-wise. > Yeah well php sucks in any case, for many reasons that are OT to this thread. Perl / mod_perl on the other hand can work quite well with mod_worker (threads) sharing many thing including all the non-mutable data, this is because Perl in general is thread safe. Using mod_worker with mod_perl can mean the difference between serving a few hundred simultaneous request to a few thousand, on the same exact hardware. Not all Perl modules are thread safe however, and in any case most thread implementations in Unix, including FreeBSD, are a potentially leaky by nature, but you can use the MaxRequestsPerChild directive (and others) to fine-tune the growing of your processes/threads. > -Mike > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=OGbvqtxoVc1h%2BdH4d_jWh708cRuqav4jGjAfh>