On Thu, 3 Jun 1999, Colin Burroughs wrote:
> Is anybody on this list currently using JSP on anything other than a low
> traffic Intranet? Have you guys at Sun done some load/performance
> testing, and is it in the public domain?
I've used a slightly different page compiler (GSP) on a large e-commerce
site. The framework itself holds up fine. You can definately scale the
application by throwing hardware at the problem. The main caveat is the
use of HttpSession. it's tempting to shove a lot of random stuff in there
because it's so easy to do. but if you have to restart a JSP server, or
if your load balancer moves a user from one server to another then you'll
probably be sad.
as long as you treat the session as a write through cache (where
session.putValue() calls are persisted somewhere), and you have a
mechanism for transparently reconstituting a session from this persistant
store, then you'll be in good shape. you can still use the session for
fast reads, but you're safe from restarts/session affinity problems.
this also requires that you not put anything too exotic in the session.
if you place a ref to an object that is the root of some large object
graph, it will certainly be difficult to ensure that the object graph has
been persisted completely at any given time.
but if you use the session as a hash of scalars (strings, ints, dates,
etc), then you'll be in good shape. you can also put more complicated
data structures there, as long as you're careful to persist on writes.
sorry if that's long winded (or obvious), but that's been the main issue
I've run into when scaling large servlet based sites.
-- James
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
