# 19. TPC C Benchmark Kit

Chapter Contents | Prev | Next
Keyword Search:
www.openlinksw.com
docs.openlinksw.com
Book Home
Contents
Preface
TPC C Benchmark Kit
Building the Test Database
Using the Test Program
Tuning Parameters and Number of Users
Omissions, Exceptions from the Definition
Sample Configuration
Other Factors
TPC C Procedures
DDL Statements
Stored Procedures

## 19.4. Omissions, Exceptions from the Definition

Running the benchmark by the book is a complex and costly process which requires hardware and software that is not commonly available.

To measure tpmC rates that are directly comparable with published figures the benchmark must comply with the scaling rule of a maximum of 12.5 tpmC per warehouse. Therefore to measure 1250 tpmC, one must have a database of 100 warehouses, approximately 10 GB.

Obtaining a good figure will require the maximum RAM configuration of the platform in question.

One will further remember the 180 day rule which states that the disk configuration quoted in the pricing section must be large enough to accommodate 180 8 hour days worth of new orders coming in at the reported rate.

The number of users will also be large, e.g. 1000 users for the 1200 tpmC result, based on 10 terminals per warehouse.

Almost all published results have been obtained with a transaction monitor, typically Tuxedo.

Note that the driver in this kit initiates a new transaction as soon as the previous one is completed. The correct behavior is to generate transactions at a basically constant rate, load being increased by adding clients and a new warehouse every 10 clients.

See Also:

The complete benchmark specification is available at the TPC Web Site.

Previous Tuning Parameters and Number of Users | Chapter Contents | Next Sample Configuration