Help With Performance Optimisation. CAS 6.6.x

157 views
Skip to first unread message

Vaibhav GPT

unread,
Feb 6, 2024, 3:19:15 AM2/6/24
to CAS Community
Hi,
I'm using CAS version 6.6.x with Zoom for authenticated Meetings. The CAS Server is running behind a proxy server.
Following is configuration of CAS Server and Proxy Server : 8 Core with 8 GB Ram.

Whenever there is a load of more than 50 users per second the CAS perfromance degrades significantly and the site becomes unreachable 

I have also tried implementing throttling but I have not got a breakthrough cas.authn.throttle.bucket4j.enabled=true
cas.authn.throttle.bucket4j.bandwidth[0].refill-count=50
cas.authn.throttle.bucket4j.bandwidth[0].capacity=50
cas.authn.throttle.bucket4j.bandwidth[0].duration=PT1S

Also i have tried increasing the tomcat configuration

server.tomcat.accept-count=500
server.tomcat.max-connections=8192
server.tomcat.max-keep-alive-requests=100
server.tomcat.threads.min-spare=100
server.tomcat.threads.max=600

Any help or suggestions on how can i make it work.  I'm expecting a user load of about 150-200 users per second.

Ray Bon

unread,
Feb 6, 2024, 8:19:20 AM2/6/24
to cas-...@apereo.org
Is the issue with tomcat's ability to handle traffic or cas's ability to process requests?
How much memory is allocated to tomcat?
What are you using for ticket storage (in memory storage will be faster than database, etc)?



Ray

On Tue, 2024-02-06 at 00:08 -0800, Vaibhav GPT wrote:
Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Vaibhav GPT

unread,
Feb 6, 2024, 9:44:51 AM2/6/24
to CAS Community, Ray Bon
Hi ray,
we are using the embedded tomcat with CAS and we are using in memory storage for ticket.
I believe there is issue with cas's ability to process requests.

Ray Bon

unread,
Feb 6, 2024, 9:51:39 PM2/6/24
to gptva...@gmail.com, cas-...@apereo.org

To eliminate some points of contention:
1. set up a file system store of services, https://apereo.github.io/cas/7.0.x/services/JSON-Service-Management.html (or in memory).
2. file system store of users, https://apereo.github.io/cas/7.0.x/authentication/Permissive-Authentication.html (or add to the default list: cas.authn.accept.users=casuser::Mellon,hsimpson::password,wsmithers::password,mburns::password)

Search this user list for mentions of cas performance. 

Ray

Vaibhav GPT

unread,
Feb 12, 2024, 6:49:22 AM2/12/24
to CAS Community, Ray Bon, gptva...@gmail.com
Thank you Ron for the information but I have found the issue. 

Looks like the embedded tomcat in CAS is responsible for high cpu usage. When I switched to a standalone tomcat it was working as expected. 

I performed load test of 1500 users with 200 users per second logging in at same time. 

Also found this as well https://groups.google.com/g/jasig-cas-user/c/K7gf8hDbNPI

Dmitriy Kopylenko

unread,
Feb 12, 2024, 8:07:06 AM2/12/24
to cas-...@apereo.org
Which exact version of CAS (and the embedded Tomcat that it carries)?

D. 

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/fe8c7e3c-29e4-4830-b45d-e7f7d7aada85n%40apereo.org.

Dmitriy Kopylenko

unread,
Feb 12, 2024, 9:34:56 AM2/12/24
to CAS Community
Ok. Cause I know that there was a performance related regression in tc 9.8.1 delivered in CAS 6.6.13

You might want to try the latest in the 6.6.x series (I believe it’s 6.6.15) to see if it makes a difference. 

D. 

On Mon, Feb 12, 2024 at 08:24 Vaibhav GPT <gptva...@gmail.com> wrote:
cas 6.6.11
tomcat 9.8.0

Vaibhav GPT

unread,
Feb 12, 2024, 9:34:56 AM2/12/24
to CAS Community, Dmitriy Kopylenko
cas 6.6.11
tomcat 9.8.0

On Monday, February 12, 2024 at 6:37:06 PM UTC+5:30 Dmitriy Kopylenko wrote:
Reply all
Reply to author
Forward
0 new messages