Monday Mar 12, 2007
Currently TPC-C is not to be replaced by TPC-E, but it should.
TPC-C is really a simplistic database benchmark that is far too old
and simple.
It was reported by Timothy Prickett Morgan last week in
http://www.itjungle.com/breaking/bn030507-story02.html
"While the TPC-C test will soon be replaced by the TPC-E OLTP test, which is designed to address some of the shortcomings of the TPC-C workload and the benchmark methodology"
In my view, TPC-C should be shunned by the industry, joining
Sun's well thought out avoidance of a simplistic benchmark years ago.
We already uncovered IBM's numerous benchmark techniques that took
advantages of the TPC-C benchmarks simplicity.
http://blogs.sun.com/bmseer/entry/ibm_too_tricky_for_good
I'm kinda surprised that people would still cover TPC-C, long ago we gave
up on Dhrystones because of people following the benchmark rules but taking advantages of shortcomings to a high degree...
The article goes on to say:
"nonetheless one of the few independent metrics for assessing the performance of a server"
Actually there are actually a number of
independent workloads to assess server performance by both
TPC and
SPEC committees as well as several other ISV benchmarks such as
SAP.