WAS v8.5 > ReferenceTune parameter hot list
- Review the hardware and software requirements
- Install the most current refresh pack, fix pack, and recommended interim fixes
- Check hardware configuration and settings
- Tune the operating systems
- Set the minimum and maximum JVM heap sizes
- Use a type 4 (or pure Java) JDBC driver
In general, the type 2 JDBC driver is recommended if the database exists on the same physical machine as the WebSphere instance. However, in the case where the database is in a different tier, the type 4 JDBC driver offers the fastest performance since they are pure Java not requiring native implementation. Use the previous link to view a list of database vendor-specific requirements, which can tell you if a type 4 JDBC driver is supported for the database.
- Tune WAS JDBC data sources and associated connection pools
- Enable the pass by reference option
- Ensure the transaction log is assigned to a fast disk
- Tune related components, for example, database
- Disable WS-Addressing if not used by the application
Use this property with care because applications might require WS -Addressing MAPs to function correctly. Setting this property also disables WAS support for the following specifications, which depend on the WS-Addressing support: Web Services Atomic Transactions, Web Services Business Agreement and Web Services Notification.
- Review the application design
Related
Tune the application serving environment
Tasks: Using the dynamic cache service to improve performance
Use application clients
Reference:
Tune TCP/IP buffer sizes
Related information:
IBM eServer Workload Estimator