: Re: HttpClient and CPU usage.
Busy wait has been fixed after 2.0a3 release. So, a recent nightly build
is needed. Besides, it turned out that Ken was using a rather old JDK
(1.2) which is known to have rather lousy JIT on Solaris platform. I
have already recommended Ken to upgrade both the JDK
original-
De: Ken Clark [mailto:[EMAIL PROTECTED]
Enviado el: miércoles, 26 de marzo de 2003 6:26
Para: [EMAIL PROTECTED]
Asunto: HttpClient and CPU usage.
I've built a b2b application using the commons HttpClient, and all works
extremely well. The problem is, however, that the app
What version of httpclient are you using?
I understand that a busy read loop was removed from httpclient a couple
of weeks ago. I'm not sure if this change was made for Alpha3, or whether
you have to go the daily builds to get it.
Tom
On Wed, 26 Mar 2003, Ken Clark wrote:
I've built a
Good call Tom, this is most definatly the problem!
As the 'busy loop' that has been fixed that you speak of would have caused
this EXACT occurance.
The bug caused HttpClient to continually call the Socket's 'int
InputStream-read()' over and over even though the socket is allready closed
(the
Busy wait has been fixed after 2.0a3 release. So, a recent nightly build
is needed. Besides, it turned out that Ken was using a rather old JDK
(1.2) which is known to have rather lousy JIT on Solaris platform. I
have already recommended Ken to upgrade both the JDK and the HttpClient
Cheers
Oleg
I've built a b2b application using the commons HttpClient, and all works
extremely well. The problem is, however, that the app is using up to 45% of
the CPU time ( as reported by various unix processes ( ps -aux, vmstat,
etc ) ). The customer has a Sun 4500, running solaris, with two processors.
