Previously I talked about improving the SSL performance in Tomcat simply by upgrading the JVM. Here we have a somewhat not-to-scale chart showing how we did in a “real world” test. Last night at 6pm an application opened up and sent a flood of users to our authentication service (CAS). Last year we could not handle the flood. CAS stalled, which caused a flood of calls to the help desk. In the business, we call that less than optimal.
We’re rolling CAS on Java 6 now and SSL performance is no longer an issue.
1 response so far ↓
1 Scott Kodai // Apr 2, 2008 at 1:53 pm
Since we’re hoping to rely on CAS for our self-service application, I’m glad to see it’s doing well.
Leave a Comment