snacktime at gmail
Jul 20, 2005, 3:57 PM
Post #8 of 8
(683 views)
Permalink
|
|
Re: memory leak with perl5.8/freebsd/mod_perl 1.29
[In reply to]
|
|
> > rev 1.61
>
> "Switch to perlmalloc by
> default, unless threaded perl is built, to improve performance."
>
> > rev 1.49
>
> "WITH_PERL_MALLOC - to compile with perl's own malloc, as opposed to
> the freebsd system malloc. Some might find this useful, since perl's
> malloc is marginally faster in typical cases, and orders of
> magnitude faster in degenerate cases. Use with care."
>
> Guess this does show the main reason for this is a performance problem with
> Perl's usage of FreeBSD's malloc(). But I'd be curious to see if this
> performance problem is still a problem. And if it still is a problem, maybe
> there is something Perl isn't doing quite right.
>
> In any case, getting to the bottom of this issue sure sounds interesting.
>
> In the meantime, FreeBSD'ers that have growing problems on FreeBSD should
> consider building their ports Perl with WITH_PERL_MALLOC=no
>
That's a requirement btw if you are using perl 5.6.x on Freebsd and
build mod perl from ports. The default build of perl 5.6.x on freebsd
is incompatible with the mod perl port because the perl malloc causes
a segfault when mod perl is built as a dso. The mod perl port gives a
warning about it though.
Chris
|
signature.asc
