See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
Larger transactions are more efficient, especially for replication. However, larger transactions can adversely impact concurrency because the locks on entries are held for a longer period of time. If you use larger transactions, you can experience a significant increase in replication performance. This performance increase is important when you are preloading a Map. Experiment with different batch sizes to determine what works best for the scenario.
Larger transactions also help with Loaders. If a Loader is being used that can perform SQL batching, then significant performance gains are possible depending on the transaction and significant load reductions on the database side. This performance gain depends on the Loader implementation.
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
