Tuning parameter hot list
- Install the most current refresh pack, fix pack, and interim fixes from IBM Support
This can provide a dramatic enhancement of performance. I have seen a Portal and Commerce Web service operation improve in speed from 6 minutes to 10 seconds after the application of fix packs and fixes.
- Check hardware configuration and settings
- Review the application design
- Tune the operating systems
- Set the minimum and maximum JVM heap sizes
- In general, the type 2 JDBC driver is recommended. However, the type 4 JDBC drivers perform faster in the area of multi-row fetch.
- Tune JDBC data sources and associated connection pools
The connection pool size and prepared statement cache need to be sized based on the number of concurrent requests being processed and the design of the application.
- Enable servlet caching
I have witnessed dramatic throughput improvements when servlet caching is enabled.
- Enable the pass by reference option
- Ensure that the transaction log is assigned to a fast disk
Some applications generate a high rate of writes to the WAS transaction log. Locating the transaction log on a fast disk or disk array can improve response time.
- Tune related components to achieve higher throughput for the entire configuration.
- Disable functions that are not required
For example, you can disable Web services addressing. Note that disabling WS-Addressing disables WAS support for the following specifications...
- Web Services Atomic Transactions
- Web Services Business Agreement
- Web Services Notification
Related tasks
Tuning the application serving environment
Use the dynamic cache service to improve performance
Use application clients
Related Reference
Tuning TCP/IP buffer sizes
Related information
IBM eServer Workload Estimator