Sun Releases Starcat
SilentChris writes: "Sun has released the Starcat server, a beast with up to 106 processors running Unix. Anyone have an extra couple [million] bucks lying around?" They're not cheap.
← Back to Stories (view on slashdot.org)
until it shows up on e-bay from a disgruntled former dot bomb employee who five-fingered it from a linux shop which stole BSD code.
Lets remember, that this system is not intended to replace a beowolf cluster of cheap pc's. It is intended to do something that most beowolf clusters can never do: present a single OS image with half a terabyte of memory that any cpu can access at very high speed.
This is a system that is very good at things like fluid dynamics and massive database operations. It is not a good idea if all you want to do is get to the top of the list for the SETI@Home project
The system grows to 106 in the following way:
There are 18 "cpu/memory" boards that hold 4 cpu's each. This brings the system up to a total of 72 cpu's and 576GB of ram.
Now, if you want an server that just does number crunching and dont care about I/O, you can then add 'MaxCPU" modules. Each module holds two additional cpu's (no memory) and occupies the hPCI module slot (a hot swap PCI case that can hold what looks like two to four pci cards). You can use up to 17 of the hPCI module slots to hold MaxCPU modules. (there are 18 pci channels on the system, and at least one must be used for accessing the boot disk).
So there ya have it, 106 cpu's and half a terabyte of ram. I think that in most cases, folks will opt to not use the MaxCPU modules and just stick to the 72 cpu limit.
"Wow, look at all the hits we're getting on the Starcat shopping cart! We're going to make a mint on these suckers!"
"Huh? I understand that the nation's air traffic controllers may need updated equipment in light of the existing crisis, but how hard can scheduling be? I could see a use for a massively parallel monster like this in, say, flow-through or structural analysis or something, but scheduling? "
What your missing is that this isn't a matter of airtraffic control. This is a matter of determining which planes and crews to fly to which locations at what times to maximize revenue. This is a classic, big, nasty travelling salesman problem. The bigger of a beast of a machine you get, the closer you get to an optimized solution. I.E. Most passengers willing to pay this most money with the least use of resources. It's a huge problem that needs massive computational power.
According to the specs each processor board holds 4 processors and 32 gigs of memory.
Now, if the starcat treats domains (partitions) the same as the E10k (I haven't been to training yet on it), then each domain at minimum will consist of 4 processors and 32 gigs of ram, ie 1 processor board. Basicaly these doamins are treated as seperate boxes as far as Solaris is concerned. You configure a domain to say contain 2 system boards, and then when you load Solaris, it then sees 8 processors and 64 gigs of memory. This way you can allocate resources as the need fits. But this means it doesn't look like the virtual processor that mainframes present.
The starcat may deal with processors above 72 in a different way, but I honestly don't know at this time how it deals with them.
Hope this helps answer your question.
"If you insist on using Windoze you're on your own."
We all know strncat() is better.
Liberty in your lifetime