Re: eating memory ... // RE: Porting to OS X
On Wed, 5 Jun 2002, Alvar Freude wrote: > probably it's the same as on FreeBSD: if you use a DSO mod_perl, for each > restart (apachectl graceful or apachectl restart) it eats all the memory > your mod_perl modules use. Try to build it statically; at least on FreeBSD > it helps, and OSX is FreeBSD ... :-) > > But my newest test was with Apache 1.3.23 and mod_perl 1.26; perhaps it's > fixed in 1.27?!? dso should be fine with 1.26 or 1.27, provided you are using Perl 5.6.1 or higher. 5.005_03 still has leakage.
eating memory ... // RE: Porting to OS X
Hi, -- Michael Robinton <[EMAIL PROTECTED]> wrote: > application, which runs on an aging 486 with 64 megs in our shop and uses > about 4 megs including mod_perl enhanced apache, took 40 megs on OSX and > was very slow. This was on a G4 with 500 megs of memory. probably it's the same as on FreeBSD: if you use a DSO mod_perl, for each restart (apachectl graceful or apachectl restart) it eats all the memory your mod_perl modules use. Try to build it statically; at least on FreeBSD it helps, and OSX is FreeBSD ... :-) But my newest test was with Apache 1.3.23 and mod_perl 1.26; perhaps it's fixed in 1.27?!? But nevertheless 4 MB is very small; my frontend Apache 1.3.23 without mod_perl takes 3 MB; my frontend Apache 2.0.36 on developing system >4 MB without mod_perl ... Ciao Alvar -- // Unterschreiben! http://www.odem.org/informationsfreiheit/ // Internet am Telefon: http://www.teletrust.info/ // Das freieste Medium? http://www.odem.org/insert_coin/ // Blaster: http://www.assoziations-blaster.de/