Administration guide > Tune and performance

Tune the dynamic cache provider

When you register a change event listener with the dynamic cache provider and generate a ChangeEvent instance, there is overhead associated with deserializing the cache entry so the value can be put inside the ChangeEvent. Setting this optional parameter on the cache instance to true skips the deserialization of the cache entry when generating ChangeEvents. The value returned will either be null in the case of a remove operation or a byte array containing the serialized form of the object.

InvalidationEvent instances carry a similar performance penalty, which you can avoid by setting... = true

By default, the WXS dynamic cache provider compresses the cache entries in memory to increase cache density. which can save a significant amount of memory for applications like servlet caching. If you know that most of the cache data will be not be compressible, consider setting this value to false.

Parent topic:

Tune and performance

Related concepts

Operating systems and network tuning

Plan for network ports

ORB properties and file descriptor settings

JVM tuning for WXS

Use WebSphere Real Time

Related tasks

Configure failover detection

Tune the cache sizing agent for accurate memory consumption estimates

Related reference

Operational checklist


Search Tips   |   Advanced Search