Infinispan Caches Compared and Contrasted
Caches are crucial technologies for scaling your enterprise upward, learn which best suits your needs in this compare and contrast article.
Join the DZone community and get the full member experience.Join For Free
See Gartner’s latest research on the application performance monitoring landscape and how APM suites are becoming more and more critical to the business, brought to you in partnership with AppDynamics.
Infinispan local caches have several features that make it more than just a map—expiration and eviction, listeners, statistics, transactions, cache stores, and so forth. However, this comes at a price—due to all the hooks and object allocation, plain
ConcurrentHashMap is faster than local cache.
There are applications that need something in between—great performance but some of those features, too. In our case, the motivation were internal caches in Hibernate Second Level Cache. Therefore Infinispan 8.0.1.Final brings the simple cache —alternative implementation of the
AdvancedCache interface optimized for maximum performance when you need just the basics.
The table below shows which features are available in simple cache:
|Basic map-like API||✔|
|Cache listeners (non-clustered)||✔|
|Persistence (cache stores and loader)||✘|
|Map Reduce Framework||✘|
|Distributed Executors Framework||✘|
|Store as binary||✘|
Configuring a simple cache is as simple as adding one attribute to the XML configuration:
<local-cache name="mySimpleCache" simple-cache="true"> <!-- expiration, eviction, security... --> </local-cache>
While configuration schema allows to set up the unsupported features, doing so results in an exception when the cache is created.
You can also configure simple cache programmatically:
CacheManager cm = getCacheManager(); ConfigurationBuilder builder = new ConfigurationBuilder().simpleCache(true); cm.defineConfiguration("mySimpleCache", builder.build()); Cache cache = cm.getCache("mySimpleCache");
So, what kind of performance improvement can you expect? We had run a basic (single-threaded) benchmark using JMH and this is what we got:
|Implementation||get() (operations/s)||put() (operations/s)|
This gives us about 5✕ speedup for reads and 6✕ for writes. Your mileage may vary, but it's certain that simple cache provides substantial performance benefits.
So, if your use-case allows it, try out simple cache and let us know. It's as simple as one configuration attribute!