Tuning performance

Tuning

You can tune settings in your environment to increase the overall performance of your WebSphere® eXtreme Scale environment.

Tuning operating systems and network settings
Network tuning can reduce Transmission Control Protocol (TCP) stack delay by changing connection settings and can improve throughput by changing TCP buffers.
ORB properties
(Deprecated)Object Request Broker (ORB) properties modify the transport behavior of the data grid. These properties can be set with an orb.properties file, as settings in the WebSphere Application Server administrative console, or as custom properties on the ORB in the WebSphere Application Server administrative console.
Tuning IBM eXtremeIO (XIO)
You can use XIO server properties to tune the behavior of the XIO transport in the data grid.
Tuning Java virtual machines
You must take into account several specific aspects of Java™ virtual machine (JVM) tuning for WebSphere eXtreme Scale best performance. In most cases, few or no special JVM settings are required. If many objects are being stored in the data grid, adjust the heap size to an appropriate level to avoid running out of memory.
Tuning the heartbeat interval setting for failover detection
You can configure the amount of time between system checks for failed servers with the heartbeat interval setting. This setting applies to catalog servers only.
Tuning garbage collection with WebSphere Real Time
Using WebSphere eXtreme Scale with WebSphere Real Time increases consistency and predictability at a cost of performance throughput in comparison to the default garbage collection policy employed in the standard IBM® Java™ SE Runtime Environment (JRE). The cost versus benefit proposition can vary. WebSphere eXtreme Scale creates many temporary objects that are associated with each transaction. These temporary objects deal with requests, responses, log sequences, and sessions. Without WebSphere Real Time, transaction response time can go up to hundreds of milliseconds. However, using WebSphere Real Time with WebSphere eXtreme Scale can increase the efficiency of garbage collection and reduce response time to 10% of the stand-alone configuration response time.
Tuning the cache sizing agent for accurate memory consumption estimates
WebSphere eXtreme Scale supports sizing the memory consumption of BackingMap instances in distributed data grids. Memory consumption sizing is not supported for local data grid instances. The value that is reported by WebSphere eXtreme Scale for a given map is very close to the value that is reported by heap dump analysis. If map object is complex, the sizings might be less accurate. The CWOBJ4543 message is displayed in the log for any cache entry object that cannot be accurately sized because it is overly complex. You can get a more accurate measurement by avoiding unnecessary map complexity.
Tuning and performance for application development
To improve performance for your in-memory data grid or database processing space, you can investigate several considerations such using the best practices for product features such as locking, serialization, and query performance.

Parent topic: WebSphere eXtreme Scale 8.6 documentation

Last updated: 2021-03-29