Mailing List Archive: ModPerl: ModPerl

Mod_Perl2 vs. Mod_Perl1, MPM_WORKER....

Index | Next | Previous | View Threaded

jrosenberg at shopzilla

Mar 23, 2007, 2:06 PM

Post #1 of 5 (2935 views)
Permalink

Mod_Perl2 vs. Mod_Perl1, MPM_WORKER....

Hi,

Išm just wondering what the mod_perl intelligencia thinks about the choice
between using mod_perl1 vs. mod_perl2....

Is there a reason not to go with the newer mod_perl2 (and Apache2, of
course). Is it stable and well accepted at this point? It seems like a
great number of people still use mod_perl1.....

Further, what success have people had using threading with mod_perl2, using
MPM_WORKER?

Jason

frank at wiles

Mar 26, 2007, 8:26 AM

Post #2 of 5 (2697 views)
Permalink

Re: Mod_Perl2 vs. Mod_Perl1, MPM_WORKER.... [In reply to]

On Fri, 23 Mar 2007 17:06:18 -0400
Jason Rosenberg <jrosenberg [at] shopzilla> wrote:

> Išm just wondering what the mod_perl intelligencia thinks about the
> choice between using mod_perl1 vs. mod_perl2....
>
> Is there a reason not to go with the newer mod_perl2 (and Apache2, of
> course). Is it stable and well accepted at this point? It seems
> like a great number of people still use mod_perl1.....

I can't think of a reason not to go with mod_perl2, I use it daily
and have for many months.

> Further, what success have people had using threading with mod_perl2,
> using MPM_WORKER?

Other than for some testing of modules I haven't found a need to use
either the threaded or worker MPMs.

---------------------------------
Frank Wiles <frank [at] wiles>
http://www.wiles.org
---------------------------------

pharkins at gmail

Mar 26, 2007, 9:28 AM

Post #3 of 5 (2706 views)
Permalink

Re: Mod_Perl2 vs. Mod_Perl1, MPM_WORKER.... [In reply to]

On 3/26/07, Frank Wiles <frank [at] wiles> wrote:
> > Further, what success have people had using threading with mod_perl2,
> > using MPM_WORKER?
>
> Other than for some testing of modules I haven't found a need to use
> either the threaded or worker MPMs.

I'd second that. The general advice is to avoid using threads if you
are on a unix-like system. They are slower and use more memory than
the prefork MPM on those systems.

- Perrin

wrowe at rowe-clan

Mar 26, 2007, 10:22 AM

Post #4 of 5 (2689 views)
Permalink

Re: Mod_Perl2 vs. Mod_Perl1, MPM_WORKER.... [In reply to]

Perrin Harkins wrote:
> On 3/26/07, Frank Wiles <frank [at] wiles> wrote:
>> > Further, what success have people had using threading with mod_perl2,
>> > using MPM_WORKER?
>>
>> Other than for some testing of modules I haven't found a need to use
>> either the threaded or worker MPMs.
>
> I'd second that. The general advice is to avoid using threads if you
> are on a unix-like system. They are slower and use more memory than
> the prefork MPM on those systems.

Hmmm, been using it here for about 6 years.

Careful with FUD, threading by definition is lighter weight than processes,
although the older Linux threads certainly didn't measure up.

Bill

pharkins at gmail

Mar 26, 2007, 12:11 PM

Post #5 of 5 (2694 views)
Permalink

Re: Mod_Perl2 vs. Mod_Perl1, MPM_WORKER.... [In reply to]

On 3/26/07, William A. Rowe, Jr. <wrowe [at] rowe-clan> wrote:
> Careful with FUD, threading by definition is lighter weight than processes,
> although the older Linux threads certainly didn't measure up.

We're not talking about Linux threads or apache threaded MPMs in
general here. The issue is Perl threads. They are implemented in a
way that makes them slower and heavier than a prefork model in most
cases, due to duplication without copy-on-write benefits. This has
been pretty thoroughly covered before so please check the mailing
archives if you want more information.

For static content, the worker MPM seems to work very well. I expect
it would be a good choice for your reverse proxy server.

- Perrin

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads