Hello We continue to see issues around CAS performance in conjunction with a remote LDAP server.
First, we have read in this forum from several contributors that CAS performance exceeds the performances of its services. In an effort to understand why CAS is not performing at the levels others have reported, we are providing more details of our CAS implementation. Tests: Tests show that CAS plateaus at 9 *simultaneous* login attempts. At that point, the tester will aggregate logins and continue to push them through, but at some point the multi-tasking slows down to the point that Apache times out. The tests were isolated to authentication to confirm that communicating to client services did not affect the login rate. During tests, the CPU and Memory consumption remain at low levels. The priority of the task is set high enough to be handled immediately. There is nothing that suggests the disk may be thrashing due to swapping. CAS Server: - CAS is run on a VM hosted upon RHEL 6, with 4G memory, 1G PermGen, Allocated disk space for CAS is 1008M while total logging is 3G - Tomcat 6 is the web server - Authentication is handled via a remote AD LDAP server - Apache handles SSL encryption/decryption between the user and CAS. AD Server: The AD environment is not clustered, so the load is not being balanced. -- Linda Toth University of Alaska - Office of Information Technology (OIT) - Identity and Access Management 910 Yukon Drive, Suite 103 907-450-8320 Fairbanks, Alaska 99775 [email protected] | www.alaska.edu/oit/ -- 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
