Looks I did not receive the response because I wasn't subscribed. The reason I did not put my performance results down, was because I thought I am having the same kinda problem as was earlier reported. I was interested in what happened to those problems and whether a solution was found.
But anyways, here are all the details I have. I am using 2.0 final version of HttpClient. I did my tests by making POST requests to a local server for 100 times(I have done 1000 times too, got similar results). I am sending and receiving XML documents and doing some additional processing and I am using j2sdk1.4.2_05. If I use the MultiThreadedHttpConnectionManager with 20 maxConnections, it is giving me about 8ms per request. And if I use the SimpleHttpConnectionManager as I described, I get about 6ms per request. And if I do not use HttpClient and use the java.net.HttpURLConnection, I get about 5.4ms per request. That means that even if you do not check for stale connection in HttpClient, the HttpClient is slower than the JDK. I do not remember which earlier releases I used. I only remeber that it did not have the rcX attached to it. I am not sure if it matters now. I guess, the only thing we are concerned here is whether we can get HttpClient performance better than JDK or not. If yes, then how do we get it? I guess some other folks had a similar problem before. Wondering if a solution to the problem was found or not? Hope this helps you in understanding the problem. -Zulfi -----Original Message----- Subject: HttpClient performance Date: Fri, 20 Aug 2004 08:39:21 +0100 From: Kalnichevski, Oleg <[EMAIL PROTECTED]> Zulfi, If you expect us to react on this report, you have to be a little more specific on how exactly you measured the performance, exactly what kind of HTTP methods your tests included, exactly what pre-release-candidate you are referring to, and what exactly you mean by "but it is still slower than using JDK-1.4.2". Do you actually mean using HttpURLConnection? Raw socket? Something else? I'll run a few tests of my own to see if I get significant difference in terms of performance between HttpClient 2.0alpha3, 2.0.1, CVS HEAD (post-3.0a1) and HttpURLConnection Oleg -----Original Message----- From: Zulfi Umrani [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 7:06 AM To: [EMAIL PROTECTED] Subject: HttpClient performance Hi, Just wanted to get the latest information on the performance issues reported earlier. I have gone through the below emails from Archive, but could not get a definite solution to the performance problem. Wondering whether a definite solution was found and whether there is a patch available. We tested the performance using pre-release-candidate version of HttpClient(2.0) and it was much better than the release-candidate versions and the final 2.0 version of HttpClient. Please note that I did try using the SimpleHttpConnectionManager and calling the setConnectionStaleCheckingEnabled method with false argument. The performance does improve, but it is still slower than using JDK-1.4.2. I will appreciate if someone who knows the solution can respond. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=781750 http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=781859 http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=781909 http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=779703 Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]