Re: [RELEASE STOPPER] 2.0rc1 is no-go due to a serious performanceissue

2003-07-30 Thread Michael Becke
Okay. I will apply it tonight. Mike Kalnichevski, Oleg wrote: Mike, The patch looks fine to me. I think it is good to be committed to both the 2.0 branch and the trunk. Oleg -Original Message- From: Michael Becke [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 06:12 To: Common

Re: [RELEASE STOPPER] 2.0rc1 is no-go due to a serious performanceissue

2003-07-29 Thread Michael Becke
Oleg, I should have time to take care of these two items tonight. I will let you know how far I get. You may have to take over if I don't finish this evening. Mike Oleg Kalnichevski wrote: All right. I believe the crisis can be declared dealt with. Once additional DEBUG log entries for the

Re: [RELEASE STOPPER] 2.0rc1 is no-go due to a serious performanceissue

2003-07-29 Thread Oleg Kalnichevski
All right. I believe the crisis can be declared dealt with. Once additional DEBUG log entries for the multi-threaded connection manager are introduced and option to disable 'stale' connection check is added, we will proceed with the 2.0 Release Candidate 1 release. Mike, I see connection pooling a

Re: [RELEASE STOPPER] 2.0rc1 is no-go due to a serious performanceissue

2003-07-27 Thread Oleg Kalnichevski
All right. I have found the culprit. It is our much loved & loathed (depending upon the circumstances) HttpConnection#isStale(). By making this method always return false the average response time goes down from 23ms to 6ms using the test app posted below. Thoughts? suggestions? Oleg On Su

[RELEASE STOPPER] 2.0rc1 is no-go due to a serious performanceissue

2003-07-27 Thread Oleg Kalnichevski
Folks, Sadly enough, I have to confirm the performance problem reported by Todd Wolff <[EMAIL PROTECTED]>. HttpClient's performance as of 2.0 beta-1 degraded almost four-fold compared to 2.0 alpha-3. The problem is fairly easy to reproduce: import org.apache.commons.httpclient.*; import org.apache