Thank everyone for your replies, it was inspring! > I am pretty sure most core component of CAS is multi-thread enabled, where do you get the info that CAS is thread-blocking all the way? I never questioned the fact CAS is multi-threaded. All I wanted to say that it is using the 20+ years old thread-per-request paradigm (vs asynchronous like Undertow or Spring Web Reactive), and it doesn't use any asynchronous storage features either. That means as long as you have 1000 requests per second, you likely have 1000s of threads of your system, which causes high CPU core contention and high latencies.
> well known large b2c deployments in telecom and gaming with scale around 20 million clients and millions of authentications every day. That's impressive enough, I assume some sort of distributed cache is used for ticket storage in this case? Of course load tests are planned, as this is cloud-hosted and we have to be cautious with costs. -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/3a30cac5-687f-4e28-962e-aae83ce771b5%40apereo.org.
