I've been working on updating from 3.2 to 3.3 and wanted to give memcached a try instead of JBoss. I read Scott's message about performance and we've had good success here with memcached for other applications. It also looks like using memcached instead of JBoss will simplify the configuration changes for the CAS server.
I do have the JBoss replication working with CAS 3.2 but pounding the heck out of it with JMeter will cause some not so nice stuff to happen. I'm using VMWare VI3 and configured an isolated switch for the clustering and Linux-HA traffic. I do see higher traffic levels coming to my cluster in the future, but I'm not sure if they'll meet the levels from my JMeter test. (I'm just throwing this out there because of the recent Best practice thread.) If I use memcached, is the ticketRegistryCleaner not needed anymore? I left those beans in the ticketRegistry.xml file and saw all kinds of errors. After taking it out it seems to load fine and appears to work, but I wasn't sure what the behavior is and I haven't tested it further. What if memcached fills up all the way? Does anyone have a general idea of how much memory to allocate to memcached with regards to concurrent logins and tickets stored? Thanks, Pat -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Patrick Hennessy ([EMAIL PROTECTED]) Senior Systems Specialist Division of Information and Educational Technology Delaware Technical and Community College =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
