Elisabeth Stahl on Benchmarking and IT Optimization

Oracle, The Dates They are A-Changin´

with one comment

One of the great things about using industry standard benchmarks for performance evaluation is that you can trust the data. It is run according to benchmark kits developed by a committee. It is audited. It produces data and the results don’t change.

Except when they do.

One of the very useful pieces of data that is part of a TPC benchmark result, in addition to performance and price performance, is the availability date. This is the date for which all components, hardware and software are available for purchase. There are TPC rules around this: “The Committed delivery date for general availability (availability date) of products used in the price calculations must be reported. The Availability Date must be reported on the first page of the Executive Summary and with a precision of one day. When the priced system includes products with different availability dates, the reported availability date for the priced system must be the date at which all Components are committed to be Generally Available. Each Component used in the Priced Configuration is considered to be Available on the Availability Date unless an earlier date is specified.”

As a consumer of industry standard benchmarks, we trust that the vendor has made extensive and detailed plans to meet this date and that we can use this date in our own systems planning.

It is not very common to change this date after the result is published. It is not very common to change this date on the exact date that the system is supposed to become available. Oracle just did both — yesterday they delayed the system availability date on a TPC-C Sun Fire X4800 result.(1) If you take a look at the Full Disclosure Report you can see that the components that aren’t ready are no small extraneous part of the configuration — they’re huge DIMMs, memory modules.

I’m going to take a wild guess that these components that are not yet available are very much needed to produce this benchmark result.


(1)Oracle Sun Fire X4800 M2 server (8 chips/80 cores/160 threads) – 5,055,888 tpmC, US$.89/tpmC, available 7/10/12.
Source: Result current as of 6/27/12.
TPC-C ,TPC-H, and TPC-E are trademarks of the Transaction Performance Processing Council (TPPC).
The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management.

technorati tags: , , ,,,,,,,,,,,,


Written by benchmarkingblog

June 27, 2012 at 11:34 am

Posted in Oracle, TPC-C

Tagged with , ,

One Response

Subscribe to comments with RSS.

  1. Small main-memory servers force horizontal scaling which forces the purchase of more CPU cores and thus more software licenses. It might not be in Oracle’s best interest to sell servers that obviate software licenses. It’s up to customers to determine whether their best interests align with Oracle’s best interests.


    June 29, 2012 at 11:37 am

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: