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)?

See https://apereo.github.io/cas/7.0.x/planning/Installation-Requirements.html 
and other related sections.


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.

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.

-- 
- 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+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/9d0072959fd54812d90bab33feb15fd6e59b1705.camel%40uvic.ca.

Reply via email to