>
> FYI, I reposted the benchmarks without the MaxRequestsPerChild 100 set
> for HTML::Mason & Template Toolkit, as it was only Embperl 2.x that
> needed it.
>
Embperl 2.0b8 has still some real memory leaks. That's why it called beta.
Of course they will be fixed before the final release of 2.0.
Ed wrote:
> Hi,
>
> (as far as i can tell after a quick peek at the code and some debugging)
>
> It looks like there is a bug w/ AxKit::run_axkit_engine() and/or
> Apache::AxKit::Cache::_get_stats()
>
This is really great Ed. Adding the AxGzipOutput On config to the XSLT
tests in the benchmar
Dave Rolsky wrote:
> On Mon, 14 Oct 2002, Josh Chamas wrote:
>
>
>>This is interesting. I should look into upgrading to perl 5.8 on
>>these tests & see what difference there may be.
>>
>>You might also see if it makes a difference if you run the tests for
>>a long enough time. I run them at le
Hi,
(as far as i can tell after a quick peek at the code and some debugging)
It looks like there is a bug w/ AxKit::run_axkit_engine() and/or
Apache::AxKit::Cache::_get_stats()
run_axkit_engine() wants to create a .gzip cachefile when AxGzipOutput is off.
When AxGzipOutput is off the .gzip fil
On Mon, 14 Oct 2002, Josh Chamas wrote:
> This is interesting. I should look into upgrading to perl 5.8 on
> these tests & see what difference there may be.
>
> You might also see if it makes a difference if you run the tests for
> a long enough time. I run them at least 60 seconds for these be
Dave Rolsky wrote:
>
> I'm fairly sure, FWIW, that Mason does not have any memory leaks, as of
> 1.12. Pre-1.10 versions do have a _very_ slow memory leak, and 1.10 and
> 1.11 had that leak plus another, much nastier one.
>
Yes, Mason seemed pretty free of leaks when I tested it more today too
Perrin Harkins wrote:
> Josh Chamas wrote:
>
>> Set MaxRequestsPerChild to 100 for applications that seem to leak
>> memory which include Embperl 2.0, HTML::Mason, and Template Toolkit.
>> This is a more typical setting in a mod_perl type application that
>> leaks memory, so should be fai
On Tue, 15 Oct 2002, Perrin Harkins wrote:
> Josh Chamas wrote:
>
> > Set MaxRequestsPerChild to 100 for applications that seem to leak
> > memory which include Embperl 2.0, HTML::Mason, and Template Toolkit.
> > This is a more typical setting in a mod_perl type application that
> > leaks
Josh Chamas wrote:
> Set MaxRequestsPerChild to 100 for applications that seem to leak
> memory which include Embperl 2.0, HTML::Mason, and Template Toolkit.
> This is a more typical setting in a mod_perl type application that
> leaks memory, so should be fairly representative benchmark s
Hey,
The Apache Hello World benchmarks are updated at
http://chamas.com/bench/
The changes that affect performance numbers include:
Set MaxRequestsPerChild to 1000 globally for more realistic run.
Set MaxRequestsPerChild to 100 for applications that seem to leak
memory which inclu
10 matches
Mail list logo