Load testing CAS for proof of concept.
Background:
* CAS release 6.6.13
* initializr build
* dependencies:
* support-ldap
* support-saml
* support-saml-idp
* support-hazelcast-ticket-registry
* support-hazelcast-monitor
* support-jdbc
* support-jdbc-monitor
* support-simple-mfa
* support-git-service-registry
* support-reports
* support-metrics
* support-discovery-profile
* support-consent-webflow
* support-surrogate-webflow
* support-surrogate-authentication-ldap
* support-throttle
* embedded tomcat server
* gradlew clean build setExecutable
* Red Hat Enterprise 7.9 selinux
* run as systemd service
* load testing with locust
The problem we are running into is system cpu usage during a load test.
Systemd-journal ramps to 100% cpu usage when we run a minimal load test(400
users). Has anyone running the embedded CAS seen similar behavior? Running
the same system on standalone Tomcat did not see similar behavior.
--
- 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/DS7PR17MB6730313FB7685692E0B183F7B4DDA%40DS7PR17MB6730.namprd17.prod.outlook.com.
