Tune >


WebSphere Commerce is a complex interaction between a number of products. Each product has its own performance characteristics and within the interaction of the various components, there are a number of places where performance can be affected by incorrect configuration or insufficient resources.

Performance objectives include handling the following types of requests in a timely manner:

To optimize WebSphere Commerce, consider the following components:


Make sure the system meets the minimum system requirements.

In a production environment with a lot of concurrent users, multiple processors will help increase performance. Using a faster processor will generally speed up most operations.


See the IBM Redbooks - DB2 UDB V8 and WebSphere V5 Performance Tuning and Operations Guide for more information about DB2 Database tuning.

Make sure that the maximum database connection pool size is sufficient to handle all concurrent tasks (for example, HTTP connection, scheduler threads, and so on).

WebSphere Commerce

Make sure the server is I/O bound - the WebSphere Commerce system performance might be impacted if a lot of file access or network access is occurring. For example, if all logging and tracing is turned on, the system could spend most of the time writing data to the disk instead of handling the workload.

Use dynamic caching as documented in Dynamic caching.

If you are using server-based session management, see the following topics in the WebSphere Application Server Information Center:

WebSphere Application Server

See the Tuning performance parameter index topic in the WebSphere Application Server Information Center.

Connection pool size

When considering the size of the connection pool, include the following items in the calculation:

  • Web container threads
  • Active schedule threads
  • WebSphere Commerce key manager
  • WebSphere Commerce audit
  • WebSphere MQ listeners
  • Other multi-connection threads in the custom code

Other considerations

  • WebSphere Datasource (Minimum and Maximum Connection pool size, Statement Cache Size)

  • Web site design

  • Security (configuration, time outs, authentication, and access control)

  • Web server issues (process handling, resource usage, fast response cache accelerator)

  • WebSphere engine issues (Java Virtual Machine or JVM, transport queue, the caching of JSP files, EJB container)

  • WebSphere Commerce session management (caching, storing sessions in memory or storing sessions in the database)

  • WebSphere Application Server session management, (setting for the in-memory session count, allow overflow, timeout interval, and Distributed Environment setting).

  • NFS (Network File System) performance tuning (file server tuning)


Search Tips   |   Advanced Search