Itanium Problems
webdev writes "An article in today's NYTimes (free but...) highlights some industry concerns over Itanium. The author suggests the normal "what's bad for Intel is bad for the computer industry". Anyone know the power consumption for IBM's 64 bit effort GPUL?"
I'd venture to say that IBM's processor uses little more power than other PowerPC CPUs. Doesn't it sport SOI and other technologies to limit heat production? Heck, for an--albeit moderately poor--example of this is IBMs 750FX processor vs. the P4. At the same clock speed, the 750FX would consume roughly one fourth the power of the P4.
The Political Programmer
"It has taken an entire decade, an estimated $5 billion and teams of hundreds of engineers from the two companies to bring the first Itanium chip to market. As the struggles and costs mount for the companies, skeptical technologists say Itanium now has the hallmarks of a bloated project in deep trouble. It is already four years behind schedule, emerging just as companies are in no mood to spend money on technology"
Skeptical? More like, forget it Chachi, it ain't happening.
I guess the larger companies don't get it. Corporations are struggling. Companies are in holding patterns, waiting for the mess, erm, economy, to level off.
Can I have a job now making millions being a skeptical technologist?
Sent from your iPad.
...friend!
I just read a story on msnbc.com about AMD's 64bit processor, I close the window, check slashdot and there is the story about Intels Itanium. Anyway here is the link for msnbc. http://www.msnbc.com/news/813950.asp?0si=-
In college, really poor, need a flatscreen.
"Every big computing disaster has come from taking too many ideas and putting them in one place, and the Itanium is exactly that," said Gordon Bell, a veteran computer designer and a Microsoft researcher."
He should follow that up by saying, "Here at Microsoft we have proved this time and time again."
http://www.hp.com/products1/itanium/performance/ar chitecture/speccpu.html
-Kevin
AMD's x86-64 architecture will allow companies to upgrade individual parts of their software systems to 64-bit without having to replace everything else. That's the key to AMD's future success; it makes the migration path to 64-bit that much easier (and that much cheaper).
Itanium flopped before; chances are good it will flop again.
Only if you try to overclock it.
"They do not preach that their god will rouse them, a little before the Nuts work loose." Kipling, 'The Sons of Martha'
He's absolutely correct. The most intelligent thing to do is to make insignificant, incremental changes, and charge customers full price for each of them.
Jesus was all right but his disciples were thick and ordinary. -John Lennon
We've ported chemistry simulation code to the pre-release ITA-2, and run benchmarks. There's not much like it, performance-wise, and on a cycle/dollar scale, it's in a class by itself. Smokes US-IIIs, walks away from the Alpha, and keeps pace handily with the Power4, at a more academicly-tolerable price. It's a good chip in its second incarnation, and has the misfortune to be introduced during a recession.
As always, the NYT ignored that you'll need the 64-bit address space for large applications, it has excellent memory bandwidth, and those customers requiring such a system weren't explicitly interviewed or mentioned. The heat issue is true, and that's it's one failing, but as with the Alpha, it will get better in time. (I still remember the rumors, pre-release of the Alpha that DEC was going to have to build a liquid-cooled workstation)
...can you imagine a beowulf cluster of these?
In fact, I know from a reliable source that tomorrow the president of the USA is going to reveal that the Iraqi army has managed to get hold of 2000 Itanium chips and is threatening to turn them all on and melt the Earth.
RMN
~~~
GCC already supports the Itanium and Intel has great code they could give to GCC in terms of optomization (Intel doesn't make money in the compiler business).
Wrong... Intel IS in the compiler business: they have their own compiler called "icc". They could give code to GCC, but they won't because it'll hurt their icc business. You'd think they'd be smart and release their optimizations to GCC to help their processors perform better, but Intel doesn't think this way. They want you to believe their slick marketing that their processors really are better, AND they want you to shell out for their compiler (which may or may not actually get those processors to perform well--you won't know until you pay up and try it out). Of course, how does this help all of us who use open-source software (which includes Google mentioned in this article), compiled by GCC? It doesn't.
Heaven knows they have a copy of MS's book on corporate behaviour when it comes to competitors.
Bad for Intel probably means good for the industry, as we won't have another half-assed chip shoved down our throats.
* Winners compare their achievements to their goals, losers compare theirs to that of others.
The Itanium relies heavily on exceedingly good compilers that will perform for the IA64 the same level of optimization that regular, on-the-fly predictive optimization do in RISC chips.
The main obstacle with this method is that Turing's theorem says static compile-time optimization will never work as well as dynamic optimization. This is because, roughly, the only way to guess what a program will do with a given set of input data is to execute it with its actual data set. Here is a link where a reader of The Register addressed this concern in 1999.
Is anyone aware of how well the limits predicting by Turing can apply to the compile-time IA64 algorithms?
--
Mad science! Robots! Underwear! Cute girls! Full comic online! http://www.girlgeniusonline.com/
Saddest sentence in the whole article:
"There are other benefits for Hewlett-Packard. The Itanium allows the company to eliminate both of its current 64-bit chips -- the H.P. PA-RISC and Compaq Alpha. That alone should save the company $200 million to $400 million annually in development and manufacturing costs, according to Steven M. Milunovich, an analyst at Merrill Lynch."
Yeah, HP and Compaq have been fine stewards of their engineering legacy...
"How to Do Nothing," kids activities, back in print!
Dynamic optimization is not restricted to hardware. Java Hotspot will do well with Itanium (if Sun survives), and I believe Smalltalk and LISP have dynamic optimization as well. The way I see it, Virtual Machines are the future of high performance computing. And yes, .NET is important for Microsoft to prosper in the non-IA32 world. (Although I hate it when the wicked prosper.)
In the future I envision every IT department having its own trash can sized nuclear reactor. No need for UPS.
I know this was a joke, but a lot of people won't understand how silly this comment is. A nuclear reactor can really be quite small... but all it will do for you is get hot.
A lot of people don't seem to realize that a nuclear reactor is really just a fancy steam generator. The nuclear pile gets hot (heat-- after neutrons-- is the primary by-product of a fission reaction) and that heat is used to boil water. Steam drives a generator which creates electricity from the kinetic energy of motion.
So a trashcan-sized nuclear reactor isn't such a fanciful idea. But the enormous closed-loop steam turbine generator attached to it may be somewhat unwieldy.
Now, if you want to talk super-high-efficiency fuel cells, you've got my attention.
Well, the steam generators don't have to be that big, actually. For example, there are steam locomotives in use which are about as powerful as similarly sized diesel locomotives, only their fuel consumption is a lot worse.
Anyway, you don't necessarily need steam either. There are those nuclear batteries used on spacecraft and shit like that. Terribly inefficient, but you get electricity from a nuclear reaction with no moving parts at all. And don't forget gas turbines, that many of the more modern nuclear powerstation designs are using. They can be a lot smaller than comparable steam generator systems. For example the Pebble bed modular reactor.