You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2003/12/10 10:04:10 UTC
[mp2] raising the default startup timeout
As our test suite grows it takes more and more time to start the server, the
worker mpm almost always fail to start within 60 secs on my machine (which is
pretty fast). And now we get reports from users who run prefork and it takes
68 secs to start.
So I'd suggest to make the default per server mpm and not one for all and go
with 120 secs for prefork and 180 worker/winnt. If it sometimes takes more
than 90 secs to start worker on my machine, I can see it hitting 3 minutes on
a slower machine.
Ideally there should be no timeout at all, if we could deterministically
detect a failure in the server startup, but we weren't quite successful at it
so far.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] raising the default startup timeout
Posted by "Philippe M. Chiasson" <go...@cpan.org>.
On Wed, 2003-12-10 at 01:04, Stas Bekman wrote:
> As our test suite grows it takes more and more time to start the server, the
> worker mpm almost always fail to start within 60 secs on my machine (which is
> pretty fast). And now we get reports from users who run prefork and it takes
> 68 secs to start.
I constantly hover between 55-65 seconds, so my local copy has been
patched for 90secs for quite a while already ;-)
> So I'd suggest to make the default per server mpm and not one for all and go
> with 120 secs for prefork and 180 worker/winnt. If it sometimes takes more
> than 90 secs to start worker on my machine, I can see it hitting 3 minutes on
> a slower machine.
>
> Ideally there should be no timeout at all, if we could deterministically
> detect a failure in the server startup, but we weren't quite successful at it
> so far.
Well, until we can do that reliably, I am completely in favor of a
high(er) timeout
> __________________________________________________________________
> Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org http://ticketmaster.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
--
--------------------------------------------------------------------------------
Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 (122FF51B/C634E37B)
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3 A5A5
Q: It is impossible to make anything foolproof because fools are so ingenious.
perl -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}'
Re: [mp2] raising the default startup timeout
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>>Of course. We have the new argument -startup_timeout (which is still
>>misplaced), which we will set if it wasn't set already, just like
>>maxclients.
>
>
> actually, I no longer think it's misplaced - I want the persistence that
> placing it where it is gives. that is, if I need to raise it for my
> particular box, I don't want to be required to raise it every time I call
> t/TEST.
So you suggest to make it a configuration option (which it happens to be now).
Fine with me.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] raising the default startup timeout
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> Of course. We have the new argument -startup_timeout (which is still
> misplaced), which we will set if it wasn't set already, just like
> maxclients.
actually, I no longer think it's misplaced - I want the persistence that
placing it where it is gives. that is, if I need to raise it for my
particular box, I don't want to be required to raise it every time I call
t/TEST.
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] raising the default startup timeout
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
> Stas Bekman wrote:
>
>>As our test suite grows it takes more and more time to start the server,
>>the worker mpm almost always fail to start within 60 secs on my machine
>>(which is pretty fast). And now we get reports from users who run
>>prefork and it takes 68 secs to start.
>
>
> yikes. I got 49 seconds last night, so I guess it is pretty close
And that's on Unloaded machine. Try to do some heave things at the same time
(e.g. run another test suite or compilation) and the startup time will double.
>>So I'd suggest to make the default per server mpm and not one for all
>>and go with 120 secs for prefork and 180 worker/winnt. If it sometimes
>>takes more than 90 secs to start worker on my machine, I can see it
>>hitting 3 minutes on a slower machine.
>
>
>
> I'm in favor so long as the change is mod_perl specific - no need to burden
> the entire apache community with perl's bloat :)
Of course. We have the new argument -startup_timeout (which is still
misplaced), which we will set if it wasn't set already, just like maxclients.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] raising the default startup timeout
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
> Stas Bekman wrote:
>
>>As our test suite grows it takes more and more time to start the server,
>>the worker mpm almost always fail to start within 60 secs on my machine
>>(which is pretty fast). And now we get reports from users who run
>>prefork and it takes 68 secs to start.
>
>
> yikes. I got 49 seconds last night, so I guess it is pretty close
>
>
>>So I'd suggest to make the default per server mpm and not one for all
>>and go with 120 secs for prefork and 180 worker/winnt. If it sometimes
>>takes more than 90 secs to start worker on my machine, I can see it
>>hitting 3 minutes on a slower machine.
>
>
>
> I'm in favor so long as the change is mod_perl specific - no need to burden
> the entire apache community with perl's bloat :)
now commmitted.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] raising the default startup timeout
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Stas Bekman wrote:
> As our test suite grows it takes more and more time to start the server,
> the worker mpm almost always fail to start within 60 secs on my machine
> (which is pretty fast). And now we get reports from users who run
> prefork and it takes 68 secs to start.
yikes. I got 49 seconds last night, so I guess it is pretty close
>
> So I'd suggest to make the default per server mpm and not one for all
> and go with 120 secs for prefork and 180 worker/winnt. If it sometimes
> takes more than 90 secs to start worker on my machine, I can see it
> hitting 3 minutes on a slower machine.
I'm in favor so long as the change is mod_perl specific - no need to burden
the entire apache community with perl's bloat :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org