>> If you want to try it yourself and report back, I'm sure we'd all be
>> interested in what you find out. The main thing I'm aware of is that
>> copy-on-write works very well for preforking and threads usually can't
>> match it, but maybe your application is different.
>>
>> Regarding your
> If you want to try it yourself and report back, I'm sure we'd all be
> interested in what you find out. The main thing I'm aware of is that
> copy-on-write works very well for preforking and threads usually can't
> match it, but maybe your application is different.
>
> Regarding your
If you want to try it yourself and report back, I'm sure we'd all be
interested in what you find out. The main thing I'm aware of is that
copy-on-write works very well for preforking and threads usually can't
match it, but maybe your application is different.
Regarding your thread-safety
Hi Perrin,
Thank you for your answer.
Well, for the moment I only use the prefork (non-threaded) MPM.
But I would have liked to test performance of the threaded MPM, so I would have
liked my code to be thread-ready.
According to this :
Hi Ben.
Before you get too far into the details of using threads, can I ask why
you're considering it? The memory footprint and performance of using forked
processes with Perl is generally going to be better than that of threads,
due to copy-on-write.
- Perrin
On Mon, Apr 4, 2016 at 4:44 PM,
Hello,
I have some questions regarding mod_perl, threads, thread-safe functions,
special vars scope...
From
https://perl.apache.org/docs/2.0/user/coding/coding.html#toc_Thread_environment_Issues
:
"if you chdir() in one thread, all other thread now see the current working
directory of that
