You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2016/02/18 18:20:43 UTC
[Bug 59029] New: httpclient PoolingConnectionManager has
inappropriate default values
https://bz.apache.org/bugzilla/show_bug.cgi?id=59029
Bug ID: 59029
Summary: httpclient PoolingConnectionManager has inappropriate
default values
Product: JMeter
Version: 2.13
Hardware: Macintosh
OS: Windows CE
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: benoit.wiart@gmail.com
looks like jmeter is using the PoolingConnectionManager default values.
>From PoolingConnectionManager javadoc
* PoolingConnectionManager maintains a maximum limit of connection on
* a per route basis and in total. Per default this implementation will
* create no more than than 2 concurrent connections per given route
* and no more 20 connections in total.
We should initialize the MeasuringConnectionManager with better (higher)
default values.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59029] httpclient PoolingConnectionManager has inappropriate
default values
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59029
--- Comment #4 from benoit.wiart@gmail.com ---
> JMeter is not a browser.
thanx I wasn't aware...
But, to be realist, the load should simulate a browser behavior.
> A browser with a single tab does not need as many connections.
Where did you take this information ?
I'm afraid that's wrong. Google for "browser max connection per host".
for example for ie 8 :
"The connection limit is per process, the browser will make the determination
about process creation as a web site owner you can't really change that. The
process may be shared between multiple tabs/windows or it may not, it depends
on many factors outside your control."
the new default value will not change the "main" http samplers as for a given
user they are executed sequentially.
But it will make the embedded resources parallel downloads more realistic.
a global parameter that let the user choose a custom value is fine BUT the
default value should also be increased.
BTW, did you know that JMeter is not a browser ? ;-)
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59029] httpclient PoolingConnectionManager has inappropriate
default values
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59029
--- Comment #2 from benoit.wiart@gmail.com ---
a connection pool is created for each user (thread) see HTTPHC4Impl#setupClient
So this is not about sharing connections across threads.
Modern browsers use more connections than the current JMeter default.
see
http://sgdev-blog.blogspot.fr/2014/01/maximum-concurrent-connection-to-same.html
Even for a single user, current defaults are not reasonable
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59029] httpclient PoolingConnectionManager has inappropriate
default values
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59029
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |p.mouawad@ubik-ingenierie.c
| |om
Resolution|--- |DUPLICATE
--- Comment #5 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Will be fixed within Bug 59034
*** This bug has been marked as a duplicate of bug 59034 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59029] httpclient PoolingConnectionManager has inappropriate
default values
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59029
--- Comment #3 from Sebb <se...@apache.org> ---
JMeter is not a browser.
JMeter threads behave more like a single browser tab. A browser with a single
tab does not need as many connections.
Unless you can show that there is a need to change the default, I think it
should be left as it is. If there is a need to change the default for a
particular test, then there should be a way to configure the values.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59029] httpclient PoolingConnectionManager has inappropriate
default values
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59029
--- Comment #1 from Sebb <se...@apache.org> ---
Each JMeter thread is intended to simulate an independent user.
So I'm not sure it makes sense to pool connections across threads.
In fact that was one of the issues with using the Java HTTP implementation - it
was not possible to control connection pooling.
The defaults seem reasonable to me for a single user.
--
You are receiving this mail because:
You are the assignee for the bug.