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
August 2005


The TPC held a General Council meeting on June 30 in Toronto, Ontario.  The main focus of the work was on refining existing benchmarks and laying the foundation for new benchmarks.  On the OLTP front, a new draft of the TPC-E specification was completed and prototyping the newly implemented runtime techniques has begun.  With respect to decision support, development of the DS benchmark continues in the areas of queries, specification, data maintenance and prototyping.  Version 1.0. of the Pricing Specification was approved.  The CPU Working Group completed its task of defining how CPUs are counted and reported in light of multi-core, multi-threaded processors.

Current Benchmarks


The TPC-C Maintenance Subcommittee did not convene at this meeting.


The subcommittee incorporated pricing specification version 1 into the TPC-H specification version 2.1.0.  Changes were applied to the following clauses:

  • 0 (Introduction)
  • 7 (Pricing)
  • 8 (Full Disclosure)
  • 9 (Audit)

Each of the above clauses was amended with an initial reference to the pricing specification.  Additionally,

  • Item (g) was deleted from Clause 0.2
  • Clause 7.2 was changed
  • Clause 7.3 deleted
  • Clauses 8.6 and 9.2.7 were deleted to avoid overlap with the pricing specification

The new version for TPC-H is 2.2.0.  It will take effect on August 29th, 2005.


The TPC-W / TPC-App subcommittee did not convene at this meeting.

New Benchmarks


Over the past month, the TPC-E subcommittee has continued its efforts in the development of a new OLTP benchmark.  During this time a new draft of the specification has been approved.  In addition, a new version of the TPC provided code has been released to subcommittee members.

Techniques designed for use in setting runtime I/O characteristics have been implemented.  Prototyping of these techniques has begun.  An additional test has been developed to verify compliance with established isolation level requirements.

Moving forward, prototyping will continue and various changes to the runtime workload characteristics will be evaluated.


The subcommittee is finishing its work on developing TPC-DS in the areas of queries, specification, data maintenance and prototyping.  During conference calls the subcommittee reviewed editorial specification changes made by the group’s consultant.  During these sessions open issues were raised.  The focus of this meeting was an in depth review of these open issues.  Until the next meeting the queries will be finalized and the prototype data will be presented for the data maintenance process.  Final decision of the content of the executive summary will be made.

Other TPC Activities

Public Relations Committee

The PR Committee continues its work on the campaign to promote the TPC and the TPC benchmarks to the industry.  A media and analyst tour to announce the newly released benchmarks was completed on May 13.  The TPC held 13 briefings with press and analysts from CNET, Jupiter Research, Dr. Dobb’s Journal,, eWeek, InformationWeek, The Microprocessor Report, In-stat/MDR, Aberdeen, Vericours, Winter Corp, Ideas International, CRN, ClienT Server News, and Summit Strategies.

Presentations for TPC speakers have been prepared, reviewed, and are in final draft. The prototype of a new customized information system for subscribers of TPC lists and reports continues its tests.


The TPC approved the TPC Pricing Specification Version 1.0.1 in June 2005. This editorial version of the specification provides additional clarity for some clauses and definitions, and includes other minor editorial updates.

The use of the Pricing Specification is currently required for TPC-C and TPC-App benchmarks and a Version 2.2.0 of TPC-H was passed in the June 2005 meeting that will require the use of the Pricing Specification.

The Pricing Maintenance Subcommittee is not currently examining any substantive new change proposals for the specification.

CPU Working Group

The CPU working group completed its assigned task of defining how CPUs are counted and reported in light of multi-core, multi-threaded processors.  Definitions of several key terms were adopted.  These are shown below.  In addition, the impact on the TPC benchmarks and policies was evaluated, and recommended changes were advanced. 

Processor.  A component that contains one or more cores.  The number of processors claimed by the test sponsor must be consistent with the way the product is represented in the test sponsorís marketing collateral, including that which is not related to TPC benchmark results.  The reported number of processors must be the number of processors that are enabled for the benchmark.

Core.  Execution unit that is capable of running one or more processor threads. If a hardware unit can run more than one concurrent processor thread without requiring the processor threads to share execution resources, it is more than one core. It may rely on other "assist" units, such as cache, hardware accelerators, and the like - some or all of which may be shared by multiple cores. The reported number of cores must be the number of cores that are enabled for the benchmark.

Execution Unit. The electronic circuits necessary to implement the semantics of all possible instructions in a computer architecture.

Processor Thread.  The hardware necessary to maintain the state of a Software Thread. The reported number of processor threads must be the number of concurrent processor threads that are enabled for the benchmark.

Software Thread.  An instruction sequence that performs operations within an address space and is scheduled by software.

All Benchmark Status Reports

Valid XHTML 1.0 Transitional Valid CSS!