On Mon, 2004-02-23 at 16:04, Perrin Harkins wrote: > 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.
Hello Perrin, Umm, maybe we are talking about different things. If I run my application with 500+ httpd's in the process list using prefork, it uses a lot more memory than running 10 httpds with 64 threads each using worker. It also gets worse over time (as shared pages get altered). Did I miss something or did I do something wrong? > - Perrin -- Richard F. Rebel [EMAIL PROTECTED] t. 212.239.0000
signature.asc
Description: This is a digitally signed message part
