[Catalyst] Catalyst for (really) big applications

Perrin Harkins perrin at elem.com
Mon May 22 15:25:22 CEST 2006


On Mon, 2006-05-22 at 08:30 +0200, Marcello Romani wrote:
> ThreadsPerChild 250
[...]
> as config 1, but ThreadsPerChild 1

You wouldn't really want either of these values, would you?  250 means
that you have enough memory to run 250 Perl interpreters with your app
loaded, which seems unlikely, especially since threads kill the
copy-on-write sharing you'd get from processes.  And 1 is no good
because it limits your concurrency.

You may want to keep the threads high for static requests and limit the
number of interpreters by setting PerlInterpMax.

In general, Perl's memory use will be more efficient on a pre-fork
platform than a threaded one, since copy-on-write usually helps quite a
bit.

- Perrin




More information about the Catalyst mailing list