> -----Original Message-----
> From: Romo, AlX P [mailto:[EMAIL PROTECTED]]
>
> Though OS and JDK's are independent considerations, I am looking for
> subjective answers on high performance OS\WWW\(latest JDK\JSDK)
> combinations.
Right, but the best servlet engines run out of process from the native web
server, a la JRun (some partiality there, but where are you going to find a
totally unbiased opinion?). So in those cases the web server has nothing to
do with the performance of the JVM, JSDK or the servlet engine. The
greatest limiters to performance are going to be the user load you are
handling and the servlets you run and what they do and how they do it. RMI
and database access can take a long time, depending on environmental
conditions and coding issues. And then there's how many and the nature of
the CPUs you have and what servlet engine you're using, whether it supports
the latest Servlet API, and so on.
> I want to know which combos
> work best in a
> WWW situation.
>
> The volano report doesn't reflect a WWW situation. It is a
> client \ server
> test for java JDK's tested against the volano chat package.
The WWW is all client/server, and a JVM is a JVM no matter what it's doing
(this may be somewhat naive, but theoretically it sounds good), so I don't
see your point.
Scott Stirling
Allaire Corporation
JRun: http://www.allaire.com/developer/jrunreferencedesk/
Allaire Knowledge Base:
http://www1.allaire.com/Support/KnowledgeBase/SearchForm.cfm
===========================================================================
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