Hello,

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).

Performance is good on decent hardware, sub second page generation
times.  I have noticed that for my app, prefork was a smidgen faster.

That said the following should be said as well:

Make sure (atleast on Linux) that you have set your number of available
threads high enough that requests do not have to wait for a new thread
to be created.  Your performance will suck otherwise as new thread
creation is slower than one would expect.  This is true for apache2
without mod_perl as well btw but not quite as bad..

Apache2 still has bugs, so does mp2, be careful.  I have identified at
at least one run away memory leak that I can't track down and apache2
segfaults on occasion.  Isolating such things in busy threaded apps is
*very* difficult.  

ithreads in perl are very slow to start and the implementation is a bit
buggy with spotty documentation.  Eg, you *can NOT* return a list from a
thread, you may return exactly one scalar ref to whatever, the docs are
*wrong* and the snots on P5P have yet to even admit (atleast to me, I
stopped following the issue a while ago, may be fixed now) that this is
even a bug or a problem.  

Best,

Richard F. Rebel



On Sat, 2004-02-21 at 06:07, Stefan Cars wrote:
> Hi!
> 
> I don't have any problems, I'm just interested in what people think of
> the performance vs. preforking and if there is any problems using worker
> and ithreads ?
> 
> On Fri, 20 Feb 2004, Stas Bekman wrote:
> 
> > Stefan Cars wrote:
> > > Hi!
> > >
> > > Anyone that has any good links or any good input on using the worker MPM
> > > and ithreads with mod_perl 2 and Apache 2
> >
> > You could be a bit more specific, Stafan. What kind of problems do you have?
> > You also have to tell us more about your environment, which is done the best
> > by calling mp2bug or t/REPORT
> > http://perl.apache.org/docs/2.0/user/help/help.html#Important_Information
> >
> > __________________________________________________________________
> > Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> > http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> > mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> > http://modperlbook.org http://apache.org   http://ticketmaster.com
> >
> 
> --
> Stefan Cars
> Snowfall Communications
> Tel: +46 (0)18 430 80 50 - Direct: +46 (0)18 430 80 51
> Mobile: +46 (0)708 44 36 00 - Fax: +46 (0)708 44 36 04
> 
> 
> 
> ______________________________________________________________________
> SNOWFALL DISCLAIMER:
> The information contained in this email and in any
> attachments is confidential and may be privileged. If you are not the
> intended recipient, please destroy this message and notify the sender
> immediately. You should not retain, copy or use this email for any
> purpose, nor disclose all or any part of its content to any other person.
> Any views expressed in this message are those of the individual sender,
> except where the sender specifically states them to be the views of
> Snowfall Communications.
> 
> Snowfall Communications monitors the content of emails sent and received
> via its network for unauthorised use and for other lawful business
> purposes. The contents of an attachment to this email may contain viruses
> which could damage your computer system. While Snowfall Communications has
> taken every reasonable precaution to minimise this risk, we cannot accept
> liability for any damage which you sustain as a result of software
> viruses. You should carry out your own virus checks before opening the
> attachment.
-- 
Richard F. Rebel
[EMAIL PROTECTED]
t. 212.239.0000

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to