Mailing-List: contact httpcomponents-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <httpcomponents-dev@jakarta.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <1193404378.4721e7da154ce@webmail.quies.net>
Date: Fri, 26 Oct 2007 15:12:58 +0200
From: "Pascal S. de Kloe" <pascal@quies.net>
To: HttpComponents Project <httpcomponents-dev@jakarta.apache.org>
Subject: Re: Performance
References: <1193402814.4721e1be31d5a@webmail.quies.net>
 <1193403884.18403.52.camel@okhost>
In-Reply-To: <1193403884.18403.52.camel@okhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.6

Hello Oleg,


> (2) Can you give us a little more details regarding the performance
> problems you have been observing?

The latencies they are experiencing are somewhere between 37 and 100 ms with 10
threads doing 100 HTTP GET calls each. However once they move to a 100 threads
with 1000 calls each the latencies go up from 1500 to 15000 ms!

I guess this has something to do with the extensive use of synchronized methods?


> (3) Give us a little more details about your application. At the very
> least what version of HttpClient is being used.

The application is a server doing lots of small HTTP GET requests with one of
the latest 3.x versions.

> Just for the record, HttpClient 3.x codeline has numerous design issues
> with its core components but I am not aware of anything that may lead to
> "some serious performance problems"

For this server 40 ms is a serious performance problem. That's why I wanted to
know how much performance tuning you'd like. ;)


Thanks for your quick reply.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org