A 20nm 32-Core 64MB L3 Cache SPARC M7 Processor
ieeexplore.ieee.org
ieeexplore.ieee.org
The "old" Sun gave me a loaded T1000, gratis, to run the site on (I'd actually asked for one for a review, and they said "Keep it for the site."). The "new" Sun/Oracle gave me the finger.
I had to move everything off the T1K and onto a Debian box hosted at home because I couldn't afford a support contract for it (required to get any patches/updates, even for the OS install that came on it).
I've often likened Oracle's treatment of the hobbyist/enthusiast community as "they shot it in the face and said unless you're going to spend $XXXX with us, we don't care about you. Period."
The "old" Sun recognized that if sysadmin types played with older gear at home and enjoyed it, they were more likely to recommend it for purchases at work, and they encouraged it.
I can't imagine being able to have a 2-3 message conversation with Ellison at all, as I don't spend enough with Oracle to be worth a microsecond of his attention.
https://www.youtube.com/watch?v=G4f62FJGVcE
If you're interested in CPU architecture the Hot Chips talks are generally worthwhile. They're available for free a few months after the conference.
SPARC has been pretty long track history and I admit I really used to love Sun Sparc Servers; now I just look at them and think of the cost and cry.
EDIT: The CPU is 'scheduled to be available sometime in calendar year 2015' according to http://www.oracle.com/us/corporate/features/sparc-m7/index.h... So, barring rumors and insider information, I gest this is it.
My closest option? E5v3-1620 or 1630. It'd be nice if someone started producing non-x86 options for that.
Discussions about ARM vs x86 tend to miss this point. They tend to get stuck on performance or software or process size, missing that the revolutionary thing is the licensing.
[To head off some replies: 64 bit ARMv8 has fast single-thread performance, unlike 32 bit ARMv7]
Intel has made several x86 SoCs, and there's also a few others:
http://en.wikipedia.org/wiki/List_of_x86_manufacturers
This one in particular is interesting since it contains most of a standard PC:
http://en.wikipedia.org/wiki/Vortex86
However the current market for x86 SoCs is in industrial/embedded where performance is not a main concern, so these are not particularly fast.
It's not remotely the same as AMDs eco system of course, as they are competing in someone else's market. But perhaps it's comparable to making software for Apple or Microsoft's platforms.
(There is an incomplete list here: https://en.wikipedia.org/wiki/List_of_x86_manufacturers )
Of course, open instruction sets like RISC-V http://riscv.org/ require no license fee. At lowRISC we're aiming to build a complete open source SoC using RISC-V http://www.lowrisc.org/. I'll note that getting a license for an existing architecture and core implementation isn't as straight-forward as you say. You do need to negotiate and enter an agreement with ARM/MIPS/... (and ARM/Imagination/... need to decide it's worth their while going through that process).
Is that the overclocked speed? I could only find a maximum of 3.5 GHz in the specs...
I would like to see a test between the Haswell E5v3s that support both DDR3 and DDR4 and see what the real world difference is on that specific implementation (which could not be generalized to other implementations of memory controllers by other vendors).
If only we'd make a Power 7 or 8 workstation...
There's still some bizarre stuff though. You can set separate text/data page sizes via env variables that differ from the system wide settings. Take a guess which override, if either, will be reported through POSIX calls? Neither! Fun when someone changes how they invoke your app. Just an example...
AIX is not Linux, so you don't like it. Exactly my point. If these are your use cases, use Linux; don't bitch about AIX because it isn't. You can even use Power blissfully without ever having to use AIX. But then we'd have to hear about Power sucking when a linux developer baked the assumption that Linux == Intel ISA into some "standard" open source packages.
And, BTW...last time I checked, the people doing the Linux kernel were different than the people doing GCC who are different than the people doing GDB. I don't disagree that the AIX ecosystem is generally more dysfunctional, but the mere presence of separation is yet another straw man. Linus has had some less than flattering things to say about what GCC has been up to in the last year or so.