Tuning parameter hot list
The following hot list contains recommendations that have improved performance or scalability, or both, for many applications.
- Review the hardware and software requirements
It is critical for proper functionality and performance to satisfy the minimum hardware and software requirements. Refer to IBM® WebSphere Application Server supported hardware, software, and APIs website which details hardware and software requirements.
Install the most current refresh pack, fix pack, and the recommended interim
fixesThe list of recommended updates is maintained on the Support site.
- Check hardware configuration and settings
Check network connections to make sure that they are running at their highest
speed. For more information, see 調整應用程式服務環境.
Verify network interconnections and hardware configuration is setup for peak
performance. ![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
Tune the
operating systemsOperating system configuration plays a key role in performance. For example, adjustments such as TCP/IP parameters might be necessary for your application
![[IBM i]](../images/iseries.gif)
Tuning IBM i systemsOperating system configuration plays a key role in performance. For example, adjustments such as TCP/IP parameters might be necessary for your application.
IBM Power Systems Performance Capabilities Reference IBM i operating system Version 7.2
- Set the minimum and maximum Java™ virtual machine (JVM) heap
sizes
Many applications need a larger heap size then the default for best performance. It is also advised to select an appropriate GC policy based on the application's characteristics.
Use a type
4 (or pure Java) JDBC driverIn 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 your database.
Use a type 2
JDBC driver for local data access and a type 4 (or pure Java) JDBC driver for remote data
accessIn general, the type 2 JDBC driver is recommended. 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 your database.
Tune
WebSphere Application Server JDBC data sources and associated connection
pools
The JDBC data source configuration might have a significant performance impact. For example, 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.
See the Connection pooling topic for more information.
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
Enable the pass by
reference optionUse applications that can take advantage of the pass by reference option to avoid the cost of copying parameters to the stack.
- Ensure that the transaction log is assigned to a fast disk
Some applications generate a high rate of writes to the transaction log. Locating the transaction log on a fast disk or disk array can improve response time.
- Tune related components, for example, database
In many cases, some other component, for example, a database, needs adjustments to achieve higher throughput for your entire configuration.
- Disable functions that are not required
For example, if your application does not use the web services addressing (WS-Addressing) support, disabling this function can improve performance.
Attention: Use this property with care because applications might require WS-Addressing MAPs to function correctly. Setting this property also disables WebSphere Application Server support for the following specifications, which depend on the WS-Addressing support: Web Services Atomic Transactions, Web Services Business Agreement and Web Services Notification.
To disable the support for WS-Addressing, refer to Enabling Web Services Addressing support for JAX-RPC applications
- Review your application design
You can track many performance problems back to the application design. Review the design to determine if it causes performance problems.
- CDI behavior
changes
By default, CDI 1.2 scans all application archives. CDI 1.2 can greatly increase startup time, especially for larger applications. To disable implicit archive scanning for annotations, set the system property, enableImplicitBeanArchives to false. This setting skips the scanning of archives unless they contain a beans.xml file.

參照主題