Data set
The size of the data set is an important consideration in WebSphere Commerce benchmarking. How big should the catalog be? How many registered users should there be in the system? Sometimes, we also need to consider other elements, such as the number of orders, campaigns, discounts, and so on. For our tests, the WebSphere Commerce database initially contained the following data1:
| 
|
| Users |
50,000 registered users
|
|
150,000 guest users
|
|
|
|
| Catalog: 500,000 entries |
|
10 top-level categories
|
|
20 second-level categories per top-level category
|
|
25 third-level categories per second-level category
|
|
10 products per third-level category
|
8 available (in-stock) items
|
|
1 backorder (out-of-stock) item
|
|
3 attributes (1 integer and 2 string attributes) per product
|
|
1 top-level dynamic kit category
|
|
10 second-level dynamic kit categories
|
|
10 third-level dynamic kit categories per second-level dynamic kit category
|
|
20 dynamic kits per third-level dynamic kit category
|
|
20 available (in-stock) items per dynamic kit
|
|
|
|
| Orders |
|
170,000 completed orders
|
|
20,000 pending orders
|
|
10,000 canceled orders
|
1For detailed explanations of WebSphere Commerce terminology, please refer to the WebSphere Commerce v6.0 Information Center at http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp