----- Original Message -----
From: "Scott Ferguson" <[EMAIL PROTECTED]>
> Resin/IBM 620 529 553 43 84
> Orion/JDK1.2 192 190 428 5 49
> Resin/JDK1.2 267 212 234 6 71
I just put in production a JSP app running on TomCat 3.1, which performance
looks very good right now (in a few months the system should grow
significantly in # of users, so maybe I'll need a commercial engine...).
Anyway, I see that you don't test Orion on IBM JDK. I suppose Orion
requires Java2 and you're running IBM 1.1.8. Why don't you try IBM 1.2.2,
it's available inside DirectDOM (you can grab this thing from AlphaWorks).
> Also, after a certain point, the servlet engine performance really doesn't
> matter. You'll be stuck with database overhead or your own code.
Well, this is true for a dumb server with low-level database code (e.g.
JDBC). Gotta use a persistence engine including a good object cache. Reads
vastly dominate creates & updates in most database apps, so all you gotta do
is not destroying your persistent objects immediately after they're used,
only to reincarnate them in the next millisecond when a new request comes.
Maybe even a decent JDBC driver with a good client-side cache would serve.
But I agree that the application code will outweight everything else, if
it's not a simple read-database-write-HTML toy.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
