So we move to Memcached solution.... However, the
default serialization mechanism brought by the default Memcached CAS
implementation uses the Java serialization with compression, which is
not really performant in CPU and finally serialized size. We move to
Kryo also and get really better results.
Thanks for your thoughtful feedback, Jérôme. Glad to know other folks
have looked into serialization issues in depth.
I would recommend to use synchronous transcoder in Kryo
as using asynchronous transcoder generates CPU bursts and erratic
behaviours (I also remember that the pool size for asynchronous
transconding could not be extended easily).
Are you referring to the async support that's enabled by default in
MemCachedTicketRegistry, but can be disabled via
#setSynchronizeUpdatesToRegistry(true) [1]? Or something else?
Thanks,
M
[1]
https://github.com/Jasig/cas/blob/master/cas-server-integration-memcached/src/main/java/org/jasig/cas/ticket/registry/MemCacheTicketRegistry.java
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
