You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Guido Serra <ze...@fsfe.org> on 2012/12/16 03:28:41 UTC
ab: socket_timeout parameter "-s" (default: 30sec)
Hi,
I added a parameter to the utility Apache Benchmark (ab) to allow setting the socket timeout
...it is currently a hardcoded value at 30 seconds, and this is problematic on bad applications that
have a slight percentage of requests going above that threshold... or worse
Re: ab: socket_timeout parameter "-s" (default: 30sec)
Posted by Christophe JAILLET <ch...@wanadoo.fr>.
Le 17/12/2012 12:45, Christophe JAILLET a écrit :
> Le 16/12/2012 03:28, Guido Serra a écrit :
>> Hi,
>> I added a parameter to the utility Apache Benchmark (ab) to allow
>> setting the socket timeout
>> ...it is currently a hardcoded value at 30 seconds, and this is
>> problematic on bad applications that
>> have a slight percentage of requests going above that threshold... or
>> worse
>>
> Thank you for the patch and for the test results.
>
> I've applied it on my own tree but not pushed yet on trunk.
>
> You use a new -s switch. However,
> http://httpd.apache.org/docs/trunk/en/programs/ab.html has it already
> assigned.
> This was related to rudimentary https support.
>
> *But* I don't find anything that look like that in the code or
> changelog about this.
>
>
> Does any one know when/if this option was already used and where this
> rudimentary https support is ?
> The only things I have is the use of port 443 if the scheme has https://.
> Is there something I have missed ?
>
>
> IMO, using the -s option for passing a timeout should be OK, as per
> the proposed patch, and doc should be updated accordingly.
>
>
> Best regards,
> CJ
>
Applied to trunk:
http://svn.apache.org/viewvc?view=revision&revision=1422937
CJ
Re: ab: socket_timeout parameter "-s" (default: 30sec)
Posted by Christophe JAILLET <ch...@wanadoo.fr>.
Le 16/12/2012 03:28, Guido Serra a écrit :
> Hi,
> I added a parameter to the utility Apache Benchmark (ab) to allow setting the socket timeout
> ...it is currently a hardcoded value at 30 seconds, and this is problematic on bad applications that
> have a slight percentage of requests going above that threshold... or worse
>
Thank you for the patch and for the test results.
I've applied it on my own tree but not pushed yet on trunk.
You use a new -s switch. However,
http://httpd.apache.org/docs/trunk/en/programs/ab.html has it already
assigned.
This was related to rudimentary https support.
*But* I don't find anything that look like that in the code or changelog
about this.
Does any one know when/if this option was already used and where this
rudimentary https support is ?
The only things I have is the use of port 443 if the scheme has https://.
Is there something I have missed ?
IMO, using the -s option for passing a timeout should be OK, as per the
proposed patch, and doc should be updated accordingly.
Best regards,
CJ
Re: ab: socket_timeout parameter "-s" (default: 30sec)
Posted by Christophe JAILLET <ch...@wanadoo.fr>.
Le 16/12/2012 03:28, Guido Serra a écrit :
> Hi,
> I added a parameter to the utility Apache Benchmark (ab) to allow setting the socket timeout
> ...it is currently a hardcoded value at 30 seconds, and this is problematic on bad applications that
> have a slight percentage of requests going above that threshold... or worse
>
Thank you for the patch and for the test results.
I've applied it on my own tree but not pushed yet on trunk.
You use a new -s switch. However,
http://httpd.apache.org/docs/trunk/en/programs/ab.html has it already
assigned.
This was related to rudimentary https support.
*But* I don't find anything that look like that in the code or changelog
about this.
Does any one know when/if this option was already used and where this
rudimentary https support is ?
The only things I have is the use of port 443 if the scheme has https://.
Is there something I have missed ?
IMO, using the -s option for passing a timeout should be OK, as per the
proposed patch, and doc should be updated accordingly.
Best regards,
CJ