Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS
Tuning the WebSphere Virtual Enterprise cell
Start here for a summary of key performance tuning parameters for your WebSphere® Virtual Enterprise configuration.
About this task
You can complete any of these steps to improve the performance of your WebSphere Virtual Enterprise configuration.
Procedure
- Assign all URL patterns from an application to transaction classes. Any URL that does not map to a transaction class is classified as "best effort", also called discretionary, the default policy. Transaction classes are part of service policies. To change transaction classes from the administrative console, select Operational policies > Service policies > service_policy_name > Transaction classes.
- Check service policy goals against the actual performance of the service class and adjust the goals if necessary. For example, your service policy has an average response goal of 200 milliseconds and the measured average service time is 300 milliseconds. You might consider adjusting your goal to 500 milliseconds.
- To change how quickly the application placement controller reacts to load changes, adjust the following properties:
- Configure the minimum time between placement changes in the administrative console. Select Operational policies > Autonomic controllers > Application placement controller. Set the minimum time between placement changes to a suitable value.
- Configure the application placement controller cycle from the administrative console. Select Operational policies > Autonomic controllers > Application placement controller > Custom properties. Add a custom property with the name minControlCycleLength and a suitable value in minutes.
- Adjust the control cycle length. The control cycle length minimum property determines how quickly the autonomic request flow manager (ARFM) reacts to load changes. You can change the ARFM control cycle length. From the administrative console select Operational policies > Autonomic controllers > Autonomic request flow manager. Set the control cycle length minimum property to a suitable value.
- Adjust ARFM to limit the maximum use of the nodes.
- In the administrative console, select Operational policies > Autonomic controllers > Autonomic request flow manager.
- Set the Maximum CPU Utilization property. Higher values give better resource use, lower values give more robust operation.
Related tasks
Configure the autonomic request flow manager
Configure the health controller
Manage the WebSphere Virtual Enterprise environment