Slashdot Mirror
Oracle To Halve Core Count In Next Sparc Processor
angry tapir writes "Oracle will halve the number of cores in its next Sparc processor and instead improve its single-thread performance, a weak area for the chip but one that's important for running large databases and back-end applications. The next Sparc chip on Oracle's roadmap, the T4, will have eight cores on each chip, down from 16 in the current Sparc T3."
The reduction in cores from 16 to 8 was part of the Sparc road-map before Sun was acquired by Oracle. Despite a lot of speculation it appears Oracle is following through with the plans they bought from Sun.
Lurking at the bottom of the gravity well, getting old
No. Nobody's moving away from Oracle - that rhetorical question doesn't make you sound like a smartass, but rather its less intelligent opposite.
What matters to Oracle's customers who buy Sun hardware is that their databases run as fast as possible, as that's the limiting factor on those customers' businesses. That's why Oracle bought Sun: to compete with IBM, which runs DB2 on IBM CPUs at the high end, the HW and SW tweaked to work best together for that operation.
Reducing the number of cores isn't designed to help. It's designed to leave that amount of transistors on the CPU available for making Oracle DBs run as fast as possible in the few simultaneous threads that Oracle needs for DB performance.
Oracle is not selling CPUs to the mass market that can't tell the difference among products, mostly because they don't have a benchmark that describes their use profile specifically. Oracle is selling to customers who pitch $:TPM to their bosses. And the $:TPM buzzword is not only not going out of style, it's what continues to drive $ to Oracle.
--
make install -not war
ISTR benchmark after benchmark saying that they performed about as well as a Pentium Pro/II of the same clock speed, when running native code. Except they were doing 533 MHz when Pentium Pros were doing 200. Oh, and the benchmarks I remember showed that the Alpha could emulate x86 code as fast as the Pentium Pro 200 could run it natively, after DEC's emulation software had profiled the code.
The problem is this... they were also, IIRC, more EXPENSIVE than said Pentium Pro machines, and they could (for the Windows market) only run NT, when everyone targeted 95. And the performance advantage was completely wasted if your code wasn't written for Alpha. (So, you could run Office 95 and such on them, but because Microsoft only compiled the OS and maybe some server software, for general desktop AND workstation duty if your business needed Windows, a PPro box was cheaper and may have been able to do the same job.)
(Keep in mind that back then, Microsoft was ambivalent about x86, at least in the workstation and server market. Windows NT was written to run on quite a few popular processor families - MIPS, PPC, and Alpha, in addition to x86. And, Microsoft made what was essentially an AT Architecture MIPS system specification for running NT on MIPS.)
At the very least, Oracle has introduced a great deal of uncertainty into Sun products, so you have to ask "What does Sun hardware offer than other hardware doesn't?". With all the bad press, they have an uphill battle converting people to Sun from other platforms, and for those who have a choice, what *exactly* is the big benefit that can't be purchased from someone else for less?
Do you care about crypto at all? If so, the T-series CPUs have on-die MD5, SHA-1, SHA-2 family, DES, 3DES, AES (multiple modes of operation), RC4, RSA (up to 2Kb), and ECC acceleration, as well as RNG. The T3s can do almost 80 Kop/sec for RSA 1024. All you have to do is link against the Solaris-provided OpenSSL library and call the appropriate "engine" APIs to activate things (this is built-in to a lot of FLOSS software already (e.g., Apache)).
The T5220 (T2 processor, the T3 just came out) has been benchmarked as doing 44 Gb/s AES128: and that's on the crypto co-processors, so the "real" processors are free to do "actual" work--like serving HTTP requests. At the same time as this, the T2 can also do 38 Kop/sec of RSA 1024. At the time this benchmark was published, a quad-core Xeon 3 GHz could do about 8 Gb/s AES1028 and 9 Kop/s of RSA1024 signing--with little to nothing left over to do anything else.
So you ask, "what can these systems do?" Well, how about: instead of paying for a bunch layer of load balancers to do SSL and RSA, and a whole bunch more machines to do actual web requests, why not just buy a lot fewer T2s (now T3s), and save power, cooling, and rack space?
The T-series is not good at everything, but for the mutl-threaded, multi-client workloads it was designed for it works very well.