jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: httpclient4.time_to_live defaults to 2000 which is way less than the typical browser behavior
Date Wed, 25 Dec 2019 11:17:44 GMT

Am 12.12.19 um 11:21 schrieb Vladimir Sitnikov:
> Hi,
>
> JMeter defaults to 2 seconds timeout for keep-alive HTTP connections, which
> seems to be much less than the typical browser configuration.
>
> https://en.wikipedia.org/wiki/HTTP_persistent_connection#Use_in_web_browsers
> ,
> https://fastmail.blog/2011/06/28/http-keep-alive-connection-timeouts/
> suggest that:
> IE: 60 sec
> FireFox: 115 sec
> Chrome: 300 sec
>
> What do you think if we bump the default for httpclient4.time_to_live from
> 2000 to 120000 (==2 min)?
>
> I guess the current setting of 2000 was just a copy-paste result when the
> setting was initially implemented.
> Here's the commit that introduces the feature:
> https://github.com/apache/jmeter/commit/eaaf1be40908ba5f74e7baac9ea985cc62de6a6f#diff-4e3471b25c91730a99ed23402467b9eaR146

When we use a higher default, we are using more connections on the
client, which can be a sparse resource. So I think two minutes is
relatively high.

Two seconds might be a bit low, but I personally don't use keepalives
longer that five to ten seconds on our servers.

Felix

>
> Vladimir
>

Mime
View raw message