> Does anybody know of any performance figures of servlets vs CGI and
> servlets vs .asp with Active X. I just want to see the rough speed
> difference of the multi-threaded vs the multi-process model in a real-life
> application. I've read the book figures but rarely see differences of that
> magnitude in real-life.
This has been discussed quite a few times on this list, you might want to go
back over the archives to see those discussions.
Basically threading performance is much better... but this is a very
simplistic statement. There are lots of ways of implementing HTTP based
servers (one process per request, one thread per request, select based io)
and each of these have advantages in different scenarios.
eg:
- one process per rquest
if you need to dynamically get stuff from some external process it's quicker
to use per process stuff as you might not need to pay the process startup
cost
- one thread per request
best for servlets and JSPs generating dynamic data
- select based io
best where you have a very clearly defined process that can be easily shared
amongst lots of io streams, eg: static page servicing.
So, to sum up, it's really impossible to answer your question because the
right thing to use depends on the particular circumstance.
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
