WebSphere Commerce works closely with a number of different components and products, each with its own performance characteristics. Provision of sufficient hardware and software resources, and careful consideration to configuration settings, can help achieve performance objectives.

Performance objectives include handling the following types of requests in a timely manner:
  • Handling multiple customer requests
  • Accessing data in the WebSphere Commerce database
  • Formatting data as web pages
  • Returning responses to the customer's browser

Too frequently, the idea of performance testing is equated with adding a test phase, believing that performance risks can be covered by running a performance test right before launch. A test phase might discover bottlenecks in the application, but the fix might require a solution that goes back to the fundamentals of application design and architecture. Considering performance only at the end of development leads to not being able to address issues on time or having to patch and get by. In the long term, the "band-aid" mode leads to an increasingly complex application that becomes more difficult to manage and optimize. The point of the performance lifecycle is about considering performance in all aspects of the project, not just as a one-time event.

The premise of the performance lifecycle is that performance is considered throughout the entire project lifecycle. Adapting the performance lifecycle approach shifts performance from a point in time activity to a parallel and equally important track alongside a project’s development activities. Additionally, achieving pre-defined performance criteria becomes part of the website or application launch approval process. The key performance metrics are continually addressed and tracked against targets.

To optimize WebSphere Commerce performance, review the performance methodology section for the recommended approach.