Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Date: Mon, 12 Jul 2010 22:36:21 +0200
From: "Thomas den Braber" <thomas@delos.nl>
To: modperl@perl.apache.org
Subject: Re: Strawberry perl + mod_perl (call for testers)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <WC20100712203621.310079@delos.nl>
In-Reply-To: <20100709201623.GD3036@wladimir>
References: <4C1FD127.3060807@volny.cz>
 <AANLkTimP1oCDwBU2RZ2hfK4nMorZ-SoZlJ_ennx8JKTT@mail.gmail.com>
 <20100709161229.GC3036@wladimir>
 <AANLkTilzgsnz-38dRCoLdv2mwiTVjKI20dAUSXuF7x6h@mail.gmail.com>
 <20100709201623.GD3036@wladimir>

I have very good experiences with Apache under Windows. Especially with
running under Windows 2008 64 Bit (with 32 bit versions of Apache and Perl).
It runs very fast and comes close to the speed of running under Linux.

One big disadvantage is that you can only run in Worker MPM. If you have a
big modperl application it uses much more memory than with the Prefork MPM
on Linux. Also restarting Apache Worker takes more time then with Prefork
MPM on Linux.

But stability and performance are very good.

--
Thomas den Braber

-----Original Message-----
From: Michael Ludwig <milu71@gmx.de>
To: modperl@perl.apache.org
Date: Fri, 9 Jul 2010 22:16:23 +0200
Subject: Re: Strawberry perl + mod_perl (call for testers)

> Perrin Harkins schrieb am 09.07.2010 um 13:19 (-0400):
> > On Fri, Jul 9, 2010 at 12:12 PM, Michael Ludwig <milu71@gmx.de>
> wrote:
> 
> > > What's the status of using mod_perl on Windows?
> > 
> > http://perl.apache.org/docs/2.0/os/win32/install.html
> 
> Thanks. Doesn't sound too bad. So it's (1) ActiveState, (2) one of the
> All-in-one packages mentioned, or (3) build your own. Or - as announced
> by the originator of this thread - (4) Strawberry mod_perl.
> 
> I stumbled upon a blog post, which may or may not be relevant, or
> rather
> like the domain name indicates:
> 
> The Rise and Fall of mod_perl
> http://blog.afoolishmanifesto.com/archives/1303
> 
> The title is badly chosen, as it doesn't deal with any rise or fall of
> mod_perl, but only with the author's experiences of using mod_perl on
> Windows. Could be summarized as follows:
> 
> * crashes and leaks running mod_perl on Windows (maybe just FUD, no
>   indication it was specific to Windows)
> * could be fixed
> * desire to use Strawberry and CPAN instead of ActiveState and PPM
>   (the former possibly being more convenient to use)
> * no success building mod_perl against Strawberry (no need to do this
>   any more now as Strawberry offers mod_perl binaries now)
> * more crashes on mod_perl/Windows with a Catalyst app
> * switch made from mod_perl to Pure Perl Server plus Apache/mod_proxy
> 
> Relevant or not, this story makes me ask the following questions:
> Are there any people on this list using mod_perl 2.0 on Windows?
> Do you have any positive or negative experiences to share?
> 
> -- 
> Michael Ludwig