New SGI Altix 3000
dlloyd writes "SGI has just publicly announced the Altix 3000 series of computers that can scale from 4 to hundreds of processors, with up to 64 processors per single system image. Processors each come in a C brick that has 4 CPUs. I/O is done though IX and PX bricks (12 PCI slots per brick, IX bricks have a base I/O controler and two ultra 160 disks inside), just like on the Origin 3900 series. Anything more than 8 CPUs (2 C bricks) is connected by R bricks, which route the NumaLink packets between nodes. The NumaLink network is good for an aggregate 6.4 gigabytes/sec to *each* node. That scales as you add more C and R bricks. Basically, you can think of this as SGI's origin 3000 series, except that it runs Linux and has Itanium2 processors. The performance and scalability is like nothing that has ever run Linux and is *far* ahead of the competition. For those of you who wonder why anyone would need a 64 processor Linux machine, many scientific and technical customers prefer running their code on large, single system image machines. Large single system image machines are also less labor intensive to maintain and admin, plus they work much better on code that needs to share memory and pass messages between threads (even myrinet and mpi is glacial compared to the SGI numalink network and running code multithreaded)."
What is keeping SGI afloat? Service contracts on existing machines?
--Pat / zippy@cs.brandeis.edu
I still don't understand why SGI has foregone such a great OS as IRIX. Why go with Linux? Just trendy, or does it really offer advantages for scientific computing?
How many keys/sec?
That's a lie. SGI has not dropped it's MIPS machines or it's IRIX operating system.
Last quarter IRIX 6.5.18 was released. MIPSpro compilers version 7.4 were released introducing C99 compliance and much better compliance with C++ standards. This hardly sounds like SGI is dropping MIPS/IRIX.
I rather like the concept of this...no more trying to pair up older processors when you run across a board someone is getting rid of a few years down the road. I recall getting a couple dual-PII workstations a year or so ago, and finding a pair of matching (and working) processors to put in them was hell...this way I could have just searched Ebay or my parts stash for a single old part.
In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
I don't do this for a living, but it seems that $/MIPS is the only benchmark even worth discussing, so shouldn't one be able to put together massive clusters of boxen to do the same thing, only without the SGI price tag?
Correct me, because I'm almost certian I'm wrong.
ceci n'est pas un sig.
SGI did make Intel-based workstations that ran Windows NT/2000 that used all standard ports (ATX motherboard layout, Rambus memory, AGP video, et al)... particularly the 550 workstation. They also made several workstation lines that used proprietary memory and graphics subsystem that also ran Windows NT.
For a time... didn't SGI repackage Intergraph workstations as their own? They also had an Itanium 1 workstation that was nearly identical to HP's and Dell's Itanium 1 workstation... but I don't think many of those were ever made.
Just curious, but did anybody notice an estimated price for various configurations either the 3300 or 3700? I couldn't find any price info on their site.
The futexes are also cursed!
It is new. Find me another 64-node shared memory I64 Linux system. I'd much rather develop for a shared memory system than a message passing system. And for a lot of supercomputing apps, a Beowulf cluster just won't cut it.
One of the reasons we continue to choose high-end SGI systems like the O3k series is because of the way IRIX can do engineering/scientifical computational graphics. No one can compete with IRIX when it comes to things like fluid dynamics calculations. Many other vendors have tried, but none come close to SGI's capabilities. I sincerely hope they have continued their unique software in their Linux distribution.
As Linux gets into high-end systems, it will drive the industry to compete. Allmost certainly, Sun and HP will have to release high-end systems with Linux rather than trying to keep it on low-end only. Otherwise, it will be SGI and IBM only
Now, If a major would start using Linux in an innovative way rather than simply trying to lower their costs. That would help drive real sales.
I prefer the "u" in honour as it seems to be missing these days.
even myrinet and mpi is glacial compared to the SGI numalink network and running code multithreaded
Don't mix shitty parallel computation libraries and actual performance. Multithreaded applications without MPI are, of course, faster than anything with MPI, however it says absolutely nothing about:
Contrary to the popular belief, there indeed is no God.
You can use the 64-processor version for not only the simulation of, but also for the real-life purpose of melting iron. A double Itanium2 HP ZX6000 is heating up my office like no computer before. When I turned the ZX6000 on, my daughters' self-made art (taped on the wall) started flapping in the warm air. To me it looks like Itanium2 is server room hardware, at least until we get the 130 nm version.
-- Imperial units must die --
Well... our experience with the O2K was a bit different (haven't touched an O3K though so I dunno much about it). With the Origins 2K and NUMA, if you ran large simulations, the distant memory would flat kill your performance so you had to make sure your working sets fit on a single node. Also, even though each processor board in the O2K had 2 CPUs, if you actually ran an even somewhat memory intensive process on each CPU, your app slogged because the memory bandwidth only supported about 1.4X the bandwidth of a single CPU. Another bad habit was that if someone snuck onto the machine when you were running your 64 process job and they fired up something like emacs, it would cause this nasty shifting around of memory that got you into the NUMA state mentioned above. Later, SGI came out with some tools that would minimize this effect though, which helped a lot.
So... in order to support the kind of stuff we did and run it on 64 nodes, we would have had to buy a 128 processor system because we would only run one process per node and all the nodes were two processors.
So, we also looked at the Sun10K. While the cpu to cpu comparison of raw crunch was lower, the memory bandwidth was uniform so the programs behaved predictably and were almost as fast in any case. It also had the benefit of running 1 process (as far as performance per process) wasn't noticably different from running 64 processes (on a 64 processor machine). At the time, the Sun10K met our needs much better.
Now, of course, all those have been shoved out the door and replaced by something even faster.