Has anybody actually tried running bleadperl with modperl and mpm_event on
Linux?  I wouldn’t be surprised if it works without coring in malloc() at
this point, or at least can be tuned to work.

On Sat, Aug 20, 2022 at 11:31 AM Joe Schaefer <j...@sunstarsys.com> wrote:

> Solaris libc malloc() is also tunable (% man mallopt again), but I can
> tell you that I've yet to have a reason to bother, because it simply
> doesn't dump core on my mod_perl applications.
>
>
>
> On Sat, Aug 20, 2022 at 10:37 AM Joe Schaefer <j...@sunstarsys.com> wrote:
>
>>
>>
>> ---------- Forwarded message ---------
>> From: Joe Schaefer <j...@sunstarsys.com>
>> Date: Fri, Aug 19, 2022 at 10:37 PM
>> Subject: Re: Experience running mod_perl2 with mpm_event on Solaris 11
>> To: pengyh <pen...@mail.de>
>>
>>
>> Seriously it’s always been a quality of implementation issue in open
>> source libc implementations (FreeBSD libc isn’t any better than glibc for
>> modperl and event_mpm).
>>
>> I papered over a third player in the memory management regimes in play.
>> The real problem for modperl isn’t apr pool allocations, it’s the bucket
>> brigades in the filter stacks.  That stuff is hitting malloc/free multiple
>> times every time you deliver content to the browser.  Combine that with a
>> lot of concurrent ithreads and things fall apart on non Solaris libc
>> implementations.
>>
>>
>> On Fri, Aug 19, 2022 at 10:17 PM Joe Schaefer <j...@sunstarsys.com> wrote:
>>
>>> Lower case t on technology
>>>
>>> On Fri, Aug 19, 2022 at 10:17 PM Joe Schaefer <j...@sunstarsys.com>
>>> wrote:
>>>
>>>> https://sunstarsys.com/CMS/Technology
>>>>
>>>> On Fri, Aug 19, 2022 at 10:15 PM pengyh <pen...@mail.de> wrote:
>>>>
>>>>> i am not a programming expert. but I hear that most scripts like
>>>>> perl/python/ruby support threads not that well. is it?
>>>>>
>>>>>
>>>>> Joe Schaefer wrote:
>>>>> > Yes, with per Interpreter Threads.  Everything else uses a Global
>>>>> > Interpreter Lock, which makes it single threaded on the actual op
>>>>> tree
>>>>> > walk (running your script logic, instead of system calls).
>>>>>
>>>> --
>>>> Joe Schaefer, Ph.D.
>>>> We only build what you need built.
>>>> <j...@sunstarsys.com>
>>>> 954.253.3732 <//954.253.3732>
>>>>
>>>>
>>>> --
>>> Joe Schaefer, Ph.D.
>>> We only build what you need built.
>>> <j...@sunstarsys.com>
>>> 954.253.3732 <//954.253.3732>
>>>
>>>
>>> --
>> Joe Schaefer, Ph.D.
>> We only build what you need built.
>> <j...@sunstarsys.com>
>> 954.253.3732 <//954.253.3732>
>>
>>
>>
>>
>> --
>> Joe Schaefer, Ph.D.
>> We only build what you need built.
>> <j...@sunstarsys.com>
>> 954.253.3732 <//954.253.3732>
>>
>>
>>
>
> --
> Joe Schaefer, Ph.D.
> We only build what you need built.
> <j...@sunstarsys.com>
> 954.253.3732 <//954.253.3732>
>
>
> --
Joe Schaefer, Ph.D.
We only build what you need built.
<j...@sunstarsys.com>
954.253.3732 <//954.253.3732>

Reply via email to