13 ms·
The Itanic Has Sunk
- kstrauser 5y agoI had to maintain an IA-64 Linux system at a previous job, and it was such an odd duck. The OS did a decent job of abstracting away most of the weirdness, but at the end of the day it was just a very slow server. The compiler breakthroughs that Intel was counting on to make it competitive never happened, and since its unusual architecture made it bad at running code not specifically tuned to it, the end result was that nothing ran great on it. I’m sure that HP had some highly optimized code that ran like greased lightning, but that never worked its way out to the general public. I admit that I’m glad Itanium finally died. It killed a lot of other interesting architectures and gave nothing in return.
- h2odragon 5y ago> I’m sure that HP had some highly optimized code that ran like greased lightning, unwarranted optimism. I recall HP Pentium Pro servers with loads of "built in" stuff and dual PCI buses: all the builtins were hung off the 2nd, chained bus; on one IRQ. The memory was severely limited, too, iirc; NUMA'd through one of 4 CPUs. HP design seems to be all about locking performance away; it might be in that box in theory, but all their ingenuity was spent ensuring it stayed there.
- frjalex 5y ago> It killed a lot of other interesting architectures and gave nothing in return. What sort of architectures (if any) got killed as a direct result of developing IA-64? That aside, though odd and impractical, I found Itanium to be at least a technically interesting perspective (both in terms of architecture, ie VLIW, and in terms of the amount of technical work it inspired at HP and Intel, such as the Itanium C++ abi [1]) [1] https://itanium-cxx-abi.github.io/cxx-abi/abi-eh.html https://itanium-cxx-abi.github.io/cxx-abi/abi-eh.html
- aidenn0 5y agoArguably it was the nail in the coffin for alpha
- thequux 5y agoItanium may have been the nail in the coffin, but by the time the hammer fell on that nail, Alpha was already basically dead due to bad business structure and incentives that were inherited from DEC. They had many of the same problems that Intel has been having recently (low yields, failure to keep up with performance increases) without Intel's long-standing business agreements or inertia to hold up the product line through a difficult period.
- garaetjjte 5y ago>What sort of architectures (if any) got killed as a direct result of developing IA-64? Alpha?
- hulitu 5y agoAnd HP-PA and, later, MIPS (as a mainstream computer). MIPS survives in some routers.
- __d 5y agoMIPS is very, very close to dead now. To be fair though, I think its death is more attributable to ARM than Itanium. And RISC-V is killing off anything that remained.
- WorldMaker 5y agoMIPS the brand was bought for cheap from a bankruptcy, and resurrected by its new owner… to be an ARM partner building ARM chips.
- saati 5y agoAlpha, HP-PA.
- throwawaylinux 5y agoFor some periods (including during some of the Opteron era) Itanium 2 actually did okay. https://www.realworldtech.com/forum/?threadid=27345&curpostid=27345 https://www.realworldtech.com/forum/?threadid=27345&curposti... It had very strong floating point performance and on spec int it was holding pace with Opterons, Athlons and P4s clocked a lot higher. Apparently a lot of the int performance was due to large fast caches (I think it had a bigger die size compared with the others) -- have a look at the 1.5MB version vs the 3MB version. But even there it wasn't doing so bad against the Sun and IBM processors which were out of order I think. So yes you're right some things did run pretty fast. Unfortunately for Itanium, compiler techniques to make up for in-order execution had just about run out of steam at that point, while OOOE continued to scale up and improve steadily. Which is pretty much the opposite of what HP and Intel had predicted in the 90s, which is why they justified Itanium's approach.
- theandrewbailey 5y agoItanium was so insignificant that while I recall that it was being EOL'd, I hadn't marked my calendar for it. A year ago, Derbauer did a teardown and got some sweet die shots of one: https://www.youtube.com/watch?v=Lqz5ZtiCmYk https://www.youtube.com/watch?v=Lqz5ZtiCmYk Nit: this blog's text is a bit small and thin.
- kstrauser 5y agoHaving had to deal with it, I scheduled a reminder. I didn't want to let the day slip past! Ooh! The pretty pictures start around 11:03. (Blog is mine; I'll see about tweaking the text.)
- sbierwagen 5y agoFun fact, Intel did this exact thing once before, in 1981, with the iAPX 432: https://en.wikipedia.org/wiki/Intel_iAPX_432 https://en.wikipedia.org/wiki/Intel_iAPX_432 They had made the 8008 and 8080, but those were awkward and ungainly chips meant to power calculators, of all things. iAPX 432 was a clean sheet 32 bit design designed for high level languages and real computers, kind of like mini Lisp machines, complete with native machine support for garbage collection. But it was taking a while to get out the door, and performance wasn't so great, so they hacked together a quick upgrade to the 8080... the 8088, which was used in the original IBM PC. History takes over from there.
- krylon 5y agoAnd they did it again with the i960 and i860. I'm told they were quite nice processors in their day (never having been close to one myself, that was before my time), but for whatever reasons, they did not go mainstream.
- rwmj 5y agoThe i860 was lovely! I wrote some software for an i860-based hypercube back in the day, and it was the fastest thing on earth. The reason it never went mainstream is easy enough to explain: expensive chips and (for the hypercube) a very different programming model.
- justthisonce666 5y agoI've programmed both, though only shipped products that used the i960 (CA and KB). I believe the i960 tended to be used in things like printers but there weren't many design wins for the i860. I managed to miss the magic that is the 88k thankfully. Who actually used it? Linotype? Tek workstations maybe?
- justthisonce666 5y agoWhile I was musing about such matters, now, the TI C80 MVP, that was an interesting one to write software for.
- lmm 5y agoPeople let their (understandable) hatred of Intel-the-company colour their technical judgement. Itanium was one of the more interesting architectures of its time, it fairly flew on expert-tuned assembly; I still believe we'll see a return to its ideas once the computing world finally moves on from C. (Netburst is also unfairly maligned if you ask me; contrary to the article, enthusiasts have clocked those P4s up to 12GHz. As far as I know they're still, over a decade later, the fastest CPU for single-threaded sequential integer workloads that has ever been made; certainly the fastest x86-compatible processor for such. They're kind of the equal and opposite failure to the Itanium, ironically enough)
- xorcist 5y agoWhat types of languages do you see would enable more efficient VLIW compilers? From my limited perspective, I find C one of the easier languages to write optimizing compilers for, and would therefore expect optimizing compilers to be the most efficient there. 40 years of collective experience of optimizing for C-like languages also helps of course. Or is it the lack of explicit parallelism in the language that is limiting? Somehow I suspect the limited uptake of better suited languages to be a sign that they aren't very helpful most of the time, and most of the parallel operations people do is more like serving a lot of individually sequential transactions per second, which is something C and unix is pretty good at.
- throwaway81523 5y agoOne well known obstacle to optimizing C is the difficulty of alias analysis. It's easier to do that for languages that don't have C's unrestricted pointers.
- bitwize 5y agoNot even sad. What I am sad about is that it took Alpha and PA-RISC with it.
- dlsa 5y agoIs it too cynical to assert that this was the actual intent?
- Cullinet 5y agoIt was the intent of DEC and HP insofar as they joined the Itanium programme and EOL'd their own designs.
- psandor 5y agoDEC was part of HP at that point, so it was the HP leadership that made the decision to ditch Alpha.
- Paianni 5y agoCompaq bought DEC and killed Alpha before both got folded into HP.
- TheOtherHobbes 5y agoAlpha was the reason DEC was for sale. It was a very cool speedy architecture, but it took too long to emerge from the DEC management swamp. Bitsavers has a series of memos showing how the Alpha predecessor Prism went down in flames when DEC decided to quick-fix its technology hole with MIPS. Alpha was a kind of illicit skunk works leftover from that failed project. If DEC had pushed it out the door a couple of years earlier - not likely, but possible with a push - it might have eaten the rest of the industry.
- jabl 5y agoI suspect that whatever the virtues of the Alpha architecture [1], DEC simply didn't have the muscle to stay in the game with exponentially increasing R&D costs. [1] And it's not like Alpha was some shining beauty of ISA design either. Early versions lacking sub-word load/store, the absolutely crazy memory consistency model, ...
- okonomiyaki3000 5y agoThis guy has been waiting 20 years to use that headline but, if he wants me to make room for him on my door, he'll have to do better than that.
- kstrauser 5y agoI did my best! And as with Intel, it just wasn't enough.
- shrikant 5y ago> In 2003, AMD launched their 64-bit, but Pentium-compatible, Opteron CPU. Everyone stopped buying Intel CPUs for a while. [...] almost everyone immediately embraced AMD's instruction set and no one but HP wanted anything to do with Itanium. Huh, I never really connected the dots before, but TIL that this is why 64-bit images and package repositories of various Linux distributions were referred to as `amd64`...
- krylon 5y agoThis leads to an interesting situation, where Intel owns x86 and licenses it to AMD, while AMD owns the amd64 extension and licenses it to Intel. Should one company revoke their license, so would the other (I assume, naively), and boom - no more amd64/x86_64 CPUs for you and me. Intel could probably create a new extension to x86, but that would take some time. And IIRC, AMD's x86 license evaporates automatically, if the company is acquired by someone else, which means the only company that could buy it without disastrous consequences is Intel, who probably would run into some anti-trust issues if they did.
- Beldin 5y agoWhat is it that ensures licensing is required? Patents? Because patents on x86 technology predating amd64 should be expired by now... and without patent protection, another company would be allowed to reverse-engineer it, no?
- ramchip 5y agohttps://www.blopeur.com/2020/04/08/Intel-x86-patent-never-ending.html https://www.blopeur.com/2020/04/08/Intel-x86-patent-never-en... Tl;dr: many new patents have been created over the years, for instance SSE extensions, and those haven't expired.
- pjc50 5y agoYup. It was a classic mishandled transition; they messed up the emulation https://www.zdnet.com/article/intel-scraps-once-crucial-itanium-feature/ https://www.zdnet.com/article/intel-scraps-once-crucial-itan... , and getting the benefits of the transition required a big ecosystem shift. You more-or-less had to use Intel's compilers. Meanwhile AMD offered "x86, but faster and wider", which (once you booted a 64-bit operating system) could run either type of binary at native speed. Sometimes people really do just want a faster horse.
- captainmuon 5y agoIt's a bit ironic that one of the reasons for Itanium's failure was that the compilers were not ready. I have no doubt that nowadays GCC and clang would immediately have good support for any new processor (especially from a big player like Intel). In any case the processor vendor would make sure themselves that there would be good compiler support (see Apple). (Setting aside the question if good compiler support would have been possible with Itanium's architecture, or if the optimizations they thought of could not be implemented in principle. I don't know enough about it to tell for sure.)
- saurik 5y agogcc had already existed for 14 years by the time Itanium came out, and it had been widely ported to many different systems... that was kind of the whole point of the project. The real issue I feel is locked up in your parenthetical: it is difficult to put aside the question of whether good compilers for Itanium were even possible, as part of the entire problem was that the VLIW architecture concept was so incredibly different than CISC/RISC that it made porting the compiler very difficult (and while you could, can, and did somewhat easily do naive compilation that simply ignored the potential benefits, the resulting performance sucked). I was in college at the time and I remember VLIW being cited as a reason why compilers had a lot of hot research that needed to be done ASAP.
- jabl 5y agoAFAIK Intel and HP spent well north of $1B on VLIW compiler research, with crickets to show for it all. The people prophesying the second coming of VLIW (for general purpose code) seriously need to explain the compiler breakthroughs that have been done to make the whole affair worthwhile.
- therealcamino 5y agoYes -- and explain how code statically scheduled for the worst-case dependences at compile time can ever beat out-of-order and speculative execution that can see the actual dependences at runtime. For anything other than extremely regular codes, there's an information gap that can't be overcome.
- macdice 5y agoIs this also the end of HPUX? Can it run on anything else? It's hard to find information on that.
- dsr_ 5y agoIt certainly used to run on other architectures -- notably PA-RISC and Motorola 680x0.
- spijdar 5y agoThey definitely "can" port it, but would they? I believe HP is internally using Linux for more and more things -- the question is if there are enough customers paying for HP-UX to make porting worth it, or if they are legally able to sell the rights to it as they did OpenVMS. Only HP knows the full answer.
- pferde 5y agoThere's still a lot of legacy HPUX servers out there, mostly running SAP+Oracle combo, but they all slowly get phased out in favour of Linux or Windows boxes. Still, some of them will likely remain chugging along for years to come, because their performance will simply be sufficient for the task at hand.
- jabl 5y agoI can well imagining HP milking existing HP-UX customers for all they're worth, but I'm finding it hard to justify spending much $$$ to develop it. So I would expect HPE to provide security patches and nothing more.
- GekkePrutser 5y agoYeah but those versions have long been unmaintained. All modern HPUX code and third party apps are itanium only. The last 10 years or so HP actually paid intel a lot to keep making and developing itanium because they're so dependent on it for hpux and their long term support contracts. If a port was realistic they would have done it
- pjmlp 5y ago> In 2003, AMD launched their 64-bit, but Pentium-compatible, Opteron CPU. Everyone stopped buying Intel CPUs for a while. Within a few years Intel made their own 64-bit, but AMD-compatible, CPUs to avoid entirely losing the desktop and small server market. They were right earlier: almost everyone immediately embraced AMD's instruction set and no one but HP wanted anything to do with Itanium. This is the only reason why Itanium failed. Had AMD not been allowed to produce Intel-compatible CPUs, everyone would eventually be forced to eat Itanium regardless how they tasted. One doesn't get to be picky when food supply dries out.
- Nursie 5y agoHistory may have unrolled quite differently at that point, if the only choice was to shift architecture, then we may have seen a more diverse server CPU estate being maintained. At that point Sun were still relevant, POWER systems were still being bought and deployed in larger proportions etc.
- pjmlp 5y agoNone of them would adopt Windows laptops running on POWER, just as one possible scenario.
- Nursie 5y agoTrue, but Apple were running Macbooks on power back then I think. I know windows was even more dominant then than it is now so perhaps large numbers of powerbooks was never on the cards. But in the server space the story might have been different. I take it intel were planning "Mobile Itanium" at some point?
- pjmlp 5y agoOn those days Apple market share was still of a company struggling to get out of insolvency, and they never had any significant market share outside North America during the last century. Yes, on the server it would have been differently, however Linux distributions might have still killed the other UNIX vendors with their CPUs alongside, as it happened.
- pabs3 5y agoI note that Debian still has an unofficial ia64 port: https://www.debian.org/ports/ia64/ https://www.debian.org/ports/ia64/ https://wiki.debian.org/Ports/ia64 https://wiki.debian.org/Ports/ia64
- tobiasu 5y agoGentoo also has instructions. Linux/ia64 works fine for the most part, it's not an architecture that causes much drama for userspace applications. Servers are cheap on ebay and the older Intel boards (also sold by Dell, Fujitsu,..) can be upgraded to newer CPUs that are either less power hungry or faster with more cores and sort-of HT. HP are generally not upgrade-able and SGI/ia64 is a special case with lots of other custom hardware as usual. Annoyingly many Linux / gcc developers want to remove ia64 support from their source trees because the architecture is no longer commercially relevant. As a necrocomputing enthusiast it's quite sad, but not much one can do about. If only this old junk was as popular as the various homecomputers...
- fredoralive 5y agoNote at a kernel level it's now marked as orphaned. It also seems to just get random regressions, because nobody actually tests it. https://www.phoronix.com/scan.php?page=news_item&px=Linux-Orphans-Itanium-IA64 https://www.phoronix.com/scan.php?page=news_item&px=Linux-Or...
- cbmuser 5y agoThat's because not everyone is always running bleeding-edge kernels. We have found and fixed multiple regressions in the kernel on ia64. As of Linux 5.12, the kernel runs fine on most ia64, there is still one known regression that affects some machines. Disclaimer: I'm Debian's maintainer for ia64 (and most other older architectures such as m68k).
- macintux 5y agoMinor historical footnote: HP paid Progeny (Ian Murdock's company he founded years after creating Debian) to help port Debian packages to Itanium. They gave us a first-generation computer, which was epically slow of course. That contract helped keep Progeny alive after the venture capital funding dried up; the company's original plan was to allow customers to reboot their Windows desktop computers overnight to run as a distributed Linux supercomputer.
- Cullinet 5y agoa vessel deliberately sunk is scuttled.
- andrem 5y agoLittle anecdote: The Itanium led to one of a more remarkable episodes in my career. Around 2007 we were running a heavy workload on MS SQL Server in a fast growing business. We faced a lot of outages due to DB overload. Instead of trying to investigate and understand the issue better and optimize the software, some external consultants were brought in and recommended to upgrade the hardware to an Itanium based monster. It was a massive piece of hardware with a price tag close to 7 figures. The thing went live and performance decreased and issues increased. After a couple of weeks of trying to run on the Itanium we switched back to the old setup and then focused on software improvements. Long story short - after about 8 weeks of dedicated troubleshooting and improvements the whole app became stable, was capable to double workload on the same hardware without outages for the next 12 months. The Itanium took up a lot of space in the server room before it was dismantled and used as a paperweight. A lawsuit involving multiple parties (supplier,consultant,business) eventually got settled out of court in 2015 (?) long after I left there. Farewell Itanium :)
- api 5y ago> some external consultants were brought in Is there a single example of that working anywhere ever? I have never seen one.
- mprovost 5y agoThere was that time a bunch of Silicon Valley engineers went and fixed the healthcare.gov (Obamacare) site for the US govt after the original contractors did a terrible job. But then the first team were already contractors, so maybe the lesson there is, if your first external consultants don't work, just keep bringing in more?
- dekhn 5y agothe engineers who "fixed" the site all worked themselves to near-death "fixing" the site. Not sure that's a real win.
- 5y ago
- jwildeboer 5y agoKind of curious why the article didn't mention HPs PARISC architecture. IIRC, HP switched away from PARISC to Itanium at the time. I guess because they saw that managing your own architecture comes at a huge cost? I very well remember how Itanium was heavily promoted by HP to existing PARISC customers as the natural upgrade path and how they played down x86 as unreliable PC derived stuff that no-one should put in a datacenter ;)
- spijdar 5y ago> Goodbye, Itanic. You were a strange, unloved little detour, better known for the good designs you killed than for any successes of your own. Few will miss you. It does, albeit indirectly, and not by name. Poor Alpha and PA-RISC...
- criticas 5y agoHP concluded PA-RISC (and all RISC, really) had reached a plateau. Wikipedia explains it well: In 1989, HP determined that the Reduced Instruction Set Computing (RISC) architectures were approaching the processing limit at one instruction per cycle. HP researchers investigated a new architecture, later named Explicitly Parallel Instruction Computing (EPIC), that allows the processor to execute multiple instructions in each clock cycle. EPIC implements a form of very long instruction word (VLIW) architecture, in which a single instruction word contains multiple instructions. With EPIC, the compiler determines in advance which instructions can be executed at the same time, so the microprocessor simply executes the instructions and does not need elaborate mechanisms to determine which instructions to execute in parallel.[5] The goal of this approach is twofold: to enable deeper inspection of the code at compile time to identify additional opportunities for parallel execution, and to simplify the processor design and reduce energy consumption by eliminating the need for runtime scheduling circuitry. HP believed that it was no longer cost-effective for individual enterprise systems companies such as itself to develop proprietary microprocessors, so it partnered with Intel in 1994 to develop the IA-64 architecture, derived from EPIC. Intel was willing to undertake the very large development effort on IA-64 in the expectation that the resulting microprocessor would be used by the majority of enterprise systems manufacturers. HP and Intel initiated a large joint development effort with a goal of delivering the first product, Merced, in 1998.[5] (https://en.wikipedia.org/wiki/Itanium https://en.wikipedia.org/wiki/Itanium)
- nickdothutton 5y agoTo see how expectations were gradually reset, see this chart which also appears on the Wikipedia page for itanium. https://helgeklein.com/wp-content/uploads/2010/05/itanium-sales-forecasts1.png https://helgeklein.com/wp-content/uploads/2010/05/itanium-sa...
- DrBazza 5y ago> In 1994, Intel and HP looked around and saw a wide variety of successful server CPU architectures like Alpha, MIPS, SPARC, and POWER. This annoyed them and they decided to make a new CPU that no one would want to use. I spent some time "optimizing" code to run on Itanium for "MegaBank". Who then dumped it. Then we swapped to AMD Opteron for while before Intel caught back up. I suppose it was successful in that it created work.
- throwawaylinux 5y agoI'm pretty surprised to hear "MegaBank" ran AMD. Not that Opteron wasn't awesome and better than what Intel had at most things, at least until Woodcrest if not Nehalem. But because MegaBanks are usually pretty conservative. More than a few still run mainframes and proprietary unixes. Unless you worked in their HFT group, that is.
- DrBazza 5y agoWe wrote quant code that had to run on all architectures... for the HFT team [1], unfortunately, including a long drawn out debacle supporting Solaris 5.7 for an absurdly long time. Other members of my team were looking at IBM architectures as well, mostly because IBM were throwing money at us to use their kit. [1] high frequency, not necessarily low latency, for some defintion of the word 'high'.
- lmilcin 5y agoIntel lost a lot by playing games rather than letting engineers build the best stuff they could and cash out checks on it. Now they cry help to the same engineers they have turned away from in the past.
- phkahler 5y ago>> Intel lost a lot by playing games rather than letting engineers build the best stuff they could and cash out checks on it. Which is strange since IIRC Intel engineers designed the PCI bus to replace ISA in spite of management saying that's for the PC makes to do. I would have thought they'd learn from that success, but apparently not.
- lmilcin 5y agoI have worked for Intel sometime later, when they stopped being so elitist and actually started overdoing it in the other direction -- building everything else and the kitchen sink rather than focusing on their core competency.
- throwaway9870 5y agoI would like the suggest the Itanium was a huge business success. At the start of the 90s, there were many decent workstation CPUs: SPARC, MIPS, PowerPC, Alpha, and PA-RISC. Intel CPUs were not considered in the same class. Big engineering work was done on workstations powered by these chips. But as the decade went on, the chips became vastly more complex and expensive to design. Near the middle of the decade, it was becoming clear what the trajectory was and companies started looking around trying to figure out how to navigate this. On top of this problem, Intel/HP teamed up to design a processor that was quite beyond (in terms of complexity) anything being designed at the time and it became clear competing was just not economically feasible. So basically the industry folded. In one move, Intel took out entire industry of companies that could compete. PowerPC is still there, but is marginal. SPARC, PA-RISC, MIPS, and Alpha design teams are gone. Interesting technical tidbit - I remember an Intel engineer giving a talk at Stanford about the architecture and Hennessy came to listen. At the end of the talk he asked why they thought moving so much complexity to the compiler would work when other (including John) found it to be problematic? They didn't have an answer and I could see the look on John's face and at that point realized they might not understand what they are getting into.
- jabl 5y agoTrue, but the other side of the coin is that the massive economics of scale in chip manufacturing as well as around ISA ecosystems (software) meant that some massive consolidation of the industry was all but inevitable. Had Intel not embarked on the Itanium project, we might still have ended up with something close to the world we have now, with x86-64 and ARM being the top dogs, and some "traditional RISC workstation" architecture surviving in a small high-end niche (POWER).
- throwaway9870 5y agoNo question there are a lot of ways to win, probably many better than what transpired. But in the end, Itanium played a big role in Intel consolidating the CPU market and taking complete control for a significant period of time.
- nabla9 5y ago
- wil421 5y agoDon’t forget HP and Oracle have been in a lawsuit for a decade about Oracle dropping support for Itanium. Oracle is on the hook for 3 billion. https://www.reuters.com/legal/transactional/oracle-loses-bid-upend-hps-3-billion-win-2021-06-14/ https://www.reuters.com/legal/transactional/oracle-loses-bid...
- cafard 5y agoCould one say that the Itanium helped to do in the Alpha and PA-RISC architectures?
- jabl 5y agoYes, but the massive economies of scale in chip manufacturing and software compatibility would most likely have doomed Alpha and PA-RISC in any case.
- mrweasel 5y agoI don’t know if it’s true, but a story I was told by an HP engineer claims that Itanium was more or less designed by HP. Which would mean that HP wanted to kill off the PA-RISC platform.
- _ph_ 5y agoThe grand plan of VLIW might not have worked out anyway, but I always wondered what would have happened, if Intel had moved the Itanic to current process nodes, even without huge modifications. By the transistor count, it could probably be power-efficient enough to drive mobile phones. Also, on the time of its peak, the Itanium did perform quite well, I wonder what it could deliver, if it would be grown to use all of modern production processes. Maybe VLIW cannot be made to work, but I do think that Intel missed the boat by not providing cheap development systems to enthusiasts. Like a PC-compatible motherboard with an Itanium for like 500$. The Linux crowd would have picked it up gladly. Instead, it was only available as espensive hardware, which reduced the potential developer audience (both from the availability of the development resource itself as in the target market). The post mentions, that everyone picks up the new Apple Silicon processors, because they are nice. They certainly are, but the big point is, that a compatible ARM system can be picked up for as little as $35, the Raspberry Pi and its friends. And while Apple hardware isn't low-cost, it is increadibly cheap in comparison to the Itanium systems of that time.
- cesarb 5y agoEverybody here seems to be focusing on the negatives, but there's also a few positive legacies from the Itanium architecture, all of them on the software side: EFI which became UEFI (like it or not, it's still better than the legacy BIOS), the GPT partition table format, and the C++ ABI now used for all architectures on Linux.
- fanf2 5y agoSadly EFI killed OpenFirmware which could have given us open source boot code and portable drivers.
- allenrb 5y agoI’ve seen it mentioned over the years that writing the necessary compilers was more than merely difficult. As I understood it, the dynamic nature of load latencies (hit L1 cache? L2? L3? Slow trip to DRAM?) means that some workloads just can’t be statically scheduled in an effective manner. Anything to that?
- Symmetry 5y agoEssentially yes. In cases where memory latency is predictable like DSP workloads then VLIW processors actually tend to work really well. Itanium had some facilities to allow speculative loads but they had a lot of overhead in practice.
- dragontamer 5y agoGiven that we have magic compilers that convert mostly sequential CUDA into highly parallel SIMD assembly code, I don't think that the Itanium concept was too far off. But all of the details had gross amounts of complexity. More modern VLIW architectures are more obvious about their parallelism... Without any of the weird 'bundles' that made the Itanium terribly complex. I still think that 'simple decoder' has hope, and I point to NVidia Volta and Turing as my case in point. At the assembly level, the NVidia SASS compilers generate the read write dependencies. NVidia has proven that the compiler can indeed specify the dependencies at compile time, though they require a huge amount of software bulk to be able to do so (PTX pseudo assembly that compiles into SASS later) The issue is that the Itanium was poorly designed and impractical. But the overall concepts seem to still be possible (indeed, more possible given today's technology). I'd be interested in a modern Itanium, but instead split as follows: where the compiler determines the dependencies but the core figures out the precise scheduling.
- mastrsushi 5y agoThe Itanic sunk like 15 years ago, they just finally stopped making chick flicks about it.
- SavantIdiot 5y ago> This annoyed them and they decided to make a new CPU that no one would want to use. I thought this was sarcasm, but the tone continues throughout the article. Are people this really painfully misinformed? The ISA was brilliant. The execution, not so much. It was a far more scalable architecture, completely "clean" from x86 baggage (I'm talking about the ISA, not the thermal issues Madison and McKinley had with the floating point units). It even ran Windows and had two compilers (one from HP and one from Intel), and it decoded x86! Then again, people were also hot on Transmeta at the time, so perhaps the author is confusing things. > better known for the good designs you killed Like? Intel sat on Yamhill (64b "star-T" for x86) for a year, and when I was brought on, the project had issues in both instruction fetch and execution-unit area. It was not a good design, and was not ready because it was cobbled together at the last minute. Quite literally. AMD beat Intel to both 64-bit and 1 GHz, and we all (architects) knew it. Looking at it one way, Itanium was a product that was ahead of its time. In 1995~97 Google didn't even exist yet, Amazon was just getting started. Server farms with their own power plants were something reserved for investment banks as redundant backup, US eCommerce was well under $1Billion/yr . I'm 100% certain that if Intel had brought the yields up on Itanium and taken an early loss to build market share, it would have been the dominant architecture in integer cloud today. But in reality they had to beat AMD, because AMD was going after their cash cow (commodity x86) with a vengeance, and winning. Couldn't fight two wars at once, and thus, Itanium withered. So looking at it another way, one could argue Itanium was too late because the internet scaled out fast in late 1990, and Itanium was caught with its pants down, so x86 filled in the gap. Either way, Arm is more likely to take away server market from x86 than IA64, going forward, but that's a not a sure thing. I could (30% chance) see VLIW making a comeback if capacity weren't such a problem, it is far more suited to e-commerce cloud instruction mixes, and with hypervisors and docker-like virtualization so much faster than VM, it could happen.
- chasil 5y agoI know that I don't have sufficient engineering background to debate you, but still I see ARM's Johnny-come-lately 64-bit implementation that has gone farther up and down than would ever have been possible for Itanium (Fujitsu with the top supercomputer, and any 64-bit phone illustrate the point). So I am drawn to Linus Torvald's commentary on IA64: "IA64 made all the mistakes anybody else did, and threw out all the good parts of the x86 because people thought those parts were ugly. They aren't ugly, they're the "charming oddity" that makes it do well. Look at them the right way and you realize that a lot of the grottyness is exactly _why_ the x86 works so well (yeah, and the fact that they are everywhere ;)." https://yarchive.net/comp/linux/x86.html https://yarchive.net/comp/linux/x86.html
- acomjean 5y ago> Intel and HP looked around and saw a wide variety of successful server CPU architectures like Alpha, MIPS, SPARC, and POWER. I used a PA-RIRC/Alpha and Power machines in various work roles. All those architectures/OS fell to X86 speed improvements/low prices. All those other architectures couldn't compete as intel X86 got faster and faster and caught up with exotic silicon. When MS released windows NT for x86 it was over. My Mom's former employer (PTC) released for windows NT a little late and lost ground to SolidWorks. Even Apple gave up using power an switched to x86.
- chasil 5y agoWe plan to get rid of this real soon now. # uname -a HP-UX antique B.10.20 A 9000/800 862741461 two-user license # model 9000/800/K380
- deleted 5y ago[deleted]
- cbmuser 5y agoPlease offer this machine to the debian-hppa port, post a message here: > https://lists.debian.org/debian-hppa/ https://lists.debian.org/debian-hppa/ It might be worth to be hosted at the Open-Source Lab at Oregon State University where we just lost one Debian machine IIRC.
- chasil 5y agoUnfortunately, this is being used for a corporate tracking application. I have several of them, bit they run on 220v power and are the size of a small refrigerator. The CPUs range up to 220MHz.
- olympusultra 5y agoAre they in Europe?
- ianhanschen 5y agoCan you call it Itanic if it was around for more than a decade because of how well it sold and how many supercomputers chose to use it? I am familiar with the pain of Itanium, and I understand how hard it was to work with. I've kernel debugged an operating system on it. Yet it was still successful enough to be around for this long. I wouldn't call it "Itanic."
- kstrauser 5y ago> Can you call it Itanic if it was around for more than a decade because of how well it sold It didn't sell well, though. At all. > and how many supercomputers chose to use it? Here's a chart of supercomputer architecture by year: https://commons.wikimedia.org/wiki/File:Processor_families_in_TOP500_supercomputers.svg https://commons.wikimedia.org/wiki/File:Processor_families_i... Itanium showed up around 2001, peaked in 2003 at about 100 systems, and was nearly gone by 2007. However good it might have been hypothetically -- and I contend that it wasn't -- it was a market disaster.
- Lammy 5y agoItanium_Sales_Forecasts.png is my favorite image on all of Wikipedia https://commons.wikimedia.org/wiki/File:Itanium_Sales_Forecasts.png https://commons.wikimedia.org/wiki/File:Itanium_Sales_Foreca...
- not2b 5y agoOne very good thing came out of the Itanium project: the vendor-independent ABI for C++. IBM, HP, Sun, Intel, and GCC all signed on to rigorously specify the layout of C++ objects and the function call interface on the Itanium platform (GCC got funding to help with this) and the processor-independent parts of the standard were then used pretty much everywhere else (with adaptations for different instruction sets to handle the call interface).
- scardycat 5y agoItanium was one of the best processors I worked on and I worked on at least 20 different ones. It was way ahead of its time and the software was not ready and of course it cost your arm and leg and the next three generations, so it was really only ever taken up by large enterprises. I wish Intel and HP were more sensible in how they brought it to market.
- FullyFunctional 5y agoI didn't see anyone mention this, but this is completely wrong: "This annoyed them and they decided to make a new CPU that no one would want to use." Facts: 1. Itanium grew out of internal HP efforts to define their next generation architecture, presumably in response to their difficulty scaling the Precision Architecture. 2. Intel only got involved part way through. 3. Nobody ever "decides to make a CPU that no one will use". Itanium for all its issues, was used in great number, but nowhere near what it was supposed to. The failure of Itanium was a bet of handling cache misses with the compiler (like Transmeta, my alma mater) and having a design by committee (lots of nice ideas in isolation, a disaster in aggregate). There are so many technical problems with the ISA, too many features, too much performance draining complexity. Something as critical as registers is burried behind (IIRC) three levels of indirection (rotating windows, modulo scheduled registers, etc). The big bet on predication didn't help code density nor cycle time. It's really a shame that Intel throughout history has botched ISA design after ISA design. That it can be done right is exemplified by Alpha, RISC-V, and ARM64. If the rumored acquisition of SiFive happens, then maybe they can finally get it. EDIT: Typos
- Firehawke 5y agoThis post, funny enough, absolutely gets my thoughts down entirely. If I didn't know better I'd have accused myself of ghostwriting that post. That's amusing and horrifying.. but it's all accurate to what I think!
- kstrauser 5y agoThey say great minds think alike, but if you're thinking like me instead... I'm so, so sorry.