Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 14582 invoked from network); 30 Sep 2002 07:40:52 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 Sep 2002 07:40:52 -0000 Received: (qmail 18207 invoked by uid 97); 30 Sep 2002 07:41:43 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 18191 invoked by uid 97); 30 Sep 2002 07:41:42 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 18179 invoked by uid 98); 30 Sep 2002 07:41:42 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: =?iso-8859-1?Q?Aur=E9lien_Pernoud?= To: "'Jakarta Commons Developers List'" Subject: RE: [HttpClient] Bad performance with multiple request to same host ? Date: Mon, 30 Sep 2002 09:39:06 +0200 Message-ID: <9E035BE80785AA4EAA456959ECB4A30D017610DE@nt036.an.sopra> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <9E035BE80785AA4EAA456959ECB4A30D02B73565@nt036.an.sopra> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I agree with this, but when you're using an Intranet HTTP Server and you're making all requests via httpclient, 2 is a ridiculous number... Currently the httpclient i'm using can manage up to 200 people between two intranet servers, so if I dindn't increase the total connections allowed they would wait hours for page to show. And performances are here, nice work from the httpclient team ! The idea of a configuration is nice, and default set to 2 is alright. Although a getter on the httpconnectionmanager would allow developpers not to overpass the original httpmulticlient and to manage their connections better. Thanks for considering my request. Aur�lien Pernoud > -----Message d'origine----- > De : Ortwin Gl�ck [mailto:ortwin.glueck@nose.ch] > Envoy� : lundi 30 septembre 2002 09:33 > � : Jakarta Commons Developers List > Objet : Re: [HttpClient] Bad performance with multiple request to same > host ? > > > From RFC2616: > > > Clients that use persistent connections SHOULD limit the number of > simultaneous connections that they maintain to a given server. A > single-user client SHOULD NOT maintain more than 2 > connections with any > server or proxy. > > These guidelines are intended to improve HTTP response times > and avoid > congestion. > > > We can, however, introduce a configuration key for this in > the (future) > config architecture of http client. Default will be 2 per client. > > Odi > > Aur�lien Pernoud wrote: > > Personnaly I've been overwriting the HttpMultiClient > (copying it and using > > mine) and using my own HttpConnectionManager on which I > simply increased the > > total number of allowed connections on a site this way : > > > > private HttpConnectionManager mgr = new HttpConnectionManager(); > > mgr.setMaxConnectionsPerHost(100); > > > > This way I allow 100 connections to the host, and > performances are better. > > > > But I think that in HttpMultiClient their should be getter on the > > connectionmanager that is private :-( > > > > Well now that we are two users interested, maybe they will > modify it ? > > Someone can please tell us from commons-dev ? > > > > Thanx, > > Aur�lien Pernoud > > > > > -- > To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: