@AC 11:41 - I'm not here to defend Sun but...
"While the p595 in the TPC-C benchmark is an off-the-shelf highly flexible system that will perform excellently under a variety of real workloads,"
That's a completely outrageous statement! If you don't think IBM "game" the TPC-C benchmark themselves your living in dream-land, just take a look at the full disclosure report...
Look at the section that covers how the DB2 database was set up - there's 628 pages of DDL/SQL stuff on how they partitioned the hell out of their data so transactions fit neatly into the cache lines on a P6 processor!
Compare that to the HP submission for 4M TPM:
That runs to about 27 pages of DDL/SQL.... (and thats still too much!)
Now the last time you setup a database, how much DDL/SQL did you need to crunch to do it? My guess is that for something as straightforward as the schema that makes up the TPC-C benchmark, you might have a couple of pages worth... now you start to realise just how much IBM "fix" this benchmark. Don't believe me? Well why not go to the horses mouth and see what IBM's own techies say about the benchmark:
The IBM 6M TPC-C system is as much a frankenstein creation as Sun/Oracle's new one will be - it all just goes to show that _all_ these benchmarks are vendor games (and I'd extend that to the SAP and SPEC benchmarks as well).
Folks need to wise up on this stuf and realise that:
- All (IBM Power, Sun SPARC, Intel Itanium, Intel x64) current CPUs provide "good enough" performance for 99.99% of all workloads - system performance isn't the issue it used to be - system *utilisation* (and TCO) is what folks should be focussed on - In case you hadn't notice we don't all drive dragsters!
- If you need some performance metrics, benchmark your own app - don't trust anyone elses numbers