Re: Modperl 1.22 and Perl 5.6.0
On Fri, 24 Mar 2000, Ken Kosierowski wrote: > What is the best way to compile the new Perl 5.6.0 with Modperl 1.22? same way you compile 5.005 with mod_perl > Should I use the 5.005 compatible flags or start from scratch and recompile > the modules I use? you don't need the 5.005 compat flags to build mod_perl-1.22 > Are there performance issues using the 5.005 compat mode? not sure, doubt it though. > What about malloc and malloc flags -- same as what the Guide recommends? i the guide recommendations (TWO_POT_OPTIMIZE, etc) are the default since 5.005. i think linux still defaults to system malloc, you might want to configure Perl with -Dusemymalloc > What about issues with the upcoming Apache 2.0 and modperl 2.0? mod_perl-2.0 will be underway soon.
Re: Modperl 1.22 and Perl 5.6.0
On Tue, 28 Mar 2000, Doug MacEachern wrote: > On Fri, 24 Mar 2000, Ken Kosierowski wrote: > > > What is the best way to compile the new Perl 5.6.0 with Modperl 1.22? > > same way you compile 5.005 with mod_perl > > > Should I use the 5.005 compatible flags or start from scratch and recompile > > the modules I use? > > you don't need the 5.005 compat flags to build mod_perl-1.22 > > > Are there performance issues using the 5.005 compat mode? > > not sure, doubt it though. > > > What about malloc and malloc flags -- same as what the Guide recommends? > > i the guide recommendations (TWO_POT_OPTIMIZE, etc) are the default since > 5.005. i think linux still defaults to system malloc, you might want to > configure Perl with -Dusemymalloc Wait, doesn't usemymalloc mean to use the system's native malloc? This from INSTALL: "To build without perl's malloc, you can use the Configure command sh Configure -Uusemymalloc" On Linux 2.2, Perl uses its own malloc by default. To use the native malloc, specify -Dusemymalloc. It might be amusing to compare the two, as Linux has a very fast malloc implementation. BTW, I couldn't find reference to usemymalloc in the guide. Cheers, Jeffrey
Re: Modperl 1.22 and Perl 5.6.0
On Wed, 29 Mar 2000, Jeffrey W. Baker wrote: > > configure Perl with -Dusemymalloc > > Wait, doesn't usemymalloc mean to use the system's native malloc? This > from INSTALL: > > "To build without perl's malloc, you can use the Configure command > > sh Configure -Uusemymalloc" yeah, -Uusemymalloc means to use native malloc, notice i suggested -Dusemymalloc, which means to use Perl's malloc. > On Linux 2.2, Perl uses its own malloc by default. To use the native > malloc, specify -Dusemymalloc. It might be amusing to compare the two, as > Linux has a very fast malloc implementation. -U == undefine usemymalloc (use system malloc) -D == define usemymalloc (use Perl's malloc) i've benchmarked the two, it makes a HUGE difference under solaris, Perl's malloc kicks the sh*t out of solaris system malloc. Perl's malloc is not as much of a win under linux, i don't have the numbers handy though.
Re: Modperl 1.22 and Perl 5.6.0
Doug MacEachern wrote: > i've benchmarked the two, it makes a HUGE difference under solaris, Perl's > malloc kicks the sh*t out of solaris system malloc. Perl's malloc is not > as much of a win under linux, i don't have the numbers handy though. The only potential gotcha with perl's malloc is that it doesn't work if you compile perl as a 64-bit app (-Duse64bitall), as it isn't 64 bit clean. I don't suppose there are may people trying to build a 63-bit Apache though... Alan Burlison
