Administration guide >
Tune and performance
You can tune settings in the environment to increase the overall performance of the WebSphere eXtreme Scale installation.
- Operational checklist
Use the operational checklist to prepare the environment for deploying WebSphere eXtreme Scale.
- Operating systems and network tuning
Network tuning can reduce Transmission Control Protocol (TCP) stack delay by changing connection settings and can improve throughput by changing TCP buffers.
- Plan for network ports
WebSphere eXtreme Scale is a distributed cache that requires opening ports to communicate with the Object Request Broker (ORB) and Transmission Control Protocol (TCP) stack among Java™ virtual machines. Plan and control the ports, especially in an environment that has a firewall, and when you are using a catalog service and containers on multiple ports.
- ORB properties and file descriptor settings
Tuning considerations include Object Request Broker (ORB) properties and file descriptor settings.
- JVM tuning for WebSphere eXtreme Scale
JVM (JVM) tuning can yield a significant improvement in the deployment of WebSphere eXtreme Scale.
- Configure failover detection
You can configure the amount of time between system checks for failed servers with the heartbeat interval setting.
- Use 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.
- Tune the dynamic cache provider
The WebSphere eXtreme Scale dynamic cache provider supports the following configuration parameters for performance tuning.
- Tune the cache sizing agent for accurate memory consumption estimates
Beginning with v7.1, WebSphere eXtreme Scale supports sizing the memory consumption of BackingMaps 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 usually 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.
Plan the WebSphere eXtreme Scale environment
Install WebSphere eXtreme Scale
Upgrade and migrating WebSphere eXtreme Scale v7.1
Configure the deployment environment
Operate the deployment environment
Secure the deployment environment
Monitor the deployment environment