Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Performance
Methodology
Like site security, a proper approach to site performance requires planning, execution, testing, monitoring, and maintenance. The following collections of topics describe each phase of this process, and contain the recommended considerations, and best practices for getting the most out of your WebSphere Commerce deployment.
Tuning
A WebSphere Commerce deployment is made up of many individual parts that work together to provide the e-commerce experience. By default, each part is configured to provide a base level of performance. However, individual changes can be made to potentially gain extra performance. The following collection of topics provides details on how to make these performance changes to the individual components of your site.
JVM performance tuning
For improved performance, JVM settings require careful tuning. Tune your JVM settings to avoid experiencing memory allocation errors. The symptoms for these errors can vary from intermittent performance problems to the periodic failure and restart of the JVM. Consider the default JVM settings set by WebSphere Commerce as a starting point. The information in the JVM performance tuning topic is specific to the IBM JDK.
Tuning JVM settings on IBM i
To improve WebSphere Commerce performance, the WebSphere Application Server JVM settings require tuning. After you create the WebSphere Commerce instance, the default JVM arguments on IBM i are empty. Change the default behaviors using the steps in this task to improve performance on the WebSphere Commerce server.

For IBM i OS operating system

Tuning JVM settings on IBM i

To improve WebSphere Commerce performance, the WebSphere Application Server JVM settings require tuning. After you create the WebSphere Commerce instance, the default JVM arguments on IBM i are empty. Change the default behaviors using the steps in this task to improve performance on the WebSphere Commerce server.

Procedure

Open the WebSphere Application Server administrative console.
Click Servers > Server Types > WebSphere application servers > server_name where server_name is the name of the WebSphere Commerce server.
In the Server Infrastructure section, click Java and process management > Process definition > Java virtual machine.
Set the Generic JVM arguments: -Xgcpolicy:gencon -Xmns256m -Xmnx512m -Xjit:codetotal=131072

Note: Set Xgcpolicy:gencon when you are using a generational garbage collector. The generational schema attempts to achieve high throughput, along with reduced garbage collection pause times. To accomplish this goal, the heap is split into new and old segments. Long-lived objects are promoted to the old space while short-lived objects are garbage collected quickly in the new space. The gencon policy provides significant benefits for many applications. However, it is not suited for all applications, and is typically more difficult to tune.