Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Servlet response times
Thank alot for replying.

-- We are not using SSL. I am using JRE 1.6. Dont see any problem with the Java app as such. Just spike in jetty response times. In my case i have a java app that has Jetty embedded.
-- I checked GC that was my first guess too. But GC logs are perfect. Around 4 Young scans per minute and each scan taking ~4 ms. Have not seen full GC in days. Also the time stamp of servlet response times spike does not match GC time stamps.







On Thu, May 30, 2013 at 1:58 PM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:
Jetty moved to eclipse ages ago, hence this being an eclipse mailing list and all...


And typically those issues are from things like a stop the world garbage collection, so I would start there.

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Thu, May 30, 2013 at 3:53 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
So we are using BlueBox which depends on Jetty 6x. And so i am stuck with Jetty 6x. Can anyone throw some light on the direction i should follow for my investigation ?


On Thu, May 30, 2013 at 1:39 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I dont see that many releases post 6.1.26



On Thu, May 30, 2013 at 1:34 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
Sorry, but you'll find few people to help with Jetty 6.1.26, it is very old and was End of Life'd back in 2010.
There's been well over 150 stable releases of Jetty since Jetty 6.1.26.

Consider upgrading.


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts


On Thu, May 30, 2013 at 1:26 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I have enabled Jetty to log response times. I notice that in our production or load test environment, we have a temporary spike in Jetty response times. Jetty logs would trace response times of 200-400ms for a webservice that would normally take 2 ms. I did not notice particular burst of traffic at that time.

Further i traced through servlet debug logs that we have put in our application. And i never found a log that would reflect the servlet processing took more than 3 ms. For every single invocation which Jetty would report response time as 200-400ms, servlet debug logs would only show 2-3ms of processing.

I am guessing that once servlet execution starts it takes only 2-3 seconds. And latency is due latency between receiving of a request to scheduling of request in a sevlet. So i tried to increase threadpool, even though it did not make sense to increase thread pool. As my traffic comes @ 50-100 RPS and if it takes 2-3 ms to process a request 10 default thread count should be enough. But i did increase the thread count to 20 and lowThreadCount to 25. But still saw spike in response times in jetty logs.

Can anyone throw some light or show some path for further investigation ? I am using jetty-6.1.26


Thanks !



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev




_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


Back to the top