Thanks all for the feedback. It looks like management is going allocate some time so I can do some benchmarking and tuning.
I think I am going to take this opportunity to completely revamp the infrastructure. 1. Replace Sun Appserver reverse proxy with Apache. 2. Deploy CAS on Tomcat instead of Glassfish 3. Run everything on Redhat instead of Solaris 4. Run everything on VMs for testing and then move to dedicated servers for production. From: Scott Battaglia [mailto:[email protected]] Sent: Thursday, March 08, 2012 7:08 AM To: [email protected] Subject: Re: [cas-user] Stress testing CAS in production At Rutgers, we would see 5000+ logins in a five minute period with each of the two servers barely reaching 10% CPU utilization (that is with both of them running CAS and Memcache). I believe that was with no noticable latency increase. There are of course trade offs to each backend storage mechanism you use (as you're finding out :-)) On Thu, Mar 8, 2012 at 3:17 AM, jleleu <[email protected]<mailto:[email protected]>> wrote: Hi, Just to give you some more figures. We are handling ten times more logins at peak hour : 140 k logins with three servers (Tomcat 6) BUT our tickets storage is Memcached and not a database. Our CAS servers did not run slowly under load. We were using Oracle but we couldn't handle so many logins. Marvin is right : - you have to distinguish between logins and service accesses (we have three to four times more service accesses than logins) - you have to bench. The number of sessions can come into play in a drastic way : as each login page starts a web session, you can run out off memory very quickly. In our case, the number of web sessions was such a bottleneck I created a hook to kill web sessions just after login. Best regards, Jérôme -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
