On Mon, 2004-02-23 at 10:03, Richard F. Rebel wrote: > I am using ap2 + mp2 with the worker mpm and ithreads to serve about 12 > million dynamically generated pages per day. This includes RPC calls > via HTTP and database queries. I am currently experimenting with > creating pools of threads inside the perl interpreter for handling > communicating with multiple remote machines simultaniously. > > My project would not be possible using prefork without a huge increase > in hardware expense (the reason we tried using worker mpm).
What's the reason for this? Are you saving memory by using the worker MPM? I thought the consensus was that perl threads actually use more memory than pre-fork at this point. - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
