All good points. Startup time with 15-20 applications deployed would also be more interesting than pure container startup - given how that can easily take 5+ minutes, a long time in a production environment which just suffered from PermGenSpace problems and had to be restarted.
/Casper On Dec 18, 6:48 am, carl <[email protected]> wrote: > It's funny how all the benchmarks compare startup time. That's > important when developing, sure, but when running a production server > does it really matter that much? > > And how important is the disk footprint? Although, I do really like > Jetty for making self-contained webapps with the container baked in. > In that usage, the small disk footprint is a big win. > > Ram used by the container itself is interesting, but what I'd really > like to see is a comparison of runtime performance of servlets in each > container. Latency, throughput, etc. I wonder which would win for lean > and mean servlet containment? Jetty, Tomcat or Glassfish? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
