Scribd
Upload
44 views

TPC C

TPC-C is an on-line transaction processing (OLTP) benchmark approved in 1992 that is more complex than previous benchmarks. It involves a mix of five concurrent transaction types executed against a database of nine table types with varying record counts. TPC-C simulates an order-entry environment with transactions for entering, delivering, and monitoring orders. While based on a wholesale supplier, TPC-C can represent any industry that manages products or services. It was designed to include components of previous benchmarks and scale based on system power. Results must demonstrate the ACID properties and be independently verifiable through a full disclosure report.

Uploaded by

Noor Eldin Shashtari
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
44 views

TPC C

TPC-C is an on-line transaction processing (OLTP) benchmark approved in 1992 that is more complex than previous benchmarks. It involves a mix of five concurrent transaction types executed against a database of nine table types with varying record counts. TPC-C simulates an order-entry environment with transactions for entering, delivering, and monitoring orders. While based on a wholesale supplier, TPC-C can represent any industry that manages products or services. It was designed to include components of previous benchmarks and scale based on system power. Results must demonstrate the ACID properties and be independently verifiable through a full disclosure report.

Uploaded by

Noor Eldin Shashtari
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

TPC-C benchmark:

Approved in July of 1992, TPC Benchmark C is an on-line transaction


processing (OLTP) benchmark. TPC-C is more complex than previous
OLTP benchmarks such as TPC-A because of its multiple transaction types,
more complex database and overall execution structure. TPC-C involves a
mix of five concurrent transactions of different types and complexity either
executed on-line or queued for deferred execution. The database is
comprised of nine types of tables with a wide range of record and population
sizes. TPC-C is measured in transactions per minute (tpmC).

TPC-C simulates a complete computing environment where a population of


users executes transactions against a database. The benchmark is centered
around the principal activities (transactions) of an order-entry environment.
These transactions include entering and delivering orders, recording
payments, checking the status of orders, and monitoring the level of stock at
the warehouses. While the benchmark portrays the activity of a wholesale
supplier, TPC-C is not limited to the activity of any particular business
segment, but, rather represents any industry that must manage, sell, or
distribute a product or service.

TPC-C was designed to carry over many of the characteristics of TPC-A, the
TPC's standard version of DebitCredit. Therefore, TPC-C includes all the
components of a basic OLTP benchmark. To make the benchmark
applicable to systems of varying computing powers, TPC-C
implementations must scale both the number of terminals and the size of the
database proportionally to the computing power of the measured system. To
test whether the measured system is a fully production-ready system with
sufficient recovery capabilities, the database must provide what are defined
as the ACID properties: atomicity, consistency, isolation, and durability. To
facilitate independent verification of the benchmark results, the test sponsor
must release, in a full disclosure report, all information necessary to
reproduce the reported performance. This performance, which measures the
throughput of the system, must be reported along with the total system cost.
The total system cost is a close approximation of the true cost of the vendor-
supplied portion of the system to the end-user. It includes the cost of all
hardware and software components; maintenance costs over 5 years; and
sufficient storage capacity to hold the data generated over a period of 180
eight-hour days of operation at the reported throughput.

You might also like