Even the rate benchmarks are not very impressive. Oracle rigged the comparison in their press release. They compare a 16-core SPARC to an 8-core Intel. If we do apples-to-apples, the Oracle result is pretty humdrum:
- Oracle T5-1B, 16-core SPARC, 436 / 467
- Dell M520, 16-core Intel, 533 / 553
The M520 contains 2x [email protected] GHz. This is far from the fastest Intel chip. You can get them up to 3.6 GHz. It's just a common and inexpensive configuration. Let's not even talk about the respective pricing.
Personally, I haven't used anything newer than a T1. Because I haven't seen anyone buy a new Sun box in that long!
- SPARC T5, 128 threads @ 3.6GHz, 463 / 467 -> 1.01 / 0.946 result/thread/GHz
- Intel Xeon E5-2690, 16 threads @ 2.9GHz, 357 / 343 -> 7.69 / 7.39 result/thread/GHz
Or to put it another way, the SPARC needs 800% more threads and a 24% higher clock to achieve only ~30% faster than the Intel. The POWER is somewhat, but not that much better, at 2.54 / 2.24.
I used this poor comparison because that was what was readily available in SPEC's published results for single-processor (SPECcpu) and parallel (SPECcpu_rate) benchmarks.
When I pointed out that results were provided for that benchmark, you then complained that it wasn't for the general benchmark but a portion of it.
You then proceeded to claim it wasn't an Apples-to-Apples comparison, but Oracle doesn't offer anything less than 16 cores for a T5. I don't think comparing products that don't exist is very useful so attempting to extrapolate what an 8-core version might be seems silly, especially since there's not a one-to-one correlation between cores and performance.
In addition to that, at last check, you can't pick the number of cores (precisely) that you want a processor to have when purchasing so it doesn't make any sense (in my personal opinion) to strictly compare core-to-core performance, since, as the other poster pointed out, core is essentially a definition at the whim of a vendor.
So, I'll just stick to refuting your original implication -- that SPARC isn't setting world-records anymore; it is in fact doing so. And in fact, SPARC continues to have far greater memory bandwidth, I/O bandwidth, and memory capacity compared to general Intel offerings.
So if you want to find out how fast a T5 will actually run your application, try one out and get real data instead of relying on benchmarks to make your decision. Personally, I think you'd be shocked at just how well most workloads perform if you actually tried a T5.
As to the price argument, the companies I've worked for or with in the past generally didn't care about that so much as the reliability of the system and it's capability. They have workloads that consume multiple terabytes of memory. They're using the servers to process transactions that are netting them millions of dollars with the servers they use, so saving a few thousand bucks doesn't matter to them.
In the end, you have to use the right tools for the right job. There's a reason that Oracle sells x86 servers too.
Personally, I don't care which architecture is being used as long as I get to use Solaris/ZFS.
You pasted an Oracle press release that focused on parallel performance.
I complained, and pointed out SPECcpu as a common measurement.
You responded with SPECcpu_rate, a different benchmark focused on parallel performance measurement. It is not surprising that Niagara-derivative chips do well. It is also not surprising that, core for core, they can't match modern commodity systems for density, performance, or cost.
p.s. The "reliability" argument went out the window with VMware. Every fortune 500 is using x86 with VMware HA to provide the redundancy that would have once come from enterprise RISC. (Given how few RISC systems were ever configured with redundant memory or CPUs, VMware-on-commodity is probably offering a substantially better service level.)
p.p.s. a basic 1U x86 server will typically have between 0.75 and 1.5 TB of RAM in it. Yes, TB, as in terabytes. Virtualization provides a market for compact, low-wattage systems with significant memory. That's just the 1Us. In 2014, "Large" x86 boxes are very large indeed.
Lastly, I, too, miss Solaris/SPARC. It was a great platform that I enjoyed working with. I don't miss the associated hardware support contracts that came floating by after the Oracle buyout. It has been several years since I found a contract where SPARC or Solaris were anything but legacy platforms. It's sad, but it's not a mystery.
The reliability argument doesn't "go out the window"; what do you think that software is virtualised on? And to top it off, you're losing a significant amount of performance by using a virtualisation solution like vmware.
In fact, there's entire segments of industry that won't accept the latency typical virtualisation technologies bring.
As for the 0.75 and 1.5 TB of ram argument, perhaps you missed what I said about terabytes. You have any Intel boxes with 32 terabytes lying around?
While you may have not seen any contracts floating around for SPARC hardware, I have quite recently..
Finally, as for "legacy" status, SPARC and Solaris have features not found anywhere else that are continuing to be developed and added even today. It's only a "legacy" platform if you completely ignore the technology there. And Solaris runs just fine on x86 thank you very much.
https://blogs.oracle.com/BestPerf/entry/20130326_sparc_t5_sp...
http://www.spec.org/cpu2006/results/cpu2006.html
While I can't provide you my own detailed benchmarks, I can tell you anecdotally that the most recent SPARC hardware has significantly better single-threaded performance than the early T1, T2 series.
As an example, one of the projects I work on is written almost entirely in Python, and so is almost completely single-threaded (only the transport is multi-threaded using libcurl).
I had an opportunity to compare the performance on the T5 to the T1 and found it was practically night and day, and the performance of the program seems just as snappy as it does on any Xeon system I've used.
Anecdotally, I can tell you that given a choice between a fully-loaded Xeon box or one of the newest SPARC servers, most of the developers I work with will choose the SPARC server simply because builds take significantly less time.