It's not the spawn per se that takes 2 seconds, but either the time to
wait for a child process to accept the new connection (if all the
children are busy and the max is reached), or the children maintenance
code that sleeps (1 second) between loops (still creating children at
once, exponentially,
f: Re: [users@httpd] Random latency in reentrant calls (Bug 57916) [wd-vc]
Yes, but I'm still very surprised that spinning a new process can take up to 2
seconds on a powerful server :-(
On Tue, May 12, 2015 at 12:26 PM, Yann Ylavic
mailto:ylavic@gmail.com>> wrote:
So is it working
Yes, but I'm still very surprised that spinning a new process can take up
to 2 seconds on a powerful server :-(
On Tue, May 12, 2015 at 12:26 PM, Yann Ylavic wrote:
> So is it working as expected now?
>
> On Tue, May 12, 2015 at 12:07 PM, Luc Andre wrote:
> > My mistake, apache2.conf is overrid
So is it working as expected now?
On Tue, May 12, 2015 at 12:07 PM, Luc Andre wrote:
> My mistake, apache2.conf is overridden by /mods-enabled/mpm_prefork.conf
>
> sorry about that...
>
>
>
>
> On Tue, May 12, 2015 at 12:03 PM, Luc Andre wrote:
>>
>> php_sapi_name: apache2handler
>>
>>
>> Serve
My mistake, apache2.conf is overridden by /mods-enabled/mpm_prefork.conf
sorry about that...
On Tue, May 12, 2015 at 12:03 PM, Luc Andre wrote:
> php_sapi_name: apache2handler
>
>
> Server MPM: prefork
>
> I tried
>
> StartServers 20
> MinSpareServers 20
> Max
php_sapi_name: apache2handler
Server MPM: prefork
I tried
StartServers 20
MinSpareServers 20
MaxSpareServers 20
And after restarting apache still have the issue but only after waiting
about a minute between 2 tries.
Then I did a "ps -ef | grep apache" and I
2015-05-12 10:03 GMT+02:00 Luc Andre :
> Thanks for your reply.
>
> We did a test on a powerful server with
>
> StartServers 20
> MinSpareServers 5
> MaxSpareServers 20
>
> And we still have the issue...
>
To ensure that you don't hit the child spin up issue, you'l
Hi Luc,
can you please provide the corresponding error log (level debug)?
There may be higher (overall) times spent, but still difference for the
same % of requests.
Regards,
Yann.
On Tue, May 12, 2015 at 10:03 AM, Luc Andre wrote:
> Thanks for your reply.
>
> We did a test on a powerful serv
Thanks for your reply.
We did a test on a powerful server with
StartServers 20
MinSpareServers 5
MaxSpareServers 20
And we still have the issue...
As you pointed out the logging happens after the request and we get the
time at the beginning of the php script to m
You are probably hitting child spin up issues...
Out of the box apache uses a process per apache child... There is an
overhead/delay when a child is initially spun up,
and that is what you are possibly seeing...
nginx works a different way - and can cope with a moderate number of
"light" requ
This issue was first submitted as a bug report but I was advised to use
this mailing list instead.
The problem occurs with an 'out of the box' configuration (tested on debian
and windows)
Our php web site requires sometimes a reentrant call (i.e. it calls
file_get_contents(http://127.0.0.1/reentr
11 matches
Mail list logo
