On 7/8/05, Jesse Vitrone <[EMAIL PROTECTED]> wrote:
> Obviously nobody has limitless memory and performance, that's why I'm
> wondering if there is a rule of thumb for figuring out if it's going to be
> too much for the server to handle. Is 100 users on a decent sized app going
> to kill the server if it's all in the session? Is 200?
That quote about early performance optimisation being the root of all
evil springs to mind 8-)
My probably overly simplistic view is to be miserly and store the
barest minimum on the session and let hibernate, the connection pool,
the db and the os do their thing with caching. The only thing I'm
currently putting on the session is basic stuff like the current user
and the backing beans for datatables that have links in them that I
seem to have to put in session scope but I'm going to put something in
that goes through and clears them out from time to time.
This way I'm keeping everything pretty simple and consistent and if I
have a speed problem I'll think about session or application beans
later. Bear in mind with this that compared to what you are doing I'm
only working on very small intranet/extranet apps ("look Pa, we've got
10 concurrent users!").
My other thoughts on this are by the time the jvm loads Tomcat,
hibernate, all the commons stuff that goes with it, XML parsers,
logging, myfaces and other stuff I'm using like digestor there is a
fair number of objects in there already. In my case because I'm
working on a standalone app, I also run Mckoidb in the same jvm as
the app so I sometimes think things could be getting pretty full.
Regards,
Adrian
Auckland, NZ
