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
March 2001

TPC Benchmark Status is published about every two months. The first and primary purpose of the newsletter is to keep interested parties informed about the content, issues, and schedule of the TPC's benchmark development efforts. The second purpose is to invite new members to join these important development efforts. We've already outlined most of the reasons for joining the TPC in another article, Why Join. To receive the status report by email, please click here.

New Web Site
The TPC web site has a new look! The TPC web site has been redesigned to provide better access to information and results. We want to hear how you like it. Please send your comments and suggestions to

Last Meeting
The TPC held a General Council meeting February 8, 2001 in Houston during which the Committee members and Committee chairs were elected.

The Subcommittee concentrated on defining the characteristics and requirements for a successful replacement benchmark to TPC-C. The subcommittee will consider benchmark proposals during the April 2001 meeting in Denver, CO.

TPC-C Version 5
The TPC-C Version 5 was passed in a mail ballot. Changes to the specification from the Version 3.5 release involve pricing and runtime modifications. It is anticipated that the current body of results can be easily upgraded to V5 by re-pricing and resubmitting existing results.

Pricing changes include reducing maintenance support pricing to 3 year, 24x7, down from 5 years, removing terminal network pricing (hubs, switches), and allowing pricing quotes from web pages and print materials. Runtime changes include reducing the disk space requirements to 60 days from 180 days, increasing the measurement interval to 2 hours up from 20 minutes, reporting checkpoint durations, and logging and reporting the number of lost connections of users during the measurement interval. The full text of the specification is available on the TPC web site.

The first TPC-C V5 results have already been submitted. V3 and V5 results are not comparable. If a V3 result is upgraded, it will still remain on the V3 list. Older V3 results will still be accepted until April 20, 2001, with complete phase-out and withdrawal by October 20, 2001.

To upgrade a result from Version 3 to 5, the following requirements must be met:
 • Must satisfy the requirements for product substitutions defined in Clause 8.3 (2) of the spec
 • Must re-price terminal network
 • Must use V5 Maintenance pricing
 • Report original submission date, upgrade date and signify upgrade

Key milestones:
 • V5 Spec Approval:  2/26/01
 • Last V3 result accepted:  4/20/01
 • V3 results removed from result list:   10/20/01

The Technical Advisory Board (TAB) joined the TPC-H/R subcommittee to review the TAB's proposal to standardize the durability requirements across workloads. The wording that the TAB had drafted for inclusion in the next revisions of the H/R specifications was presented. The subcommittee hasn't decided yet whether to incorporate the proposal into the next spec revision.

TPC-DS working group
The TPC-DS working group continued working on the next generation decision support benchmark TPC-DS. Significant progress was made in the following areas:
 • Execution Rules
 • Query Generation
 • Introduction
 • Business and Benchmark Section
The TPC-DS working group is planning to present the first draft of the specification to the General Council in March 2001.

TPC-W Subcommittee
The TPC-W subcommittee made minor revisions to Version 1 and began work on Version 2. Most of the revisions clarified the required reporting for the Full Disclosure Report. Version 1.3.1 of the TPC-W specification reflects the clarifications, while version 1.4 of the specification reflects the minor reporting and implementation changes.

A few TPC-W version 2 topics were discussed, including network bandwidth issues, and the set of new technologies the member companies will be investigating for inclusion in the new specification. The subcommittee is exploring ways to encourage the use of commercially available e-commerce packages and is working to define a set of common features among popular e-commerce packages to be integrated in version 2.

All Benchmark Status Reports

Valid XHTML 1.0 Transitional Valid CSS!