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."

2 of 317 comments (clear)

  1. Re:Behind the times. by Twirlip+of+the+Mists · · Score: 5, Informative

    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
  2. Re:Behind the times. by bmajik · · Score: 5, Informative

    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.