Hi Jan, Thanks for following up. I'm glad it doesn't seem to occur in Restlet code.
I don't know the constraints of your project, but you could also attempt to run it as a standalone Restlet application, for example with Jetty connector, to see how it behaves compared to Tomcat. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : news [mailto:[EMAIL PROTECTED] De la part de Jan Envoye : jeudi 2 octobre 2008 23:43 A : [email protected] Objet : Re: Spiky response time problem again Hi Jerome, 1. When the server was not responding, YourKit displayed all Idle threads. There were no request failed or rejected, it was just very slow response. 2. I have tried the same application with Restlet 1.1. Sightly better, but I still see chocking. For my test environment, slow requests (which were longer than 5 seconds) were around 50 out of 36K requests. 3. Actually after more testing, I don't think this is the problem from Restlet, at least not only Restlet. Because I took off all the Restlet code and did the same application only with Servlet, the same spiky response time was still happening. Now I think it was probably because of Tomcat or JVM. The interesting thing is that when I moved the application from a Windows box to a Linux box, the problem went away. I only got 1 slow response out of 36K requests. Any input? What would be the cause for such big difference? (Please note the Linux box has 4G RAM and quad core, Windows box has 1G RAM and dual core) I could package how I tested it to a WAR. Where I could send it to? However, again, it doesn't seem to me a Restlet problem now. Thank you very much. Jan
