> From: Andrew R Feller [mailto:[EMAIL PROTECTED] > Subject: RE: Storing sessions to disk like Apache HTTP server > > The student registration application's load consists of > thousands of students pounding at a handful of servers > constantly in hopes they can schedule their classes before > they fill up.
Yes, I've watched my son do it at his school. (We used to do that with punched cards, 40 years ago. My then-roommate wrote the first automated class registration system at Georgia Tech around that time. Response time was measured in days :-) > 1. Does Tomcat keep all session information strictly in > RAM or does it swap out to disk? The standard session manager uses only the Java heap. The persistent manager sounds like it does what you want, but it's "considered experimental" (and has been so for a long, long time). I guess it's up to you if you want to play with it. The doc is here: http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html > 2. What commonly used formulas are there to determine sufficient > RAM based on load size? There aren't any because the amount of heap used is very sensitive to the specific applications deployed. You'll need to measure it in a test environment, scaling up the number of sessions to see the effect on the heap. > 3. Is it better to split large clusters into smaller ones with > a few nodes replicating to the other clusters? No experience here. Perhaps Filip has suggestions. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
