d8888 888 888      88888888888 888      d8b                                 888       888          888       .d8888b.           888                               
      d88888 888 888          888     888      Y8P                                 888   o   888          888      d88P  Y88b          888                               
     d88P888 888 888          888     888                                          888  d8b  888          888      Y88b.               888                               
    d88P 888 888 888          888     88888b.  888 88888b.   .d88b.  .d8888b       888 d888b 888  .d88b.  88888b.   "Y888b.   88888b.  88888b.   .d88b.  888d888 .d88b.  
   d88P  888 888 888          888     888 "88b 888 888 "88b d88P"88b 88K           888d88888b888 d8P  Y8b 888 "88b     "Y88b. 888 "88b 888 "88b d8P  Y8b 888P"  d8P  Y8b 
  d88P   888 888 888          888     888  888 888 888  888 888  888 "Y8888b.      88888P Y88888 88888888 888  888       "888 888  888 888  888 88888888 888    88888888 
 d8888888888 888 888          888     888  888 888 888  888 Y88b 888      X88      8888P   Y8888 Y8b.     888 d88P Y88b  d88P 888 d88P 888  888 Y8b.     888    Y8b.     
d88P     888 888 888          888     888  888 888 888  888  "Y88888  88888P'      888P     Y888  "Y8888  88888P"   "Y8888P"  88888P"  888  888  "Y8888  888     "Y8888  
                                                                 888                                                          888                                        
                                                            Y8b d88P                                                          888                                        
                                                             "Y88P"                                                           888   

All Things WebSphere

Concerns and issues relating to all versions of WebSphere Application Server

Wednesday, July 6, 2011

 

Tuning WebSphere Application Server Dynamic Cache Service (Dynacache) and Data Replication Service (DRS) for replication

If you want to improve the consistency & performance of your WebSphere Application Server DistributedMap replicated cache please follow these best practices

Dynacache Tuning

1. Change replication type of the replication domain to either NOT_SHARED or PUSH depending on your replication needs. NOT_SHARED scales better than PUSH because it only replicates invalidations not cache data.

2. Ensure that the API calls that are putting objects in the cache are NOT overriding the sharing type of the replication domain

3. Set the following as JVM custom properties or as properties on your servlet/object cache instance to reduce redundant DRS traffic, improve performance & force creation of cache instances

• com.ibm.ws.cache.CacheConfig.filterLRUInvalidation = true
• com.ibm.ws.cache.CacheConfig.filterTimeOutInvalidation = true   
• com.ibm.ws.cache.CacheConfig.filterInactivityInvalidation= true                  * requires a relatively recent APAR. check with support
• com.ibm.ws.cache.CacheConfig.ignoreValueInInvalidationEvent = true
• com.ibm.ws.cache.CacheConfig.useServerClassLoader = true
• com.ibm.ws.cache.CacheConfig.createCacheAtServerStartup = true            * since WAS v7

4. [Optional] In the PUSH replication mode to eliminate the bootstrap of cache data,  the application code that gets an instance of distributedMap should call distributedMap.setDRSBootstrap(false). Please note this will prevent the synchronization of cache instance across JVMs in the replication domain at server startup.

Data Replication Service (DRS) Tuning

Configure DRS to use its own threadpool     *default since 7.0.0.15

http://www-01.ibm.com/support/docview.wss?uid=swg1PM16027

High Availability Manager (HAManager) & Data Consistency Services (DCS) Tuning 

http://www-01.ibm.com/support/docview.wss?uid=swg21251873

HAManager Protocol Versions
Bump up the lower level wire format (IBM_CS_WIRE_FORMAT_VERSION core group custom property) and the high availability manager (IBM_CS_HAM_PROTOCOL_VERSION core group custom property)  coregroup protocol versions to the latest one supported. See the following article in the Infocenter. New protocol versions are added to the product if new messages, or new algorithms are required to support new product features, or to improve core group performance. Please note that because the new messages, or new algorithm might not be compatible with the existing messages or algorithm, a new protocol might not be able to interoperate with the old version of the protocol.

Please also revisit my earlier FAQ  and technote on cache replication 
Please also read this olden goldie on Dynacache and DRS Best Practices.

Labels: dynacache

posted by Rohit Kelapure  # 10:14 AM

Comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Subscribe to Post Comments [Atom]

<< Home

Archives

December 2006   September 2008   January 2009   February 2009   March 2009   September 2009   October 2009   November 2009   December 2009   January 2010   February 2010   March 2010   April 2010   October 2010   January 2011   February 2011   April 2011   May 2011   June 2011   July 2011   August 2011   September 2011   October 2011   November 2011   December 2011   January 2012   February 2012   March 2012   April 2012   May 2012   June 2012   July 2012   August 2012   September 2012   October 2012   November 2012   January 2013   May 2013   June 2013   July 2013   September 2013   October 2013   June 2014   August 2014  

Subscribe to Posts [Atom]