[ http://jira.codehaus.org/browse/XFIRE-743?page=comments#action_79575 ] Holger Hoffstätte commented on XFIRE-743: -----------------------------------------
We're having a similar problem in Mule and there is no single "best" way to even give an initial value without knowing what to optimize for: service latency, throughput, number of endpoints..?? Even though you may have 10 endpoints, only 3 of them might be "hot" so you'd need more connections for them; in other scenarios, all 10 endpoints might be used evenly. On a single-CPU box this is almost irrelevant (to a certain degree); with 2, 4, 32 or more "CPUs" (e.g. on a Niagara box) all these assumptions become completely wrong again. As far as I can tell commons-httpclient has no hooks to determine the effectiveness of its pool (otherwise one could come up with a self-adjusting service policy, ala cachedThreadPool that adjusts itself depending on load) so the simplest way to fix this is to bump up the default number to ~4-8 (assuming single CPU dev workstation/low-end server) and let the user configure anything else. > HttpClient only does 2 connections by default > --------------------------------------------- > > Key: XFIRE-743 > URL: http://jira.codehaus.org/browse/XFIRE-743 > Project: XFire > Issue Type: Bug > Reporter: Dan Diephouse > Assigned To: Tomasz Sztelak > Fix For: 1.2.3 > > > the multithreaded connection manager only opens two threads by default in the > http connection manager. This can cause a major bottleneck for multithreaded > applications. We should bump this up and make it configurable more easily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
