Sun To Release 8-Core Niagara 2 Processor 214
An anonymous reader writes "Sun Microsystems is set to announce its eight-core Niagara 2 processor next week. Each core supports eight threads, so the chip handles 64 simultaneous threads, making it the centerpiece of Sun's "Throughput Computing" effort. Along with having more cores than the quads from Intel and AMD, the Niagara 2 have dual, on-chip 10G Ethernet ports with cryptographic capability. Sun doesn't get much processor press, because the chips are used only in its own CoolThreads servers, but Niagara 2 will probably be the fastest processor out there when it's released, other than perhaps the also little-known 4-GHz IBM Power 6."
Yes, but.. (Score:2, Funny)
Will it be water-cooled? (nt) (Score:3, Funny)
Re:yes but ... (Score:4, Funny)
Freudian Processor? (Score:3, Funny)
Niagara (Score:2, Funny)
Re:Yes, but.. (Score:4, Funny)
It has a Vista emulation mode - move the power switch to OFF and you get something just as useful but more stable.
Re:Yes, but.. (Score:4, Funny)
No, Vista requires 640 cores, which ought to be enough for anybody.
Re:Will it be water-cooled? (nt) (Score:3, Funny)
CURSES! (Score:1, Funny)
How dare you correct your own mistakes!
I, and my fellow grammar Nazi overlords, were just about to rip your lousy post to shreds.
Re:CURSES! (Score:3, Funny)
Re:Yes, but.. (Score:3, Funny)
Re:Freudian Processor? (Score:5, Funny)
That's not fair! (Score:2, Funny)
Re:That's not fair! (Score:2, Funny)
Threads Are the Work of the Devil (Score:3, Funny)
Wow! Only 64 threads, eh? That's the problem with threads, you can't have too many of them because switching from one thread to another is very expensive, cycle-wise. In other words, as long as threads remain the only multitasking mechanism used by the computer industry, super fast, fine-grained multiprocessing will remain a dream. It gets worse. There is another problem with threads that is even worse than this. Threads are inherently asynchronous. Until and unless the computer industry comes to its senses and realizes that asynchronous processing makes it impossible to implement programs with deterministic timing, we will continue to pay the heavy price of software unreliability. Switch to a non-algorithmic, signal-based, synchronous software model (with the supporting CPU architecture), and the problem will disappear. Threads suck! Period. One man's opinion.