The problem is really confined to embedded uses of ithreads, because Perl itself will mutex-wrap the malloc calls. In httpd, so do all apr_pool_t calls to malloc. It's when the two memory management techniques are interacting that there is no application-level way to guard against thread contention in libc's malloc.
Mod_perl+ithreads are awesome, when used intelligently. You gain intelligence from experience trying to use it in a lot of ways that suck, until you hit one the path that yields success. -----Original Message----- From: Edward J. Sabol <edwardjsa...@gmail.com> Sent: Tuesday, August 16, 2022 2:27 PM To: mod_perl list <modperl@perl.apache.org> Subject: Re: Experience running mod_perl2 with mpm_event on Solaris 11 On Aug 16, 2022, at 12:27 PM, j...@sunstarsys.com wrote: > To the best of my knowledge, the underlying problem with mod_perl+ithread is > that it requires a reentrant malloc in libc. That's it? This is the first I'm learning this. Is there an option to compile Perl and mod_perl with a reentrant malloc on Linux? Thanks, Ed
openpgp-digital-signature.asc
Description: PGP signature
