WebSphere eXtreme Scale Programming Guide >
Performance considerations
To improve performance for the in-memory data grid or database processing space, you can investigate several considerations such as tuning the Java™ virtual machine settings and using the best practices for product features such as locking, serialization, and query performance.
- JVM tuning
You must take into account several specific aspects of Java virtual machine (JVM) tuning for WebSphere eXtreme Scale best performance.- CopyMode best practices
WebSphere eXtreme Scale makes a copy of the value based on the six available CopyMode settings. Determine which setting works best for the deployment requirements.- Plug-in evictor performance best practices
If you use plug-in evictors, they are not active until you create them and associate them with a backing map. The following best practices will increase performance for least frequently used (LFU) and least recently used (LRU) evictors.- Locking performance best practices
Locking strategies and transaction isolation settings affect the performance of the applications.- ObjectTransformer interface best practices
The ObjectTransformer interface uses callbacks to the application to provide custom implementations of common and expensive operations such as object serialization and deep copies on objects.- Serialization performance
WebSphere eXtreme Scale uses multiple Java processes to hold data. These processes serialize the data: That is, they convert the data (which is in the form of Java object instances) to bytes and back to objects again as needed to move the data between client and server processes. Marshalling the data is the most expensive operation and must be addressed by the application developer when designing the schema, configuring the grid and interacting with the data-access APIs.