Avoiding ExternalStore.load() on cache put for new random keys

[jugglingcats]

In our application we are tracking sessions using UUIDs. If an existing session isn't supplied by the client, we generate a new one and put it in the cache.

So we know when a put to the cache is a new entry or an update to an existing entry. It would give us a small performance benefit if we could have a putNew method call or similar (perhaps on AdvancedCache).

I wonder if anyone else would find this useful.

Thanks, Alfie.

[pruivo]

Hi Alfie,

If I understood correct, you want to avoid the CacheStore lookup during a put operation, right?

If so, you may want to use this Flag.SKIP_CACHE_LOAD (check the javadoc: Flag (Infinispan Distribution 6.0.0.Final API)). Usage example:

cache.getAdvancedCache().withFlags(Flag.SKIP_CACHE_LOAD /*, you can add other flags*/).put("newKey", "newValue");

Another possible flags you may check is Flag.IGNORE_RETURN_VALUES and Flag.SKIP_REMOTE_LOOKUP.

Cheers,

Pedro

[jugglingcats]

Perfect thank you - made a big difference!

UPDATE: for anyone stumbling across this thread, it's important to note that you should only use the return from getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES) for puts, and not for reading. If you use it for gets it won't attempt to read from the store and it'll be like you are just in-memory.