Optimize activations -------------------- Key: JBCACHE-486 URL: http://jira.jboss.com/jira/browse/JBCACHE-486 Project: JBoss Cache Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 1.3.0.GA Reporter: Jerry Gauthier Assigned To: Manik Surtani Priority: Minor Fix For: 2.1.0.GA, 2.1.0.CR1 JBCACHE-420 notes that activation processing is performed excessively. The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue. The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor. Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated. This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination. This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader). It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance. One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__ to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when activated.