> I would love to see test between the different JSP and Servlet engines. But please,
>no more informal test.
> There are people out there that make haste decision based on stuff like this.
Fair enough.
I was only testing Tomcat by itself on a machine that should be
"sufficient". In all likelyhood, there's some sort of degenerate
case I'm missing, like an error in the load tester (which I think
someone pointed out already...) or some wierdness with local
versus network sockets - anyone who is load testing from the
server machine itself is definitely going to get wierd results,
yes, I understand this.
Nevertheless, it is a bit curious to see so many connections
being refused/dropped, regardless of the setup. Just curious.
Ethan
> There are just too many unknowns in your test:
> - What versions of the engines did you use.
> - How much memory does your computer have.
> - Which engine got loaded first (e.g. hogging RAM), did you try starting them the
>other way around.
> - What happened when you ran the test one engine at a time.
> - Which settings did you use
> - What web server configuration did you use for tomcat, apache or the java server.
> - How did the engines scale to bigger JSP pages than hello.jsp.
> - Did you find any reasons for the dropped requests?
To the last one - no.
--
Ethan Henry [EMAIL PROTECTED]
Java Evangelist, KL Group http://www.klg.com
"Software Development Productivity"
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
