Intel's Itanium 2: Succeed or Fail?
An anonymous reader writes "'Intel's most powerful processor ever has the ability to take on IBM, sink Sun, make or break HP, and crush or revive AMD,' says Fortune's David Kirkpatrick. But the 64-bit question is what happens to the heavyweight competition if Itanium 2 succeeds or fails?"
Yeah, if intel's new chip is a hit then the company will profit more. In other news if intell gains market shares then AMD will not have those same market shares.....i should be an econmic analyist.
As Intel now loses its backwards compatibility, they also lose their biggest advantage. Sadly, the IA64 will probably lose out to less spectacular, but IA32 compatible designs.
Alpha tried to emulate the x86 earlier and failed. Sadly.
Wait..I have heard that before....
Neck_of_the_Woods
#/usr/local/surf/glassy/overhead
I've worked on 64-bit conversion projects for applications on HP-Unix, and it tends not be as trivial as it should be. I'd compare it to converting a 16 bit Windows app to 32-bit Windows. Yes, both should be trivial, but there are enough gotchas! On a per line of code, the Windows conversion was probably more involved, but then that was because it wasn't written as well - eg. assuming an "int" is 16 bits long.
RB
Itanium/2 is a 64 bit processor. So it needs 64 bit software, including the OS.
Umm, no. For example I am running 32-bit Solaris on a 64-bit UltraSPARC. And applications compiled 32-bit.
Whereas in the case of Windoze, the 32 bit stuff (and even some 16 bit stuff) is built right in to the API.
Yes, that's why it's called the Win32 API. Work is well under way on Win64, but in Microsoft's ideal world, almost no-one will write to the Win64 API - they'll target the CLR, which itself will be 64-bit native.
Then the millions of apps that people use, right now an excellent way to lock customers in, are going to turn into a lodestone around their necks.
Yes, just like when Apple moved from 68k to PPC? Nope, wasn't a problem.
I'm sure Micro$oft is pissed as hell, but Linux is going to take a huge upswing when Itaniums start flying off the shelves.
That doesn't necessarily follow either. After all, Win 3.11 didn't fully exploit the 80386 either, and it wasn't 'til the first NT that Microsoft did.
It's already happening, you just haven't noticed it yet.
Jon.
I think the author has it backwards. He says if the new chip fails then blah. However, the more coherent argument is that if blah happens, then Intel's new chip has failed.
But, the author doesn't seem to realize that there's more than just out and out success or failure on the spectrum. It's more likely that there will be incremental change. Intel sells X units to A, B, and C, AMD sells Y to D, E, and F, and IBM, SUN, and co. sell to whomever. And things kinda ballance out.
All this new technology that's supposed to change everything dramatically, changes things to the degree that it's touted to. My money is still on evolution rather than revolution.
In mathematics, one does not understand things, one merely gets used to them.
--VonNeumann
Is it possible to have a motherboard with two processors, a P4 and an Itanium? The core OS could run on the Itanium and non-Itanium stuff could get executed on the P4 processor(s).
I'm sure this is a stupid idea that many other posters will point out the weaknesses of, but I'm wondering why it couldn't be done.
Plus, less power consumption could mean thousands or tens of thousands depending how many servers you have. If you're google or some other huge site with thousands of systems, the power savings means lower operation overhead.
Well, the trend broke in 2001 when people started to notice that the machines needed for this generation of software was not the fastest but the slowest machines on the market. That most users did not need a top end machine and instead could buy the slowest processor out there. During 2002, the same came true for lap tops. Now everyone is swimming in so much wasted CPU power that it is going to finally crush those that can't adapt to radically lower needs compared to what Intel and their competitors are churning out. Ask someone who runs a computer room and they will tell you that they are quickly consolidating old servers that cost $250K three years ago to a server that costs $15K and only takes up a quarter of the room.
Intel is in real danger of not surviving because it does not understand where we will be in 5 years. 5 years ago when they were in the middle of this effort they did not see our need for speed slowing dramticly and are now producing a chip that has such a limited market that it will never be profitable with all the investment that was in put in.
When you look at how a company responds to the typical S curve of development, they may make the first curve but often that screws up their timing on the second curve and they just go off the cliff.
NT Alpha is both a 32Bit version and has been EOL'd (Although it lasted longer than NT PPC).
Windows 64 is due out Real Soon now, and it's delay is likely at least half the reason the Athlon 64 has been pushed back.
Itanium 2 is going to have to make up for the pathetic performance of the first revision (Which seems to perform on par with a Via C3)
"You've got an invalid haircut" -Warren Zevon - Life'll Kill Ya
It is something of a question whether this change will open up opportunities for new software. I think it will. Think shared memory -- very large memory spaces being simultaneously updated and accessed by multiple independent processes and processors performing different tasks possibly for different users. The three drivers of technology are corporate databases, games, and pornography. Huge memory spaces with multiple processors attached have many possible breathtaking applications in each of these domains. Start coding.
I think the success of the Itanium not only rests on its technical merits but more importantly it rests with how much mindshare they can get for the product with the business people who, more often than not, end up making technical decision in a void.
I think that Intel is aware of this. Marketing can make the product. The best engineered solution does not always win out.
Sun are still scheduled to release the UltraSPARC-IV this year (at last report) which will be dual-core (same as Power4) and might again leapfrog IBM for a while.
Sun aren't doing that badly, all things considered, given the current state of the economy. We'll see how things pan out over the next few years, but it's too early to say Sun/SPARC is dying.
The main problem is that the theory sounds good, but the reality shows a LOT of problems. The Itanium is a VLIW processor, which is quite different from the more traditional RISC and CISC designs of other chips. The idea is rather similar to the difference between RISC and CISC (which, these days, are more or less the same thing), move more of the optimizations into the compiler to make the chip design more simple, thereby allowing more money to be spent on fatter pipes, bigger caches, etc. for the chip.
The problem though, is that it's often EXTREMELY difficult for compilers to effectively optimize software for VLIW chips. Since the Itanium has no out-of-order execution or branch prediction, these things have to be done entirely at compile time. The compiler needs to organize the software so that the chip is constantly being fed with data rather than having the chip dynamically rearrange some instructions if others are sitting waiting for data. It also needs to include it's own concept of branch prediction, suggesting which branch is more likely to occur. What's even worse (and which I rarely see mentioned) is that it has to optimize it's software for a particular chip design rather than an architecture, ie Itanium software needs to be recompiled for the Itanium2 in order to see many of the benefits of the new chip.
As far as manufacturing goes, that's comparatively easy for Intel at least. There they just have to put up with a huge die and extremely high power consumption. Not exactly a cheap chip to manufacturer, but manufacturing chips has always been Intel's specialty. Also, the high selling price of the Itanium means that Intel can afford quite a bit of leeway.
Anyway, long story short, the big problem with the Itanium/IA64 in general is that it's a design that is VERY difficult to optimize code for. It requires a very good compiler to begin with, but even then there are simpily some optimizations that just can't be done at compile time, and those situations will hurt the performance of the IA64 chips a lot. If Spec CPU2000 scores are anything to go by, the things from CINT (ie databases, compression, FPGA design, compilers, etc.) are much harder to optimize for IA64 than CFP (mostly scientific computing applications).
Actually, I don't mind the idea of breaking X86 compatibility - I just object to breaking it for IA-64. IA-64 was conceived in a time when it was felt that Out Of Order (OOO) execution was going to be too tough a nut to crack.
In less time than Intel and HP took to go off and crack the VLIW/EPIC problems, other design teams learned to handle OOO, and do a very good job of it. They appear to have succeeded, and have a leading-edge part - but at what cost. AFAIK, the IA-64 is the most expensive CPU ever made.
The latest-out CPU usually does seem to hold the performance crown. But IA-64 doesn't seem to hold it that solidly, and there's question about whether the latest Alpha iterations have been allowed to fully appear - for fear of embarassment.
IA-64 looks almost like a government project gone wild. It has produced results, but IMHO horribly inefficiently. Pushing a more reasonable (not necessarily more conventional) architecture might well have yielded better results.
The living have better things to do than to continue hating the dead.
Don't be so quick to predict the demise of Itanium. I would question your analysis based on past history of Intel products.
1. Heat - has been an issue since the 8087 and lower power products or improvements in heat removal technology have continuously become available. Even in current Itanium/Itanium 2 (Itanium Processor Family - IPF) products, heat is an issue but not one that is preventing IPF products from shipping. Over time you will see a significant reduction in dissipation in Deerfield/Monticito (SP?) but, in any case, solutions to the heat issue are becoming available.
2. Cost - Intel products are only expensive while customers are willing to pay high prices for them. Any time Intel has had competitive pressures, they have been able to drop the price to meet the new price point OR introduce new products that allow them to maintain their margins.
3. Nobody seems to understand that there is an IA-32 processor core built into the chips (starting with McKinley (Itanium 2)). For backwards compatibility, it's really an operating system issue more than a hardware/software emulator issue. When the operating systems are properly implemented, IPF will be able to run 32-bit IA-32 applications concurrently with 64-bit IPF applications. When Linux supports this, I think you'll see interest in Hammer wane.
4. I would disagree with your comments on the people who want 64-bit already have them. I would not disagree that there are limited projects testing out different 64-bit architectures, but I would be very surprised at there being any large server farms out there with the latest incantations of Power or Alpha and the SPARC/MIPS are probably looking for an upgrade.
5. Itanium is ideally suited for Linux. I agree with your comments with regards to Windows - but when you are upgrading to a new Linux release don't you rebuild/retest the application to make sure it still runs? In our Linux systems we have been able to port directly from IA-32 to IPF without any changes to application software.
I believe that there is a lot of opportunity in the market for a "standard" 64-bit processor and this is what IPF is designed for. IPF may not be the best or the first but they do have the track record in taking over a market and maintaining it. Nobody has made a lot of money betting against Intel and nobody has ever gotten fired for choosing their products.
One of those sheep, sadly enough, is Shawn Robison, the CTO of HP. Mike Capellas brought him onboard at Compaq, whereupon he shoved aside all of the technical gurus from Digital, and then brought him over to HP and left him to continue to kiss Bill Gates' ass (and Steve Ballmer's) after Curly was lured away to eviscerate Worldcom. Robison is well-known as a Wintel Weenie - he thinks that Windows will ultimately rule the world and he wants it that way. He absolutely hates Unix in any form, be it Tru64 UNIX or HP-UX. The problem is, his high-end customers, the few that he has left, know better and continue to insist on high-end Unix systems. It doesn't take much analysis to figure out who some of the early non-commercial customers are for Marvel and the other associated products.
It is interesting that HP's Longview, Colorado labs developed Itanium2, and did so untainted by association with the Alpha Development Team, which was sold/indentured to Intel. It remains to be seen if Intel will be smart enough to merge all of the technology that they've stolen, er "bought", over the last few years, and be able to field a saleable product.
As for the heat dissipation, etc., well, that's been a laughable issue for many, many years, and won't change. It should be fairly obvious that the more transistors you cram into a single die, the more heat you're likely to need to dissipate. Intel laughed at Digital's initial Alpha chips because they did indeed dissipate more heat than the '486 chips shipping at the time. By the time Intel had fabricated a few Pentiums (at 60 and 66 MHz, for the software developers to have a realistic platform to use to port their software), Digital had built another generation of EV4's, at a higher speed and about the same heat, by lowering the voltage. Intel finally looked over their shoulder at Digital, and realized that they (I) simply couldn't continue to build complex microprocessors with a 5V Vcc, and started reducing the voltage. Of course, when Intel did all that, it became _acceptable_ to have a large heatsink and fan in one's computer. The fact is that Intel copied a great deal of what Digital pioneered and then made it look like they'd invented it.
As far as I'm concerned, Intel's plagarism and unethical business practices rank in the same cesspool as Microsoft's. Unfortunately, as long as there are assholes like Robison in positions of authority (yeah, Cartman comes to mind), the rest of the industry will suffer for it.
I run Linux on an SMP Athlon (2xMP1800+) for those reasons, and many others.
There are chips out that come close. The new C3 processors (VIA) run at 1 gigahertz. They also use 15 volts of power and dissipate under 10 watts of heat. And then there's VIAs Eden, which is an embedded processor platform (yes, it will run linux) that runs up to 1 gigahertz, IIRC. And according to them, it uses up to 1.2 volts and dissipates up to 6 watts of heat. And that's less than 1/10th.
And it's not only about power consumption. A lot of people have gotten sick of machines that sound like lawnmowers, and are going to the quiet side. Quiet is the new Overclock. You now can have a 2 gigahertz machine that only puts out 20 decibels of noise at 1 foot.
"Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
I don't see how a new processor from Intel, or anybody else for that matter, is going to cause "serious competition" for any vendor such as HP, IBM, or Sun. When choosing a solution, IT doesn't go for Sun because its run on a Sparc CPU. They don't choose IBM because it runs a PowerPC. I give up on why they choose HP. :)
The point is, the CPU is just 1 little part in a solution. Intel isn't going to do any damage to these vendors unless they supply the entire solution, which isn't their business! To think otherwise is pretty dumb and a bunch of PR bullshit attempting to inflate Intel's stock value.
A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin