esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <>
Subject RE: Details from Stax Load test
Date Fri, 09 Jan 2009 04:54:33 GMT
@David: is the REST-API functional in the present apache version?. Could we use this for performance
tests? I'd like to wait for the new scala library before testing but I'd curious to know if
the REST-API has changed in any way.


From: David Pollak []
Sent: Thu 1/8/2009 06:32
Subject: Re: Details from Stax Load test

Tomcat is a less than optimal platform for high concurrent load.  It does
not have the same continuations mechanism that Jetty has.  All my high load
tests are done on Jetty.  With that being said, ESME's long polling for the
HTTP APIs does not take advantage of Jetty's continuations yet.  That's on
my to-do list, but to date has not been a high priority.

Another issue is that there's a problem with Scala Actors and memory in
Scala 2.7.2.  The Scala team is releasing Scala 2.7.3 this week or next to
cure the memory problems.

Also, the continuations that Jetty currently supports are part of the
Servlet 3.0 spec and should be part of NetWeaver this year.



On Wed, Jan 7, 2009 at 8:54 PM, Hirsch, Richard

> Here are some details for a very first performance test on Stax for the
> ESME server. Daniel tried with 1000 concurrent connections and then the
> server started having some problems. Take a look at the enclosed stack trace
> and you will see that towards the end there were problems with the threads.
> I'm also enclosing a picture of the Stax performance indicators. I don't
> know the exact dimensions of the test but I'm sure Daniel will provide them
> soon.
> Load tests are critical if we are to succeed in enterprises. They are also
> critical when customers need sizing information. I assume that they should
> also be useful for the lift framework.
> D.
> ________________________________
> From: Spike Washburn []
> Sent: Wed 1/7/2009 23:13
> To: Hirsch, Richard
> Subject: Re: Stax account
> The activity died back down for a bit, but then the app started sucking up
> memory and CPU like it was stuck in a loop.  When we checked the logs, we
> saw it was throwing out of memory exceptions.  Since the app was clearly in
> a death spiral, we took a JVM stack dump and then restarted the app.  I have
> attached the last part of the appserver log if you want to review it.
> Also I noticed from the log that your app is getting warnings about
> including the servlet-api-2.5.jar in WEB-INF/lib. This is not necessary
> since the Servlet API classes are part of the classpath provided by the
> appserver.
> Before your app died we were seeing upwards of 1000 concurrent connections
> to your app.  Please let me know if you were expecting this load or if it
> was some kind of external attack against your app.
> Thanks,
> Spike
> On Wed, Jan 7, 2009 at 1:09 PM, Spike Washburn <>
> wrote:
>        Hi Dick,
>        We just noticed a major spike in activity on your application (id:
> DickHirsch/esmecloudserver).  I just wanted to check with you to see if you
> were doing some load testing or if this was some kind of external attack on
> your webapp.
>        Thanks,
>        Spike

Lift, the simply functional web framework <> 
Collaborative Task Management <> 
Follow me:
Git some:

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message