Yes, exactly, I was thinking the same thing about HTTP 1.1 (connection reuse instead of open, close, open...) vs. HTTP 1.0, though I am not 100% certain that even with 1.0 the connection is cosed and reopened. I should have run netstat... oh well.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- From: Doğacan Güney <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, April 18, 2008 2:49:03 PM Subject: Re: protocol-http vs. -httpclient, HTTP 1.1 vs 1.0 Hi, On Fri, Apr 18, 2008 at 7:27 AM, <[EMAIL PROTECTED]> wrote: > Hi, > > Has anyone done any performance testing with protocol-http vs. > protocol-httpclient? > > I just switched from protocol-http to protocol-httpclient and I switched > from useHttp11=false to useHttp11=true and I *think* this resulted in higher > download speed. I remember changing to protocol-httpclient a while back, but I didn't notice any speed-up. But then again, it is just too damn difficult to measure download speed because it is not a controlled experiment (maybe when you switch to httpclient, people start hammering those servers you are about to fetch from, etc) That being said, I remember reading that it is better to keep a connection open (by using HTTP/1.1) than opening a new connection for each request. I am not sure, but I think it is also easier on the server too.... > > > I also upgraded httpclient from 3.0.1 (which is in the trunk) to 3.1 > (which is the latest stable 3.* release) and things seem to be working just > fine. It may be a good idea to update all external libraries before we release 1.0 if they are stable. > > > Otis > > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > -- Doğacan Güney
