Scott, with what you shared, about how many users are you talking about? On Thu, Oct 1, 2009 at 9:35 PM, Scott Battaglia <[email protected]>wrote:
> On Thu, Oct 1, 2009 at 5:48 PM, Curtis Garman <[email protected]>wrote: > >> Is it typical for your production server to set up a JpaTicketRegistry or >> something similar? > > > Anyone who wants seamless failover/high availability generally applies a > clustered solution. We ran for a number of years with a hot-spare but opted > to move to a cluster to make people feel more comfortable with relying on > CAS. > > > >> Anyone know how much stress the default ticket registry places on tomcat? >> >> Not much. We used to run it on a Sun V120 which worked for everyday > stuff. It even handled beginning semester crush pretty well (once we got it > on a good JVM with some tuned settings). Web Registration period would have > killed it. We ran it on a V240 for a while with no issues (that was fine > for Web Registration). Now we actually run it on two T5120s along with > Memcached (for the cluster) and CPU utilization barely hits 10% during web > registration. All other times its like 3%. > > > >> Curtis Garman >> Web Programmer >> Heartland Community College >> >> -- >> 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 >> >> > -- > 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 > > -- 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
