Re: Why MP2
[prev]
[thread]
[next]
[Date index for 2004/12/15]
Jayce^ wrote:
> In preparation for the upcoming release of mod_perl2, I'd
> like to prepare a list of reasons why a person/company
> would look at using mod_perl2, specifically, why upgrade
> from mod_perl1, and converting from other technologies.
>
> So with that, what reasons do you have for wanting MP2?
>
> What prevented you from upgrading before?
>
> What key features are most interesting for you?
>
> How will this help your company?
I've helped developed mp2 for Win32, and on that platform
there's an enormous gain compared to mp1 - mp1 is
essentially single threaded, which prevents parallel
processing of requests, whereas mp2 is multi-threaded. Above
that, Apache2 on Win32 also has significant performance
gains, compared to Apache1.
I've also been using mp2 and libapreq2 on a linux server for
about a year now - nothing fancy, but it's been quite
stable, and, eyeballing it, is as good or better than the
equivalent mp1 system I used before in terms of speed and
memory requirements. I used the mp2 compatibility layer
initially in the migration, but as in particular Stas added
to the docs discussions of designing mp2 handlers without
Apache::compat, converting things to pure mp2 was relatively
straightforward.
Of course, there was some hesitation in taking a perfectly
functional mp1 system and migrating it over to mp2. The
biggest reason for me is that Apache2/mp2 will be the most
actively developed in the future (although Apache1/mp1 won't
go away anytime soon).
--
best regards,
randy kobes
--
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
 |
(message missing)
|
 |
 |
Why MP2
Jayce^ 23:19 on 13 Dec 2004
|