Slashdot Mirror
SGI launches R16000
nkrgovic writes " SGI has just launched a new CPU - the long expected R16000. The new CPU works on 700MHz, has 4MB secondary cache and more goodies.
For now the new CPU is only used in SGI's Fuel workstations, but we should expect to see it pretty soon in SGI's Origin servers as well. With new high density compute nodes this should make the Origin's the fastest supercomputing server per square foot."
processor performance has never been SGI's strong point, except for breifly after the R3000 and R10000 were introduced.
SGI's workstation line is largely unimpressive, especially for the 99% case of computer users, hell, even engineers.
The problem is, for a small set of jobs, for a small set of people, nothing else is suficient - at any price. You're either using an SGI, or the work isn't taking place.
That market is continuing to erode, but i dont think it will ever dissolve completely. I think eventually SGi will effectively become a US govt subsidized entity. SGI continues to build the systems that only governments need and only government agencies can afford.
Clustering has nothing to do with the markets SGI sells in. Please don't mention it, it makes me think you don't know what you're talking about.
Do you ?
My opinions are my own, and do not necessarily represent those of my employer.
Nope.
:) So who knows when MIPS IRIX will officially go away.
SGI will continue to make investments in IRIX and MIPS until it makes sense to move all of their products and customers to Linux on IA64, and that may not happen until theres something better than Linux+IA64 out
Linux isn't there yet for the bread and butter SGI customers. Neither is IA64.
My opinions are my own, and do not necessarily represent those of my employer.
You really cannot compare a 700Mhz MIPS chip to a 3000Mhz x86 p4.
You must remember, the R16000 is 64-bit, not 32-bit.
Also, it has 4000k of L2 cache, not 256k or 512k.
Also, out-of-order instruction execution, x86 chips can't do this.
you are trying to compare two things that are completely different.
Alcohol & calculus don't mix. Never drink & derive.
Wha?
You, sir, are almost completely uninformed. The R16000 is an R10000 variant, just like the R12000 and R14000 before it. It is not a vector processor, and has no vector units. The R16000 is, furthermore, a desktop processor in its own right, because it's currently being used in the Fuel workstation.
Incidentally, SGI divested itself of Cray some time ago. Cray was bought by a company called Tera Computing, which then changed its name to Cray. They're building the SV2 vector supercomputer now, using their own processors, and they also have an arrangement with NEC to market the SX-6 in the United States with a Cray logo, but that's strictly a resale agreement.
I write in my journal
You must remember, the R16000 is 64-bit, not 32-bit.
For the record, the R10000 series can run either 32-bit or 64-bit code. All other things being equal, the 32-bit version of a program will run faster than the 64-bit version; you can fit more 32-bit ints into cache at once than 64-bit ints, so the 64-bit version of a program generally suffers more cache misses than its 32-bit counterpart.
On an SGI box, you don't compile for 64-bit unless you absolutely have to address more than 2 GB of virtual memory.
Also, it has 4000k of L2 cache, not 256k or 512k.
That's pretty puny for an SGI. The processors they use in the Origin servers have typically been equipped with 8 MB of secondary cache; the 4 MB version must be just for the workstations, to keep costs manageable.
you are trying to compare two things that are completely different.
On this point, however, you're 100% correct.
I write in my journal
Before evryone assumes that this thing is fast here some numbers to keep in mind:
OK there are no numbers for 16K but here the numbers for 600Mhz 14K
SPECint2000 500
SPECfp2000 529
For comparison
UltraSPARC III Cu 1.015GHz
SPECint2000 576
SPECfp2000 775
AMD XP 2800
SPECint2000 913
SPECfp2000 843
INTEL P4 2.8
SPECint2000 1040
SPECfp2000 1048
i dont need a MIPS history lesson. I didn't "forget" any of those CPUs. The R8000 was almost non-existant across SGI's product line.
While it was the first implementation of MIPS4, and it was an FP monster, and had a huge TLB for the time, it really wasn't so hot as a general purpose CPU.
A far as "true 64 bit" in the R4000, which version of IRIX ran on R4k with 64 bit pointers ? 6.2 and 6.5 certainly don't on my IP22.
When the R3k came out it was the first real example of commercially FAST and successful RISC design. It was used in multiple machines from multiple companies. SGI didn't "really" up the ante again until R10k, which was their first offering that was superpipelined and superscalar.
Finally, regarding SGI and clustering:
SGI is not price-competitive with shared-nothing clusters of PCs or Alphas. Nor is it trying to be. You probably know what the O2k/O3k systems are good at and how they differ from any other system being sold today, othewise you wouldn't have responded to me. I think my statement is valid --- the SGI big iron solves problems that shared nothing clusters CANT. Furthermore, they're so much more expensive than shared nothings that if you need shared nothing and buy origin, you're silly.
My opinions are my own, and do not necessarily represent those of my employer.
Two way systems are not data center solutions that IBM, Sun, and SGI are competing for with this kind of hardware.
Even if they were, you're ignoring the fact that you cannot physically pack as many CPUs with Intel or AMD as with MIPS, Power4, or Sparc into a chassis. Part of the reason they are clocked slower is because you need to balance heat management with performance density when you're dealing with the big servers.
These boxes are about aggregate compute and storage power per dollar, not about whether the individual CPU cores smoke. The only place you see these cores as singletons is workstations (Single-cored "servers" are usually just the same or similar motherboards as a workstation, but in a case that has a beefier power supply and room for a useful number of hot-swap cages.)
You try and pack 32 Intel cores at 3GHz into a chassis that will handle the same number of MIPS cores, and the only thing you're going to get is voltage underflow from an overloaded power supply. Beef up the power supply, and within minutes you're going to be getting that wonderful whiff of frying, overheated electronics.
Raw performance of a core is only one factor in engineering a complete server. Anyone who claims otherwise has clearly not been involved with the hardware end of this industry.
I do not fail; I succeed at finding out what does not work.