17 ms·
AMD Killed the Itanium (2005)
- bluedino 4y agoItanium never had any software except HP/UX It was also incredibly expensive. It was never "alive" and would have died on its own.
- mnd999 4y agoI’ve definitely used Windows on it.
- bluedino 4y agoAnd probably also Linux. Windows was ported to quite a few platforms, but none of them mattered except x86
- robin_reala 4y agoOpenVMS bet fairly big on Itanium too.
- FullyFunctional 4y agoDebian, Redhat, and SuSE all supported it for several versions. I have Debian on mine.
- mnd999 4y agoActually, I don’t think so. I think I did user a prototype Monterey internally at IBM though. I did an internship there testing JVMs back in the day.
- mpol 4y agoAMD was more like the last straw that broke the camel's back. Itanium was already in trouble. It was hot (really hot) and underperforming. It wasn't selling really well, since it was too expensive. Of the UNIX vendors, only HP was left standing behind Itanium. IBM had already long pulled out of Itanium and also out of Monterey, the UNIX that would unify all unixes. AMD64 was the light that suddenly came shining and everybody knew that was where everybody was going.
- threatripper 4y agoItanium is something that sounds good in theory but didn't quite deliver in practice. It is my impression that this is how things usually turn out when you do top-down design of a new product. Maybe my impression is wrong and it has nothing to do with top-down design and it's just that the majority of products fail. Maybe 99 out of 100 fail and you have to launch 100 to have a statistical chance to get 1 winner. Intel didn't launch 100 different processor designs. They surely have a dozen designs that got killed early but then they focused most of their energy on one design and that one failed. Not enough good luck probably.
- adrianmsmith 4y agoI'm sure you're right in general - but I would say that a counterexample, or the 1 in 100 top-down design of a new product that did succeed, is the iPhone.
- dsr_ 4y agoThe first iPhone appeared after five generations of iPod, and (I believe) was co-developed with the iPod Touch, the sixth generation.
- ghaff 4y agoFurthermore, there was no compatibility expectation with phones. In fact, there really weren't third-party apps for phones to any meaningful degree. Other than nerds, who knew what processor was in their Blackberry or Treo? Apple did reinvent the smartphone. But, like the iPod, it didn't fully hit its stride for a few years.
- fishtacos 4y agoIs it really co-development if it's the same device lacking a GSM radio?
- lp4vn 4y agoIf I remember well what I learned in college, the organization of x86 processors is superescalar, which means that the processor uses an internal statistics mechanism for predicting the subsequent code that's going to be executed. Itanium on the other side used the VLIW architecture so that the instructions are optimized for a long vector of execution of instructions already in compilation time. I always found the idea behind the VLIW processor architecture to be a quite good one to be honest, but I read many engineers in many places saying that it's a bad one and it was doomed from the beginning. The article says that the death of Itanium is mostly due to the disinvestment in the IA-64 caused by the threat of AMD overtaking the x86 market, even though the competition for the x86 market probably benefited all of us, I still find it a bit sad that there was this loss of architectural diversity and sometimes I wonder how well the Itanium would perform today if it weren't killed.
- m_mueller 4y ago.. and then Nvidia brought their GPUs to the clusters and ate both Intel’s and AMDs lunch with a better version of VLIW. The CUDA programming model and hardware IMO is quite successful at abstracting vectors the right way[TM], separating the problem of the grid setup from that of the kernel code (which you can still largely program in a scalar way if you’re not after the last ~30% of performance). IMO a shame that OpenCL never got good.
- wrp 4y ago> ...I read many engineers in many places saying that it's a bad [idea]... I read an article several years ago from an engineer at...ooh, I think it was DEC or IBM. He said that during development of the Itanium, the Intel guys had talked to them and they advised most strongly that Intel drop the project, because they had been down that road and thought it was a dead end.
- wtallis 4y agoSuperscalar just means the processor can execute more than one instruction at a time (in parallel, not just pipelined). The main distinction between VLIW and mainstream x86 is in how the instruction execution is scheduled: x86 cores track dependencies between instructions, and most support reordering instructions to deal with stalls from things like cache misses or the next instruction being of the wrong type for any of the free execution ports. VLIW relies on the compiler to schedule instructions, so that the hardware does not need to do dependency tracking.
- hulitu 4y agoA simplistic story. As far as i know, Itanium delivered too little, too late. The fact that UNIX vendors (SGI, SUN) preferred AMD as a second platform shows how good the AMD was at the low end of the spectrum compared to other offerings.
- ck45 4y agoNice story, but it doesn't fully add up: "When Intel started Itanium development work in the mid 1990s" That's more than a decade after AMD releasing their first x86 compatible CPU. Intel was very aware of the threat before they started the work on Itanium. They even tried to hold back AMD with a lawsuit which they lost and ultimately allowed AMD to release their 80386 compatible CPU. I find it more likely that it failed for similar reasons why iAPX 432 and i860 failed. There just wasn't a market.
- beebeepka 4y agohttps://jolt.law.harvard.edu/digest/intel-and-the-x86-architecture-a-legal-perspective https://jolt.law.harvard.edu/digest/intel-and-the-x86-archit...
- FullyFunctional 4y agoYeah this isn't quite what happened. Firstly, Intel didn't start Itanium, HP did, as a successor to their HP Precision line. I forget how they got together, but it was a collaboration between Intel and HP, but HP started it and had largely the architecture defined before Intel got involved. Secondly, it's true that AMD hammered the nails in the coffin, but AMD wouldn't have mattered if Itanic had been faster, cheap, and on time. Itanic was a disaster partly because of overly complicated design by committee and partly because of the fundamentally flawed assumption (that you don't need dynamic scheduling, AKA OoO processing). I have an Itanium in the garage, a monument to hubris. UPDATE: I forgot to mention that from the outside it might seem that Intel had a singular vision, but the reality is that there were massive political battles internally and the company was largely split into IA-64 and x86 camps. UPDATE2: Itanium was massively successful in one thing: it killed off Alpha and a few other cpus, just based on what Intel claimed.
- hinoki 4y agoI thought the biggest problem with Itanium was the fact that it was optimising the wrong thing; it maximised single thread performance by going all in on speculative execution, but it turns out that optimising joules per instruction is much more important.
- ghaff 4y agoCertainly one of the issues with Itanium was it was fighting the last war. It was trying to optimize for instruction-level parallelism when power efficiency and thread level parallelism were coming into vogue. Arguably companies like Sun overoptimized for the latter too soon but it was the direction things were going. A senior exec at Intel told me at the time the focus on frequency in the case of Netburst was driven by Microsoft being uncomfortable with highly multi-core designs--and I have no reason to doubt that was one of the drivers. There was a lot of discussion around the challenges of parallelism, especially on the desktop, at the time. It generally wasn't the problem the hand wringing suggested it would be.
- zozbot234 4y ago
- nullc 4y agoOne of the finest illustrations on all of Wikipedia, perhaps on the entire Internet: https://en.wikipedia.org/wiki/Itanium#/media/File:Itanium_Sales_Forecasts_edit.png https://en.wikipedia.org/wiki/Itanium#/media/File:Itanium_Sa... I have itanium on a shelf somewhere-- while I was using it I got to do some assembly level debugging to track down a report a GCC bug I hit. Well worth in entertainment the $50 or whatever I paid for it.
- pengaru 4y agoAny purported explanation of Itanium's failure that doesn't even mention compilers once is at best incomplete. > I won't be surprised at all if the whole multithreading idea turns out to be a > flop, worse than the "Itanium" approach that was supposed to be so > terrific - until it turned out that the wished-for compilers were basically > impossible to write. > > - Donald Knuth 4/25/2008 in InformIT [0] [0] https://www.informit.com/articles/article.aspx?p=1193856 https://www.informit.com/articles/article.aspx?p=1193856
- Quequau 4y agoYears ago I read an interview of one of the upper managers of the project and his very brief post mortem was because Intel was focused on shipping only very high end chips, few to none of the usual people and processes that were responsible for the development of open source development tools had convenient access to the chips and so no motivation to do that work. That in turn forced Intel to do it and by the time the people making the decisions were convinced of that the willingness to spend money on the project had evaporated.
- deleted 4y ago[deleted]
- Qem 4y agoWas this assuming ahead of time (AOT) compilation? Would Just-in-time (JIT) compiling help pull it, by taking advantage of runtime information?
- ilyt 4y agoIn a way he wasn't wrong - not many compilers and languages will auto-parallelize the code, you need to explicitly build it the way that enables it to run in parallel The other part however is complete miss >Let me put it this way: During the past 50 years, I’ve written well over a thousand programs, many of which have substantial size. I can’t think of even five of those programs that would have been enhanced noticeably by parallelism or multithreading. Surely, for example, multiple processors are no help to TeX.[1]
- snvzz 4y agoAMD could, as easily if not more so, be the one to show up with a native RISC-V processor that has a legacy x86 mode. In the modern landscape, it'd be closer to a v86 mode, where the hypervisor is RISC-V, but user x86 applications can run full speed. All the legacy PC platform crap can be done away, replaced by RISC-V standard OS-A profile.
- hkgjjgjfjfjfjf 4y ago[dead]
- als0 4y agoWhy would AMD do that today though? They are in a privileged position to have an x86 license and zillions of customers asking for an x86. AMD once made some ARM chips and realised they didn’t need to.
- jeroenhd 4y agoAgreed. The only reason I can think of for AMD to set up an alternative instruction set would be a sudden rise in competition from other players. If big advances are made in the RISC-V space that make the architecture a cost effective alternative to amd64 (including the cost of porting software to RISC-V) then I can see them setting themselves up to allow running software on both platforms at native speeds. I don't think AMD is currently limited by their instruction set. Even if they are, there may be an argument to move to ARM instead of RISC-V to take advantage of the software already ported because of Apple's transition and the Graviton chips. Windows already runs on ARM but hasn't been announced to run on RISC-V, after all.
- snvzz 4y ago>would be a sudden rise in competition from other players. This is exactly what I see happening. AMD will have to move to RISC-V to stay competitive, and x86 acceleration is a compelling feature they can offer. >Windows already runs on ARM but hasn't been announced to run on RISC-V, after all. I doubt this one will be an issue for long. During last summit, in talks by the RISC-V foundation itself (specifically, the technical ones about ongoing ISA work), Windows was mentioned a few times as the reasoning for some new specifications. This strongly implies Microsoft is working on Windows for RISC-V, even if Microsoft themselves haven't said a word about it.
- jeffrallen 4y agoNeeds a 2005 tag, but it's a great story anyway.
- _ph_ 4y agoOf course the whole story is way more complex, but I have been saying for years that the Itanium might have succeeded, if AMD had not extended x86 to 64 bit. The 64 bit extensions did not only fix some of the x86 problems (it increased the register count, pushed 64 bit double floats) but it made x86 a choice for the more serious compute platforms and servers. Back then, the whole professional world had switched to 64 bit, both from a performance and memory size perspective. That is why the dotcom time basically was based on Sparc Suns. The Itanium was way late, it still was Intels only offering in the domain. Until x86-64 came and very quickly entered the professional compute centers. The performance race in the consumer space then sealed the deal by providing faster CPUs than the classic RISC processors of the time, including Itanium. It is a bit sad to see it go, I wonder how well the architecture would have performed in modern processes. After all, an iPhone has a much larger transistor count than those "large" and "hot" Itaniums.
- rwmj 4y agoAt the time there were computers containing Alpha chips with quite a PC-ish design. I nearly bought one, so they were semi-affordable. They ran Linux well. So it seems a bit more likely that these might have succeeded if AMD hadn't extended x86. What you also have to remember is that Itanic was a very weird architecture. It's hard to write compilers for it, and it made the cardinal error of baking microarchitectural decisions into the ISA.
- inkyoto 4y agoYeah, by mid-2000s most RISC workstations (Alpha, Sun, SGI, PowerPC tho not IBM POWER and certainly not the top of the range datacentre class servers) had converged on the mainstream PC architecture, e.g. a PCI bus, EIDE disk controllers, standard PC memory (168-pin DIMM's and such). I had a Sun Ultra-10 as the sole «PC» at home for some years running Solaris and later Linux. After quickly getting fed up with the standard Sun keyboard, I bought a generic, no-name USB PCI card, plugged it into my Ultra-10 and connected a Microsoft Natural keyboard. It just worked, with Solaris not even requiring extra drivers or kernel modules by virtue of being a USB keyboard.
- 4y ago
- pajko 4y agoItanium killed itself.
- znpy 4y agoIf itanium would have succeeded, what could the computing industry be like to day? What were the supposed advantages of itanium over x86?
- flohofwoe 4y ago> If itanium would have succeeded, what could the computing industry be like to day? Intel probably would have left the CPU market by now, and one of the promising workstation RISC ISAs of the 90's would have replaced x86 instead (like Alpha). > What were the supposed advantages of itanium over x86? Itanium went full in on VLIW (https://en.wikipedia.org/wiki/Very_long_instruction_word https://en.wikipedia.org/wiki/Very_long_instruction_word), but that bet didn't work out in the real world.
- cubefox 4y agoThe VLIW article sounds like VLIW is great. If so, the problem was not with VLIW, but with the fact that switching over to a complete new architecture is hard, and basically impossible when AMD at the same time creates pressure on the legacy front.
- zozbot234 4y agoVLIW has some annoying issues. The Mill proposed architecture is basically a tweak on VLIW, adding a number of features to make it easier to write software for and a variant of runtime scheduling that's quite simplified compared to OOO.
- userbinator 4y agoNeeds a (2005) in the title. I do wonder what x86 would've looked like if Intel was the one to extend it to 64-bit, given that 32-bit x86 already had a few reserved extension points that appear to have been put there precisely for this purpose.
- deleted 4y ago[deleted]
- hulitu 4y agoWell just look at "multimedia extensions" (i.e. mmx, 3dnow, avx, sse etc). It would have become a mess with every vendor having its own 64 bit extension, in my opinion.
- cubefox 4y ago[2005]
- deleted 4y ago[deleted]
- flohofwoe 4y agoI find it incredibly fascinating how the x86 prevailed again and again even though it was a compromise and stopgap solution right from the start (because the "proper" modern Intel CPU of the 80's was supposed to be the iAPX 432).
- Narishma 4y ago'Worse is better' seems to also apply to hardware.
- xorcist 4y agoItanium can be regarded as a huge success. Maybe some don't remember, but the minicomputers and unices were where all the money was. Sure, Intel had the process edge, and had completely cornered the microcomputer market. But PCs had slim margins and didn't really matter in the bigger scope important data processing. Many of the computer nerds watched in awe as vendor after vendor dropped their hugely expensive and engineering heavy custom CPU architectures and lined up behind Intel. IBM was the only big player who didn't swallow the bait. "Even if they fail, that's a huge success" was a common observation at the time. And sure enough. I don't think they failed on purpose, but business wise it was a win-win situation. The x86 architecture would have won anyway, because of the sheer scale, but the Itanium wreckage hastened it. Everyone needed to move, so why not move to x86/Linux directly?
- andromeduck 4y agoComment I saw on YouTube a while back: > In some ways Itanium was the most successful bluff every played in the tech industry. In much the same way that Reagan's Star Wars bankrupted the Soviet Union got almost every single competitor to fold. Back at the beginning of the project, Intel was nowhere in high-end & 64-bit computing. There was HP (PA- RISC), Sun (Sparc), Dec (Alpha), IBM (Power), MIPS (SGI). Intel wisely picked the partner with the stupidest management (Carly) to give up their competitive edge and announce to analysts that Intel's vision/roadmap is so awesome that RISC is dead and that they're going to follow the bidding of their master Intel for their 64-bit plan. Wall Street bought in to the story so much that almost everyone else with competitive chips folded their strong hands to Itanium's bluff - SGI spun off MIPS and MIPS decided to leave the high-end space. Compaq undervalued Alpha and let it die. Sun tried to become a software company and if it weren't for Fujitsu making modern sparcs, sparc would be dead. > Basically, with nothing but PR and Carly's stupidity, Intel wiped out over half of the high-end computing processor market. > Thankfully AMD had the vision to see through the bluff, and saw the opportunity for 64-bit computing that worked; and thankfully IBM didn't have someone like Carly around so they saw the value in retaining competitive advantages; or the computing world would be pretty bleak place right now..
- xorcist 4y ago
- deleted 4y ago[deleted]
- jmyeet 4y agoAny story trying to argue Itanium was a success is (IMHO) historical revisionism. When this was conceived, Intel’s view was somewhat consistent with Microsoft were others. Remember that at one point Windows NT ran on other architectures (eg DEC Alpha, MIPS). At this point Intel wanted to solve the compatibility issue by booting on an x86 chip essentially. The article mentions this part. In the 90s AMD (and Cyrix) had competitive 486 parts due to due to some old licensing agreements. Intel wanted to end this with a new architecture. But then Itanium was delayed and really expensive. At the same time AMD invented the x86-64 extensions and released Athlon, which was much cheaper and has a much easier path to 64 bit. Due to those same licensing agreements Intel was entitled to those extensions, copied x86-64 and the HP-Intel Itanium died. In the early 2000s Intel was in a tough spot. They’d defeated the 486 competitors with Pentium. This was the last clock speed race. But Intel hit the 3GHz barrier. The only thing that saved Intel was their mobile chips (ie Core Duo). They didn’t have clock speed but they had efficiency and performance. At the time you could find articles where enthusiasts found ways to build desktops out of Core Duo chips. They were that good. But Intel tried to milk Pentium just a little too long. Athlon forced their hand, particularly when Opteron started gaining server market share. Opteron destroyed the last hope Intel had of forcing the proprietary EPIC architecture down people’s throats. The Core Duo was so successful it is still on the DNA of today’s Intel’s CPUs. It’s where the branding “Core” originated. It saved Intel.
- ghaff 4y ago>But Intel tried to milk Pentium just a little too long. And Intel was showing off an around 10GHz, probably water-cooled, Netburst architecture CPU at the Intel Developer Forum at one point. As I mentioned in another comment, a senior Intel tech exec told me at the time folks like IBM's Bernie Meyerson were basically going around making fun of Intel for not understanding the issues with leakage current and so forth something like: Of course, we know this stuff. But Microsoft really wants frequency, rather than multi-core. My conclusion is that Intel leadership really thought they could turn the frequency crank once or twice more. And they really couldn't.
- jl6 4y agoThe timescales are just incredible. Despite the article declaring Itanium dead in 2005, sales continued for another 16 years and HP still offers support until 2025.
- antisceptic 4y agoIt's hard not to root for AMD when Intel has a track record of sitting on their hands whenever they become the market leader.
- einpoklum 4y agoAlso, sitting on other people's hands...
- jeroenhd 4y agoAMD did the same when they got an advantage through Ryzen. Intel quickly overtook them again and now they're back to being the underdog. Threadripper got killed off because it was starting to compete with AMD's own products, performance increases started to diminish, AMD very much took a short break when were at the top again. The only difference is that Intel managed to stay on top with their Core architecture for so incredibly long. That's not necessarily bad, of course. This behaviour has led to competition and competition is almost always good for the consumer.
- fishtacos 4y agoOpenly an AMD fanboy, but this year's offerings by Intel were too good to pass up in comparison, as I was due for an upgrade. Same with NVIDIA - instead of AMD went with them. It's good to have competition in the market.
- acdha 4y agoThe reason Intel gets more negativity here is that time and again they try to prevent fair competition. Itanium was an attempt to break AMD’s ability to sell x86, and each of the previous times AMD was providing better performance or pricing, Intel used their market position to require things like exclusivity or minimum volume commitments. Given how well competition has worked for consumers, I do wonder if there’s some regulatory option here to reduce those back room deals. Given the way the world runs on microprocessors now there’s a decent argument that maintaining a robust market is like what we used to do to prevent one railroad or steel company from getting too much control.
- twoodfin 4y agoIn their pre-disappointment dreams, did Intel ever imagine the Itanium architecture coming to commodity PCs? Intel is well-known for their decade-long roadmaps, and if Itanium had succeeded and consumer-class machines had been in their sights, they would have needed a part on such a roadmap. But I don’t remember ever hearing about it. They must have been planning to segment the market, possibly more aware than most that if they didn’t, fast, low-margin x86 had a good chance of winning everywhere. I guess they did alright with Xeon.
- acdha 4y agoThat was mentioned but even at the time it was described as a long way off (5-10 years). They were explicitly targeting PowerPC so they definitely wanted to say they’d be able to beat it but nobody could pretend that what they were building at first was going to be a comparably-sized chip.
- tyingq 4y agoI think improved horizontal scaling also had a big role in killing off Itanium as well as all the traditional RISC vendors. Load balancers, high throughput local networks, distributed caches, etc, became common and reliable. Which pushed the purchases of bigger RISC servers to niche things like huge database servers. That left little room for Itanium to be cheap, because it was competing only in the high end, with less economy of scale, more expensive peripherals, etc.
- ghaff 4y agoAn enormous amount of effort, some small corner of which I was involved with, went into vertically scaling x86. And, at the end of the day, it was pretty much a waste of time, effort, and money.