BM Seer Unofficial thoughts from an anonymous Sun employee

SPECpower_ssj obscuring important factors?

Wednesday Feb 25, 2009

The disclosure reports to SPECpower_ssj need to be redesigned. It seems to violate many of Dr. Edward Tufte (author of "The Visual Display of Quantitative Information"). For review, they are basically:

  • "consists of complex ideas communicated with clarity, precision, and efficiency.
  • is that which gives to the viewer the greatest number of ideas in the shortest time with the least ink in the smallest space.
  • requires telling the truth about the data."

    He continues:

  • induce the viewer to think about the substance rather than about methodology,..., or something else
  • avoid distorting what the data have to say
  • present many numbers in a small space
  • encourage the eye to compare different pieces of data
  • reveal the data at several levels of detail, from a broad overview to the fine structure

In my opinion these are not even close to being followed...

What are some of the key factors in server power? Memory size, Redundant Fans, Redundant Power supplies, Reasonable disk/network configuration, LOW-LEVEL WORKLOAD SPECIFIC TUNINGS.

Memory specification is obscured.

What do I mean by that? Memory size is critical to power consumption and for example is listed as "4" Not even 4GB. Nicely vague. It also is listed in the 3rd section in the 13th row of the table -- VERY IMPORTANT YET SO VERY BURIED. What is listed in the 1st section 2nd row, something of no value to customers. Do you have a guess? ... "Test location". Very silly.

Also, by the by, I see several server submission on SPECpower_ssj with ONLY 4GB of total server memory -- that is 1GB/core. TINY!!! I don't know any real customer that has anywhere near this ratio for most servers in their datacentre.

Non-redundant Power supplies?

ok the form shows this as 1x or 2x, but all of them seem to be 1x, meaning non-redundant.

Non-redundant Fans?

I do not see this specified, does anyone else?

LOW-LEVEL WORKLOAD SPECIFIC TUNINGS

This is specified, for example most results show, "BIOS Settings: Adjacent Sector Prefetch Disabled, and Hardware Prefetch Disabled." This seems very low-level tuning to get around the fact that the benchmark Java workload does lots of pointer chasing and overloads the prefetcher. OK how does a customer know when to do that. SPEC NEEDS TO ONLY ALLOW DEFAULT BIOS!

Disclosure Statement

SPEC and SPECpower benchmark name are registered trademarks of the Standard Performance Evaluation Corporation. www.spec.org for details.

[5] Comments
Like this post? del.icio.us | furl | slashdot | technorati | digg
Comments:

"listed as "4" Not even 4GB" - I wear bifocals and even I can easily see the label just to the left of those "4s" (or other values) and see the field label which says "Memory Amount (GB):" Rather like how it does CPU frequency with "CPU Frequency (MHz):" and a "bare" number. Doesn't seem obscure at all.

"I see several server submission on SPECpower_ssj with ONLY 4GB of total server memory -- that is 0.5GB/core. TINY!!!" You may want to look again, more closely, and check your math. I went to:

http://www.spec.org/cgi-bin/osgresults?conf=power_ssj2008&op=form and asked to have it display core count and memory amount, and looking at the results I did not find a single one at 0.5GB/core. They were all 1.0GB/core or 2.0GB/core. Just going back and double checking, I see that I actually missed one that was 4GB/core.

"ok the form shows this as 1x or 2x, but all of them seem to be 1x, meaning non-redundant." Again using SPEC's supplied search form, it is possible to see that while indeed _almost_ all are single power supply, there are 6 results with 2 power supplies and 2 results with 3 power supplies. Of course two or even three power supplies does not a priori mean they were redundant.

WRT calling-out redundant power supplies or fans, I've tried to go back through your blog posts using the "power" and "watts" links, and thus far haven't found that called-out. Sometimes it seems that details on memory config were sparse as well - sometimes they were there, sometimes they were not. I did find one instance of an ambient temperature being mentioned, (another important item that SPECpower does _not_ seem to leave-out) but that was only where you were chastising (correctly IMPO) some unnamed competitor for quoting numbers from an ambient temp of 61F.

So, while you _may_ have found a couple things that SPECpower_ssj2008 might improve in its disclosure reports in the future - perhaps calling-out if the power supply configuration is redundant, maybe something about fans (although if a system has neither, I'm sure marketing departments will be able to FUD those on their own without having to have a disclosure report telling them), one very significant virtue SPECpower_ssj2008 seems to have is that everything SPECpower_ssj2008 has disclosed is always there in every disclosure. That definitely seems _not_ to be the case with ad-hoc vendor disclosures.

Posted by rick jones on February 25, 2009 at 09:15 PM PST #

Sorry about the 0.5GB/core that has been corrected. most top ones are 1GB/core. The 4GB/core you mention is one of the lowest performers.

But how come other benchmarks are 4GB/core with some more and some less? I'll copy and paste this from 2007. We all know virtualisation is making many customer heuristics even larger.

http://blogs.sun.com/bmseer/entry/big_memory_used_on_benchmarks
SPECweb2005:
64GB: HP DL580 G5 (4 quad-core Xeon 2.933GHz)
64GB: HP DL585 G2 (4 dual-core Opteron 3GHz)
32GB: HP DL380 G5 (2 quad-core Xeon 2.66GHz)

SAP-SD 2-Tier ECC6.0:
48GB: HP rx6600 (4 dual-core Itanium2 1.6GHz)
32GB: HP DL380 (2 quad-core Xeon 3GHz)
32GB: HP BL685c (4 dual-core Opteron 3GHz)
32GB: HP BL460c (2 quad-core Xeon 3GHz)
32GB: IBM p570 (2 dual-core Power6 4.7GHz)

SPECjbb2005:
32GB: Dell PE6950 (4 dual-core Opteron 2.8GHz)

SPECjAppServer2004:
32GB: HP rx6600 (4 dual-core Itanium2 1.6GHz)

Lotus:
32GB: IBM p550Q (2 quad-core Power5+ 1.5GHz)

Disclosure Statement (all data as of Sept 27, 2007)

SPEC, SPECpower, SPECjbb, SPECjAppServer, SPECweb, reg tm of Standard Performance Evaluation Corporation, Info on www.spec.org. NotesBench Domino[R] R6iNotes, more info www.notesbench.org. Two-tier SAP Standard Sales and Distribution (SD) standard SAP ERP 2004/2005 application benchmark: SAP, R/3, mySAP reg TM of SAP AG in Germany and other countries. More info www.sap.com/benchmark.

The watts published by Sun are actually warmer than the limit by SPECpower. I've seen docs where more of that will be made explicit publicly.

Memory SIZE should be in the first line! Rick, please push for that in the next documentation... f you work vendor you have direct impact, if you are a customer you can petition them.

Posted by BM Seer on February 26, 2009 at 09:13 AM PST #

"But how come other benchmarks are 4GB/core with some more and some less?" It seems reasonable to guess that the benchmarks using lots of RAM are doing so either to get the last bits of performance, or because they were leveraging the same hardware across multiple benchmarks and the extra RAM didn't hurt on a given benchmark.

Once more benchmarks include power as part of their metrics, and I'm sure that SPEC and others are working on such things - with defined rather than ad-hoc disclosure requirements - you may see a change in configs. So, you should definitely work with Sun's SPEC and other reps to support that. That will have greater long-term benefits than calling for an expansion of the ad-hoc. After all, it was to bring some sense to the ad-hoc that SPEC et al were created right?

For SPECweb2005 you left-out a 72 GB result from FujitsuSiemens and some 64 GB results from Sun, and even some recent 128 GB results from HP, but folks who would like to see them all and more can use: http://www.spec.org/cgi-bin/osgresults?conf=web2005&op=form to include Memory config in the list and sort - seems it does an "alphabetical" sort on Memory rather than a Numeric one though. The disclosure for SPECweb2005 doesn't seem to give thread counts so while one can concoct a mem/core or mem/chip derivative it will take a bit more work to do so for mem/thread.

There are similar search forms for the rest of the SPEC benchmarks.

As for what should or should not be in the first line, from my perusal, the header of a SPECpower_ssj2008 disclosure doesn't look remarkably different from any other SPEC benchmark's. And, since full details are important, not just sound bites, folks should be reading the full disclosure anyway - it really isn't that long for most SPEC benchmarks.

Posted by rick jones on February 27, 2009 at 07:49 AM PST #

Rick: You seem to portray yourself as well versed in SPECpower and SPEC.
OK let's take a different tack, then I'll come back an answer your questions.

Please list the most important aspects of server configuration as they pertain to wattage draw in priority order. Sure it will vary from system to system, but please take a swag and post the five to say eight most important power draws in a system for the SPECpower benchmark.

Posted by BM Seer on February 27, 2009 at 11:43 AM PST #

The only question I have outstanding to you in this thread was a semi-rhetorical one about the impetus behind the creation of SPEC for which I wasn't necessarily expecting an answer. Still my take on the power draws in a SPECpower_ssj2008 benchmark, at least as they have been published thusfar it would be processors, dimms, what I've seen called alternatively the CEC (Core Electronics Complex) or glue or perhaps "other motherboard components," and either the power supply or the boot disc.

Posted by rick jones on March 03, 2009 at 08:48 AM PST #

Post a Comment:
Comments are closed for this entry.