TPC photo
The TPC defines transaction processing and database benchmarks and delivers trusted results to the industry
    Document Search         Member Login    
About the TPC
      Join the TPC
      Technical Articles

TPC Benchmark Status
November 2002


The TPC held a General Council meeting October 9 in Austin, Texas. The main focus of the work was on refining existing benchmarks and laying the foundation for new benchmarks. On the OLTP front, clarifications and enhanced wording were recommended for TPC-C. With respect to decision support, version 2.0 of the TPC-H and TPC-R benchmarks were approved by mail ballot prior to the meeting. At the meeting, the upgrade procedure from the older versions to version 2.0 was defined. Work also continues on the new DS benchmark. As for the transactional web e-Commerce benchmark, the main activity centered on re-defining the focus of the TPC-W benchmark. Some of the goals have been revised, and the business to business operations as well as the processing functionalities of these operations have been defined.



The TPC-C maintenance subcommittee continued work on refining the current benchmark. The subcommittee discussed and developed prototypes for a revised Executive Summary. In addition, the subcommittee produced specification wording to address measurement interval vs. checkpoint interval concerns. All changes agreed to are expected to be incorporated into an upcoming minor revision of the TPC-C specification.

The subcommittee also met with the members of the Technical Advisory Board discussing several of the TAB’s wording interpretations and their possible inclusion in a future revision of the TPC-C specification.


TPC-H, R and DS

The TPC-H and TPC-R maintenance subcommittees discussed specification changes to provide for two larger scale factors, 30TB and 100TB. Specification wording changes for TPC-H and TPC-R will be presented at the next meeting.

The procedures for upgrading TPC-H 1.5.0 and TPC-R 1.4.0 results to TPC-H 2.0.0 and TPC-R 2.0.0 were defined:

  • Results that are published as TPC-H/R 2.0.0 won't be visible until October 29, 2002
  • Results published after October 29, 2002 must be published as TPC-H/R 2.0.0
  • For existing results benchmark sponsors have the option to :
    1. Submit a new result: The result will be treated as a new result:
      • new Executive Summary and Full Disclosure Report are submitted
      • require review by an auditor
      • require new filing fee
    2. Upgrade old results
      • report original submission date, upgrade date and signify that it is an upgrade
      • no filing fee will be charged
      • upgrades must occur by April 30, 2003
      • cannot upgrade withdrawn results
      • upgraded results will not be visible until October 29, 2002
      • original TPC-H/R 1.5.0 results remain on the web site until April 30, 2003
      • review period is based on original submission date
    3. Do nothing
      • results will be administratively withdrawn on April 30, 2003.

The TPC-DS development subcommittee continued its work on the new decision support benchmark, TPC-DS. By the end of October the subcommittee will release a new wording of its data generator (dbgen) including schema and first draft of the SQL queries. All members of the TPC were encouraged to prototype TPC-DS.



The TPC-W subcommittee is currently focused on defining the next version of TPC-W. The benchmark is a transactional web service benchmark consisting of commercial application server and database interactions displaying ACID properties.

The TPC-W subcommittee has defined several goals for the next major version of TPC-W. The benchmark will provide for the measurement of the performance and throughput of two web/application servers that provide web services to clients. Two web/application servers are required to demonstrate application durability and fail over capabilities. An industry standard database product running on a third server will be used to provide data storage and integrity of business information. The business model addressed by this benchmark is primarily focused on the business to business scenario. The SUT will be driven by web service requests made through the industry standard and vendor neutral protocols of SOAP and XML. The business logic of the web service(s) must be implemented so that it runs in the context of a managed environment.

The Version 2 business model is fashioned after the “business operations” of a book seller and distributor. The web services exposed present business functions to a number of types of client. These include ordering operations, stock management functions, new product lists, product information, customer service functions, and administrative functions. Commercial messaging and queuing functions are also integrated into the benchmark and present in the stock management operations.

Currently the benchmark defines the following business to business (B2B) operations:

  • Create Order / Order Fulfillment
  • Order Status
  • Stock Management
  • Add New Customer
  • Customer Payment Information Change
  • Product Detail
  • New Products List
  • Modify Product Detail

The processing functionality of these operations have been specified. The subcommittee is currently defining the implementation details and rules for these functions. The subcommittee will be reviewing the functional details of the service operations and adding or modifying the functions in future meetings. The goal is to reach a prototype phase of development by February 2003.

The TPC-W Subcommittee is continuing to gather feedback from the industry regarding current and emerging eBusiness technologies, features, and components. Please take the opportunity to give us your feedback by filling out the TPC-W questionnaire.


Public Relations Committee

The TPC web site will be updated to show both TPC-H/R version 1 and version 2 results. Version 2 results will begin to appear on October 29, 2002. Version 1 results will appear on a separate page until April 30, 2002, after which they will be available only as historical results.


All Benchmark Status Reports

Valid XHTML 1.0 Transitional Valid CSS!