|
In cloud-tm the proposal is that options like {@Basic(fetch=LAZY)}
should be dynamic, so that a pluggable optimizer strategy could change them at runtime from measured behaviour.
Similarly, the cost of looking up entries which are actually null is high: in Infinispan for example the null value is not cacheable, which means you'll always trigger a remote load and/or a CacheStore hit to find the missing entry. Avoiding the loading attempt could have some benefits on this - however I'd agree that it should be preferrable to fix this in Infinispan's design.
|
