Slashdot Mirror


Why Doesn't the Itanium Get the Respect It's Due?

happycorp wonders: "As in recent years the Itanium does well, easily beating x86 processors even at its low clockspeed (1.4Ghz). The supercomputer people are serious about benchmarking (no easily tricked microbenchmarks or reliance on closed-source commercial apps), so the discrepancy between the performance and perception of this chip is serious. With a single-CPU Itanium2 system at around $2000 their price is already reasonable, and the price would come down (and software would be ported) if the Itanium ever became a mass market chip. Having an affordable chip one step above a Xeon or Opteron in floating-point performance would not be such a bad thing for gaming enthusiasts (or 3D artists). So, the recent article on the Top 500 supercomputers list brings up a question I've been meaning to ask: Why do we see so many disparaging opinions of the Itanium processor (all those 'Itanic' jokes, etc.)?" "It seems computing enthusiasts' sentiment is set against this processor, and its likely that it's going to be abandoned sooner or later. We'll be paying for x86 compatibility indefinitely (recall the Xeon has roughly three times the number of transistors of the ppc970 for example; but we hardly get three times the performance).

These are a couple scores from the top 20, with the total gigaflops divided by the number of processors to obtain a per-processor speed:


rank processor ghz (gflops / #procs) speed #5 ppc970 2.2 (27910 / 4800) 5.81 #7 itanium2 1.4 (19940 / 4096) 4.86 #10 opteron 2.0 (15250 / 5000) 3.05 #20 xeon 3.06 (9819 / 2500) 3.92
Given this, consider what a 2 or 3 Ghz Itanium could do.

(fine print: I am not affiliated with the Itanium or the top500 list in any way)."

668 comments

  1. Don't get no respect! by XanC · · Score: 5, Funny

    They should have called it the "Dangerfield".

    1. Re:Don't get no respect! by Profane+MuthaFucka · · Score: 5, Funny

      I love Dangerfield. I can imagine the jokes now.

      -I told this good looking Pentium IV that I have instructions that are very wide. She said true, but the pipeline isn't long. I get no respect!

      -The other day I was doing trillions of floating point operations a second. My wife said "Honey, could you mispredict a branch or something? I'm getting sore." I get no respect!

      -My wife finally told me that she's leaving because she's tired of my architecture. I said "Baby, I can change." Then I found out that she's seeing a Transmeta processor. I get no respect!

      --
      Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
    2. Re:Don't get no respect! by Anonymous Coward · · Score: 0

      Heh, I'd have bought one

    3. Re:Don't get no respect! by Anonymous Coward · · Score: 0

      "They should have called it the 'Dangerfield'."

      There's no way that would ever get past marketing. Nobody's grandmother would buy a computer with a 'Danger Field' in it.

    4. Re:Don't get no respect! by Anonymous Coward · · Score: 0

      So true. It's very important to Intel that people's grandmothers are interested in the Itanium.

    5. Re:Don't get no respect! by matt-larose · · Score: 1

      Bwhahaha the first one is gold !

      --
      "Be glad you sailed for a better day, But dont forget there will be hell to pay" - Dave King/Flogging Molly
    6. Re:Don't get no respect! by demachina · · Score: 4, Insightful

      But seriously, it gets no respect because its a complete dog on anything other than vectorizable Fortran codes. Its inherent in the design.

      The compiler has to do a LOT of work to pack instructions in to the VLIW(Very long instruction word). To get max performance I think you need to schedule 4? instructions in each word. You can do that with carefully written vectorizable Fortran with the help of a talented supercomputing class code tuner.

      When you get to C and C++ it is nearly impossible. Pointers and pointer aliasing completely frustrate the compiler, and in general most C and C++ code don't have the vectorized nature of the class vectorized Fortran codes.

      The IA32 emulation is inherently much slower than a Pentium or Athlon at the same clock and they have much higher clocks than the Itanic. So any application you carry a binary over from an IA32 box is a real dog. It takes advantage of none of the chips strengths and hits all its weaknesses.

      IA64 has a place on some supercomputing applications that exloit its strenghts. On others I wager x386_64 is both cheaper(higher sales volume and easier to manufacture), faster and easier to develop code for. On any C or C++ code IA32 and x86_64 will win hands down.

      With Itanium Intel was betting bumping up the clock on chips would run out of gas sooner than it did. They thought you would have to go to VLIW to keep increasing performance. Unfortunately clocks kept going up enough that the high end AMD and Penitum left it in the dust. AMD also developed x86_64 which gave people 64 bit address space which is needed for some apps, but PC prices and high clocks.

      IA64 is doomed in any place other than niche supercomputing apps and its struggling there against Power, x86_64 etc.

      --
      @de_machina
    7. Re:Don't get no respect! by vpupkind · · Score: 1

      You're ABSOLUTELY wrong about the VLIW architecture -- you need optimizing compilers (which do exist), and you have to learn slightly new optimization tricks (e.g. use the intrinsics).

    8. Re:Don't get no respect! by demachina · · Score: 3, Interesting

      They exist, they fail miserably optimizing most C and C++ code or at least they aren't good enough at it to make up for Itanic's handicapped clock speed.

      You just need to read the other posts here about how hard it is to develop compilers that can find 4 way parallel instructions to cram in to the VLIW at compile time. You find a lot more opportunities at runtime using dynamic scheduling at the price of complexity in the CPU.

      Maybe someday the compilers will be really good and Pentirum/AMD CPU clocks will hit the wall and Itanic will reign supreme. Intel is one of the few companies with pockets deep enough to keep it alive and keep pouring the billions in to both the CPU and the compiler, until it starts outshining x86_64 on anything other than vectorizable Fortran. Wouldn't necessarily count on that confluence of events happening in time to save it. I'd really like to see how much Intel has sunk in to Itanic versus the ROI. It must be appalling. Only a company with a near monopoly elsewhere could survive it.

      Me I'll take an AMD 3400+. My whole computer cost $800 versus $2000 for just an Itanic CPU, it has 2 GB/sec memory bandwidth, runs IA32 apps really fast, is running Gentoo Linux so everything is taking advantage of all the new registers and instructions set improvements, and I have 64 bit addressing. Its sweet and sensible.

      I'm not argueing that Itanic wont hold its niche in supercomputing. Aren't many people who are going to put one on a desktop or in a server.

      --
      @de_machina
    9. Re:Don't get no respect! by vpupkind · · Score: 1

      I've spent some time writing C code on VLIW architectures, and I've seen pretty decent optimizing compilers there [I haven't used Itanium, I used a couple of less-known arechitectures, e.g. TI 64xx]. You can extract a decent amount of parallelizm out of a regular code (if you think about it, since Pentium II you had a dual issue processor, you've just moved this piece of logic into the compiler). I do agree with you on the pricing issue -- as long as it costs more than any x86 processor, it will be irrelevant. However, AMD is a significantly better option, at leas for the nearest future.

    10. Re:Don't get no respect! by demachina · · Score: 1

      Is this C code you wrote written to do specific and simplish things on the TI, nice clean loops, with not much functions or logic or use of pointers. Were you being careful to write code that the compiler could fathom and do well on it, or is it some arbitrarily complex C code like a web browser or an email program using pointers, unions, templates, GUI layers, tons of function calls and massive numbers of if statements, etc. My experience optimizing compiler might do OK on the first kind, not so good on the second kind and most code on the desktop is the second kind.

      At runtime the CPU can deduce two pointers aren't pointing to the same data and its safe to put them in parallel. That is a lot harder to do at compile time unless there is a coder there to say, don't worry none of these pointers are working on the same data so you can do them in parallel. The compiler has to opt for the safe and slow approach by default.

      Fortran's absence of pointers make it a lot easier for optimizing compilers to work on.

      Most of the optimizing compilers I've used, none recently, did OK on clean vectorizable loops with no function calls or login in the middle, array indexing and no pointers. You throw typical ugly C and C++ code at them and they throw up their hands, give up and turn in to dogs.

      --
      @de_machina
    11. Re:Don't get no respect! by Tablizer · · Score: 1

      But seriously, it gets no respect because its a complete dog on anything other than vectorizable Fortran codes. Its inherent in the design.

      I for one welcome our retirement-postponed Fortran overlords.

    12. Re:Don't get no respect! by buddahboy · · Score: 1

      I for one welcome our retirement-postponed Fortran overlords.

      You're very welcome.
      I trust you left my room as I like it

    13. Re:Don't get no respect! by Anonymous Coward · · Score: 0
      - The other day my wife said to me "Baby you're too hot!" I smiled and said too her "Baby you never say such nice things about me!" and she said to me "No baby, I mean please stop, you're burning me!" I tell ya, I get no respect!

      - My agent got me this really big deal and told the customer in addition to getting top ranking on the top 500 list, we'll also list you as Dangerfield's largest customer! You know what the customer said? Can we pay extra to keep our name private, after all, we're just doing this to get that better price on Pentium 4's that you promised us!

      - I tell ya I get no respect! When I was younger my parents used to try and get people to play with me by offering them part of my parent's tax loss from my development!

      - The other night I was out with my girlfriend and in a fit of passion I told her "Baby, when they designed me I had the best specs!" I tell ya, I get no respect, you know what she said to me? "Yeah baby it was really sad that your designers were on some seemingly drug induced power trip when they designed you, you got anything else to talk about, your hour is almost up."

      - That marketing agent my parents hired for me is such a bum. I had to go out and try to sell my own act. But I can never get any respect, you know what one customer said to me? Dangerfield, we'd love to hire your act but the ConEd people told us that if we hired you we'd have to pay them extra for the Kyoto pollution credits to power your act.

      - Is it any wonder I get no respect? When I was growing up I'd go into my Mother's kitchen to see what delicious chip set's she was baking and I would ask her "Mom, is that really yummy smelling chip set baking in the oven for me?" and she would say "No dear, that really delicious feature rich chip set that works well with off the shelf high volume memory modules is for your younger brother Pentium D. You know, the brother I was forced into giving birth to because you were such a large disappointment to me."

      - Things got so desperate I had to save money by making my own show boards using magic markers. I took my new show boards to my agent and he told me: Dangerfield, I don't know how to break this to you gently, so I'm just going to say it: Microsoft dumped you. I asked my agent why? Why? And he said: Bill called me up personally and told me that there was no way he was divorcing his wife to marry you. That even if he dumped her to marry you he didn't think they be able to sell more copies than they'd sold of Bob. I just don't get any respect!

      - My parents told me I needed more developers if I was going to be a big star. So I hopped in my car and cruised the local corner where all the unemployed dot com developers hang out with signs that read "Will Code For Food". I told them "Hey buddy, I'll get you all the pizza you want if you'll write code for my instruction set" but all the developers told me that they had too much respect for themselves, they'd rather starve. I tell ya, I get no respect!

      - I decided that what my act really needed was a new enterprise server design so I went to see my Aunt Carly whom was my largest supporter in the family. But when I got there the guard at the front door said "Hey bub, she don't work here no more." I was shocked! I asked him what had happened. "Well the board was pretty pissed with her because she'd told them that merging with the company from Texas would give them the distribution muscle to really exploit the sweetheart pricing she could get on Dangerfield processors, and of course that never worked out. But the final straw came when she suggested to them that they could use all the Dangerfield processors that they couldn't sell in servers as fuser units in a new Laserjet design she'd had created."

    14. Re:Don't get no respect! by Anonymous Coward · · Score: 0

      Same reason the the G3 and G4 PowerPCs and the Alphas didn't - people care more about performanace per unit cost than anything else. The worst thing about Itanium is that it deliberately killed Alpha rather than extending that superb architecture.

  2. Did I miss something? by Rei · · Score: 0, Offtopic

    Who is going to buy a 2,000$+ graphics card to play games?

    --
    "It felt almost as good as stealing cars from grandma." -- Margaret Thatcher, probably.
    1. Re:Did I miss something? by Anonymous Coward · · Score: 0

      Fuck are you talking about? He mentioned a single Itanium CPU System for $2000, and remarked that the floating point performance of the processor might be good for gamers, he didn't say anything about graphics cards. I'd like you to meet my friend: Reading Comprehension.

    2. Re:Did I miss something? by mbrewthx · · Score: 1

      RTFA

      It's a processor!!!!!
      But it does raise the questions of what are the Doom 3 benchmarks on this chip?

      --
      __________ Leave me alone I'm compiling a RPG II program on my S/36...Thanks to metamucil I'm a Regular Meta Moderator
    3. Re:Did I miss something? by MynockGuano · · Score: 4, Informative
      He mentioned a single Itanium CPU System for $2000, and remarked that the floating point performance of the processor might be good for gamers.

      From TFA...
      The 1.4GHz Itanium 2 comes out Monday for $1,172 in 1,000-unit quantities. A 1.6GHz version comes out in May for $2,408 in similar quantities.
      That $2000 buys the processor, alone, and I don't believe I know any gamers that buy processors in lots of 1000.

      The entire issue of price and performance is moot, however. The severe restriction to acceptance of the chip for the market is the ia64 architecture (with practically non-existant emulation performance). It is very difficult to find commercial software (even HPC software) available for the system, so you're limited to in-house programs and open-source programs (most of which need to be tweaked and rewritten). The platform isn't deployed in sufficient quantities to create enough demand for commercial vendors to bother supporting it yet, so you end up with the chicken-and-egg problem that most Linux gamers are all too familiar with.
    4. Re:Did I miss something? by Anonymous Coward · · Score: 0

      Imagine the mark-up if you find a seller willing to give you a single chip. Both of those require 1000 units before that price per chip happens.

      I'd imagine it be from $1800 to $3000 range.

    5. Re:Did I miss something? by PHPhD2B · · Score: 1

      Did *I* miss something? The 1.4GHz Itanium 2 comes out Monday for $1,172 in 1,000-unit quantities. [...] That $2000 buys the processor, alone, and I don't believe I know any gamers that buy processors in lots of 1000. Are you saying that $1172 proc. in thousand quantity will cost $2000 when bought singly?

      --
      --I am Sun Tzu of the Borg. Resistance is feudal.
    6. Re:Did I miss something? by Rei · · Score: 1

      It's a processor!!!!!

      Yes, but the promotion of it was to use as a replacement for a nice graphics card for your typical "sleek gaming machine". And Itaniums cost 1.5-2.5k$. So, after factoring in the other hardware you have to get to make things work with it, you're effectively buying a 2000$+ graphics card.

      --
      "It felt almost as good as stealing cars from grandma." -- Margaret Thatcher, probably.
    7. Re:Did I miss something? by MynockGuano · · Score: 1

      Probably more. That $1172 in lots of 1000 means you have to spend over one million dollars before you get that price. Single-unit mark-up would likely make them at least $2000 apiece.

    8. Re:Did I miss something? by MynockGuano · · Score: 1

      Right. Hence the "...and I don't believe I know any gamers that buy processors in lots of 1000" in my post. >8)

    9. Re:Did I miss something? by Loconut1389 · · Score: 1

      uh.. no..

      you're effectively buying an extremely capable computing machine which happens to have a nice graphics card for probably around $4,000 to 5,000 total if you take into account lots of fast SATA or SCSI disk space (might as well do it up right?) and a good graphics card.

      granted, theres very little software and practically zero games for itanium- as of yet.

    10. Re:Did I miss something? by Rei · · Score: 1

      you're effectively buying an extremely capable computing machine ... to use as a gaming machine. You're getting the superfast processor to alleviate the need for a good graphics card. That's what the article was all about - go back and check it out for yourself:

      "Having an affordable chip one step above a Xeon or Opteron in floating-point performance would not be such a bad thing for gaming enthusiasts (or 3D artists)"

      Not that I'd call 1.5-2.5k$ per chip "affordable" for a gaming box, but some people spend ridiculous amounts on their systems... Graphics, there's more logic in that (as graphics processing can be CPU intensive and, depending on the work, may not be doable on the video card), but gaming? If your interest is gaming, get a couple hundred dollar top-of-the-line gaming card, a reasonable speed CPU, and be done with it.

      --
      "It felt almost as good as stealing cars from grandma." -- Margaret Thatcher, probably.
    11. Re:Did I miss something? by Fareq · · Score: 1

      To be fair the Intel Pentium Extreme Edition (or whatever the new dual-core EE is being called) runs for $995 in 1000-unit quantities. (At least, that's what I recall reading... but I'm too lazy to check tomshardware right now...)

      $1172 is very expensive, but if you are already considering a $995, it might not be entirely out of the question...

    12. Re:Did I miss something? by Velk · · Score: 1

      Is there anything at all that a 1.4GHz itanium would run better than a dual 3.2GHZ p4 ?

    13. Re:Did I miss something? by Anonymous Coward · · Score: 0

      >The platform isn't deployed in sufficient quantities to create enough demand for commercial vendors to bother supporting it yet

      Maybe you live in the PC server world, in the UNIX server world it is well supported. It doesn't need any special requirements. It runs Linux and HP-UX and UNIX vendors have already ported their software, they are excellent machines, very fast.
      The press seem not to regard it highly but UNIX & scientific people love it.

    14. Re:Did I miss something? by MynockGuano · · Score: 1

      I work for DoD HPC. We use SGIs, and we're having a bear of a time converting our server platforms from IRIX/MIPS Onyx machines to Linux/ia64 Altix machines, for this reason alone. It just isn't feasable to dump 90% of your commercial software to move to another platform, regardless of its technical merits. With a workflow based around these software packages, you can't just up and obsolete everything to switch. For in-house stuff, it's great, naturally, and anything you can do with Open Source. It's the commercial software (modeling and simulation, in our case) that holds everything back.

  3. The whole article (ICOS) by Anonymous Coward · · Score: 5, Informative


    The chipmaker has released two new Itaniums for two-processor servers as part of its effort to eliminate price premiums on the chip.

    Intel announced on Monday two new Itanium processors for two-processor servers, another step in the company's efforts to eliminate price as a barrier to Itanium acceptance.

    The 1.4GHz Itanium 2 with 3MB of cache is designed for servers in clusters. The new chip will provide about 25 percent more performance and cost much less than the initial Itanium optimised for clusters, which came out last year, said Jason Waxman, director of multiprocessor platform marketing at Intel.

    The second new chip, a 1.6GHz Itanium 2 with 3MB of cache, is optimised for higher performance in general-use two-processor servers, he said.

    Waxman reiterated that Intel is working on several technologies that will eliminate any price premium on Itanium by 2007 and thereby allow its performance advantages to, hopefully, blossom.

    "The price/performance balance will be heavily in favour of Itanium," Waxman said.

    With the focus on price, the Itanium melodrama is once again reaching a turning point. After several years of delays, the chip family debuted in 2001 to poor reviews and negligible customer acceptance. A second version of the chip that appeared in 2002 dramatically improved performance but failed to spark the market.

    Itanium finally began to gain acceptance in 2003 with Madison, a new version of Itanium 2 that substantially improved performance again and lowered the cost. Intel shipped about 100,000 Itaniums in 2003, compared with only around a few thousand for the first two years. Itanium volume is expected to double this year, chief executive Craig Barrett said in February.

    But in 2004, Intel announced that it would come out with a version of its Xeon chip that runs both 32- and 64-bit code. Xeon and Pentium chips typically run 32-bit code. Itanium runs 64-bit code, which, among other advantages, lets a computer maker pack far more memory into a computer.

    Itanium, however, requires completely different software to work well, a factor that has hindered adoption. Part of the appeal of the Opteron chip is that it can handle larger memory loads in 64-bit mode on essentially the same software base.

    Lowering the cost of Itanium servers won't eliminate the software issue, but it will begin to create an environment in which greater acceptance could occur, which in turn could cause software developers to gravitate to Itanium. Analysts and PC makers have viewed this theory with various doses of scepticism, but the range of opinion is generally substantially less negative than it was 18 months ago.

    Price drops have already had some effect. In 2002, a two-processor Itanium server cost about $18,000 (£9,859). With the new chips, a similarly configured system can sell for less than $8,000, while basic one-processor Itanium servers will go for just more than $2,000.

    Some of these price cuts have come as a result of Moore's Law, which predicts that the number of transistors on a chip will double every 18 months. But Intel has also expanded its product line to better suit the economic realities of two-processor servers. The company also designs and partly manufacturers many of the Itanium servers on the market, which cuts independent engineering costs.

    To lower the price further, Intel will begin to create products and add features to Itanium so that Itanium servers can be made out of many of the same components as Xeon servers. In 2005 and 2006, Itanium servers will be able to use the same memory or other components of Xeon servers, Waxman said.

    In 2005, Intel will also come out with two different chipsets for Montecito, the next major version of the chip. One chipset will wring maximum performance out of the chip, Waxman said, while the other will allow server makers to insert Montecito into their Madison-based servers, thereby cutting down independent design efforts.

    By 2007, Intel will

  4. compatibility by Anonymous Coward · · Score: 5, Insightful

    Because Intel tried to force everyone to jump on the 64bit bandwagon at once, while windows didn't even support it yet, without backwork compatibility to existing 32bit software. It's a good design, just doesn't (didn't ?) fit well with the mass market at the time of the release.

    1. Re:compatibility by Anonymous Coward · · Score: 0

      What do you mean no back"work" compatibility? When I was playing with a itanium box years ago, I could even install DOS and Windows ME without any trouble, except for the lack of drivers for some of the hardware.

    2. Re:compatibility by Anonymous Coward · · Score: 1

      I think the article which was linked to said it best:

      "...Xeon and Pentium chips typically run 32-bit code. Itanium runs 64-bit code, which, among other advantages, lets a computer maker pack far more memory into a computer.

      Itanium, however, requires completely different software to work well, a factor that has hindered adoption. Part of the appeal of the Opteron chip is that it can handle larger memory loads in 64-bit mode on essentially the same software base. "

      I still haven't seen a 64-bit version of windows for sale. When M$ releases a 64-bit version on windows, we'll probably see sales rise for those hardcore CPU hogs (digital video, gamers, /.ers, etc.). Until then, it'll remain a server technology, and a few desktops running *nix.

    3. Re:compatibility by Anonymous Coward · · Score: 1

      It also cost way too much. And it still is too expensive for most mere mortals. The question at the core (no pun intended) of this article is stupid. It sounds like Intel's marketers didn't want to pay for a study and thought they'd just ask Slashdot why their chips suck so much. Price, price, price and anti-consumer design decisions. Oh, and it would help if Intel could make decent motherboards for its own chip.

    4. Re:compatibility by hackstraw · · Score: 3, Informative

      Itaniums do run 32bit applications. At least for Linux.

      However, if your running a 32bit OS on a 64bit machine, something is not right.

    5. Re:compatibility by TykeClone · · Score: 4, Insightful

      Sounds like the days of DOS and Windows 3.1 - a 16 bit operating system on a 32 bit platform.

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    6. Re:compatibility by tleps · · Score: 2, Interesting

      Well, Without drivers it ain't worth much, is it? I'm not sure I could talk anyone into spending 2 grand & then slipping in that half the hardware they have invested in will likely never see support... and as far as gaming goes, without the drivers for the game pads\joy sticks\what ever it is they like to use, there isn't much gaming at all. Besides, you might have gotten it to install, but that is a far cry from getting it to perform acceptably with the 5 to10 grand they have invested in software. The performance didn't, and still doesn't, even come close to what they already have. Not much of an upgrade when the software runs slower... Consumer\small office VS large corporate back office are two very different worlds. Flops don't mean much to 95% of the market - if what they already have & what they want down the road don't perform at least as well on the new platform as the one they already have, your never gonna get them to buy it, even if you market the hell out of it. You all need to go back & read the why's of the fiasco - the info is all over the web.

    7. Re:compatibility by drgonzo59 · · Score: 4, Insightful
      Their hardware might be really good but the days of every hardware company making its own OS and applications is long gone. Software is just as important. So now hardware companies have to release products that will run the existing software and have room for future improvement. Intel when it released the 64 bit Itanium was still living in the 80s thinking it was controlling the computer market. Also in the late 80's and early 90's there wasn't as much software around a lot of companies could afford to switch to a new platform, today it is much much harder to do it.

      I think AMD has clearly won the market in terms of the consumer 64bit processor. And I can buy a double-core AMD today but I couldn't get a double-core Intel offering for a good price.

    8. Re:compatibility by FatherOfONe · · Score: 1

      This is the exact reason that almost everyone (Sun, Microsoft, IBM and others) are going to more of a VM enviornment. Either Sun's Java or Microsofts whatever...

      "If" Intel could have pushed Java more, then getting people off of one of their platforms to another wouldn't have been that big of a deal.

      Granted this still doesn't solve the hardware driver issue, but at least the core apps would work, and thus people would be less afraid.

      --
      The more I learn about science, the more my faith in God increases.
    9. Re:compatibility by zardo · · Score: 1

      I think its their marketing practices that have turned public opinion against them, like microsoft. They have become a burden on the industry with their non-price competition.

    10. Re:compatibility by Tony+Hoyle · · Score: 4, Funny

      Old joke. And you misquoted it...

      "Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition."

    11. Re:compatibility by Anonymous Coward · · Score: 0

      Honestly though, in the long term cold turkey would've been better, wouldn't it?

      Think about Itanium based boxes for consumers now, along with the slight increase in performance gains given by being pushed by market.

    12. Re:compatibility by MynockGuano · · Score: 2, Insightful

      Consumers aren't going to start paying 10x as much for their processors "cold-turkey", no matter how sound the long-term outlook is.

    13. Re:compatibility by man_of_mr_e · · Score: 4, Insightful

      It's not just compatibility, though that's also a big issue. The problem is that the compilers for the Itanium just aren't that mature. It's the same reason the PPC sucks so bad on a lot of benchmarks.

      Hand optimized assembly will give you screaming fast results. Unfortunately, you can't build modern applications that way and you end up having to rely on the compiler to optimize for you. On the x86, the compilers are amazingly efficient these days by contrast.

      If you've got a 64 bit database, and a 64 bit OS and a 64 bit middleware, what more do you need? You don't need to run photoshop on it. Compatibility is only marginally an issue on servers.

    14. Re:compatibility by Abreu · · Score: 1

      Sorry if Im too young to fully understand the joke... But what was the 4 bit processor MS-DOS was written for?

      --
      No sig for the moment.
    15. Re:compatibility by LWATCDR · · Score: 2

      Actually there are several more reasons all related to compatibility.
      1. It was slower than a P3 running 32 bit code.
      2. Required a "brilliant" compiler to get good speed.
      3. Half hearted windows support.

      So it became a bit player for thoses that needed really fast floating point and that would write custom software to get it.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    16. Re:compatibility by Detritus · · Score: 1

      It might be the Intel 4004, although CP/M was initially targetted at the Intel 8080. MS-DOS was (mostly) a clone of CP/M.

      --
      Mea navis aericumbens anguillis abundat
    17. Re:compatibility by ciroknight · · Score: 1, Troll

      Oh well, I love AMD for their work, but I really think they barked up the wrong tree. I would have supported whole heartedly an implementation of PPC 64-bit or even some grounded up archetecture just as much as I supported Itanium, but they decided to go the cheapest route, faking it for the sake of performance.

      Secondly, the Itanium's really not a consumer chip, as much as Intel wants it to be. The Itanium's a hella fast server chip, and that's where it'll stay for the rest of its diminuative mitigated life. I liken it to the POWER chips.

      Now, if Intel got off their asses, they'd realize they could have it both ways if they wanted. Release a chip that's got a true x86-32 bit core and a true 64-bit Itanium core, run them in parallel and when code comes for a 32 bit processor, let it run on the x86 core. The earlier P6 cores would suffice, hell, even a Pentium M with a smaller cache and a lower clock speed would work. But that's a very complicated solution, and it's really playing to the masses.

      Lastly, I don't want to sound too harsh on AMD, they really are doing their best to get back marketshare, but I really feel they've headed in a bad direction. While it seems like a good business move, it's terribly prolonging x86's life. On top of that, it's causing a huge stir in the market, especially where it concerns the hundred billion dollar giant Intel and the even worse, Microsoft. While both are bloated monopolies, they both have enough money and enough power to shut AMD up permanantly, and where would we be left, Transmeta??? Please. AMD needs to play their cards right and not be so infuriated; their gains are there, for the first time their server hardware is there, they just need to get their reputation running for them. It's really such a complex issue that I don't know where I stand with AMD anymore. I hate them for x86-64, but I love them for their speed. I hate them for keeping Itaniums out of my reach, but I love them for gaming. So complex an issue.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    18. Re:compatibility by flakier · · Score: 1

      IIRC, the 32-bit legacy x86 mode performance of the Itanium is really, really slow because it's emulated. Basically no one in their right mind runs 32-bit code on them.

      --
      --
    19. Re:compatibility by ma_luen · · Score: 1

      I just went to newegg.com on their specials they list a Pentium D starting at $253. The lowest priced X2 is $539. While the AMD is a better performer and has better power consumption it is completely wrong to say you can't get an intel or that it is not at a good price.

      Further, the consumer market for desktops seems (from my non-scientific sample) to be centered around $1000 to $1500 price point. The cost and supply issues around the X2 chips makes them rather unattractive for this segment.

      In summary I completely agree with the first half of your post (but I think improving emulation and virtualization technology will change the situation. The second half seems to be totally out of touch with the reality of the current processor market.

      Mark

    20. Re:compatibility by TykeClone · · Score: 1, Informative
      Not really. MSDOS and Windows 3.x (if I remember correctly) were a 16 bit operating system.

      The intel 386 cpu was a 32 bit platform.

      The joke was derived from this...

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    21. Re:compatibility by TykeClone · · Score: 3, Informative
      Not really. MSDOS and Windows 3.x (if I remember correctly) were a 16 bit operating system.

      The intel 386 cpu was a 32 bit platform.

      The joke was derived from this...

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    22. Re:compatibility by Anonymous Coward · · Score: 0

      Wouldn't this be the same thing as the parent stated. A 16-bit Operating System running on a 32-bit computer?

    23. Re:compatibility by Anonymous Coward · · Score: 0

      The original Itanic was actually slower than a 486/100 running 32 bit code in many cases. They eventually got rid of the 386/486 speed hardware 32 bit support and used a halfway decent dynarec emulator in later versions though which improved 32 bit performance considerably (not hard to do, even Bochs was faster than the hardware 32 bit support).

    24. Re:compatibility by Anonymous Coward · · Score: 0

      Intel was a real small player in 80's and beginning of 90's. IBM, Sun, SGI and HP had a lot more advanced circuits at that time. What Intel did and have made its enourmous success is Pentium Pro and forward. Pentium Pro kicked the RISCs in performance, and totally spanked them in price/performance.

    25. Re:compatibility by Azzhole · · Score: 0, Troll

      The format of this site sucks.. Lemme re-phrase. AMD and Linux are the greatest thing since Costa Rican Poontang ! Understood ?

    26. Re:compatibility by prisoner-of-enigma · · Score: 5, Informative

      Sure, an Itanium will run all your existing 32-bit stuff...in compatibility mode, which means you get performance akin to a 300MHz Pentium-II on your $2000 CPU. Remind me again why I'm supposed to buy Itanium?

      But to return to seriousness again for a moment, the Itanium isn't pitched at mainstream anymore, and it's debatable whether it ever was. It's an entirely new ISA -- and a very good one at that -- and software developers just didn't see a good reason to jump on it when cheap x86 CPU's were selling like hotcakes.

      Intel would've loved to have forced the entire industry to move to IA64 years ago. If it had done so before the Athlon XP ever hit the scene, it's possible the chip giant could have pulled it off. However, with the advent of the Athlon XP (and MP's as well), if Intel abandoned x86, AMD would be there to pick up the pieces, giving customers the option of (a) continued use of their paid-for apps and paid-for OS's on a cheap, fast, x86 chip or (b) loss of all practical use of your 32-bit apps and OS's, total rewrites and recompilations of all core software bits, all on a $2,000 CPU. It's quite clear why Intel didn't try to do such a stupid thing.

      So, on the one hand, we can thank AMD for giving us cheap, fast CPU's that run pretty much whatever you want these days. On the other hand, we can thank AMD for keeping us stuck on x86 to begin with, for without AMD we'd almost certainly all be on IA64 today. But, since I like competition, I can say I'm extremely glad things turned out the way they did. IA64 would've been the death-knell for AMD and any other kind of competition, and Intel would be milking us for all we're worth today if it could.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    27. Re:compatibility by AuMatar · · Score: 1

      I'm not so sure that the IA64 ISA is all that great. THe main problem is the VLIW instructions. Compiler technology is just not good enough to actually parallelize instructions for it. The end result being very poor performance, especially for the cost. Thats why Intel had to re-add the out of order execution unit so late in the game. Sure, its cleaner than x86, but VLIW was a big mistake.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    28. Re:compatibility by GreatBunzinni · · Score: 1
      However, if your running a 32bit OS on a 64bit machine, something is not right.

      And usually something isn't right, unfortunately.

      Just like in the jump from 16 to 32bits, there is a lot of hardware that right now doesn't have 64bit drivers. That halts a lot of x86 to x86-64 switches. Personally, right now I have a AMD Athlon64 that I run kubuntu x86 because there isn't x86-64 drivers out there for the wireless modem, which is a damn shame. If they existed, I wouldn't hesitate in upgrading the OS.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    29. Re:compatibility by TheRealMindChild · · Score: 1

      I think the ultimate solution will be "hybrid" processors. Right now, we are forced to have all the backward compatibility to run crap that ran on processors older then my toe funk, but maybe, once the x86_64 architecture has been around a bit (or something magically better comes along in the future), you could buy "migration hybrid processors", which we essentially run right now... has the whole mess of crap in there to run everything. Then when you are comfortable with it, buy the slimmed down "64-bit only NIGGA!" version.

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    30. Re:compatibility by prisoner-of-enigma · · Score: 1

      Given the absolutely incredible performance you can obtain from properly-compiled VLIW code, I'd say "big mistake" is about the worst adjective you could apply. Itanium is a great processor in search of software, nothing more, nothing less.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    31. Re:compatibility by AuMatar · · Score: 2, Insightful

      Except that a compiler that can create such code doesn't exist, and has never existed. EVen the best compilers are unable to keep the Itanium pipe decently full. And writing hand rolled code for it is a *huge* PITA. If a feature increases theoretical performance at a high hit to actual performance, I would classify that as a big mistake. WHen a compiler that can do VLIW well comes out, I'll reconsider it. Thats going to be at least 3-5 years down the line though.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    32. Re:compatibility by NatteringNabob · · Score: 1

      > Itaniums do run 32bit applications. At least for Linux. The problem is that Itanium doesn't run X86 pre-compiled Win32 binaries as fast as Opteron and Xeon do, and for the vast majority of computer users, and 90% of desktop computer users, that is all that matters.

    33. Re:compatibility by Nutria · · Score: 1

      Sorry if Im too young to fully understand the joke... But what was the 4 bit processor MS-DOS was written for?

      "4 bits" == 50 cents.

      So, besides the "decending powers of 2" numbering system, the joke implies that that the 8088 is cheap, and therefore sucks.

      --
      "I don't know, therefore Aliens" Wafflebox1
    34. Re:compatibility by Nutria · · Score: 1

      MS-DOS was (mostly) a clone of CP/M.

      v1.0 was a CP/M work-alike at the API level.

      IBM rewrote it for v2.0 (because they didn't trust MSFT), adding in all the stuff we greybeards came to know and hate.

      --
      "I don't know, therefore Aliens" Wafflebox1
    35. Re:compatibility by snookums · · Score: 1

      Hear, hear! If I was in the market for a CPU upgrade, I'd be looking very seriously at one of the the low-end Pentium D models.

      The sorts of things that I do with my workstation (video processing and compiling software) would really benefit from going to a dual core at the cost of a little GHz. However, AMD have limited the choices and priced themselves out of this market. All of the X2 chips are a "step up" from the Athlon64 range, with no direct choice of "would I rather have a faster clock or two cores?". A serious gamer would take the faster clock (given the current crop of games), but I would take the dual core.

      Now I'm assuming, based on the benchmarks and recommendations that I've read, tthat he core market for Athlon64 is gamers, so perhaps this explains the otherwise baffling hole in AMD's processor range.

      --
      Be careful. People in masks cannot be trusted.
    36. Re:compatibility by Nutria · · Score: 2, Insightful

      they decided to go the cheapest route

      Tell us again why doubling the number of registers (which is what AMD64 does in 64-bit mode) is such a bad thing?

      Remember, AMD didn't do what Intel did in 1985 and just strech the registers, without adding any.

      --
      "I don't know, therefore Aliens" Wafflebox1
    37. Re:compatibility by prisoner-of-enigma · · Score: 2, Insightful

      Keeping the pipeline "decently full" isn't just dependent on the compiler, you know. You need to have the right kind of operations, operations that can be made parellel in the first place. Fluid simulation, finite-element stress analysis, nuclear warhead testing simulation, galaxy formation...all of these types of calculations are fairly easy to make parallel and will keep the Itanium pipes running quite efficiently with Intel's VLIW compiler. If you doubt this, just look at some of the benchmarks you can get out of Itanium's running such code. It really is a good architecture working with a good compiler. Nothing's perfect, but it's simply not the dog you claim it to be.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    38. Re:compatibility by Nutria · · Score: 1
      I think its their marketing practices that have turned public opinion against them, like microsoft.

      No, no, no.

      The issues are:
      • it was really, really late
      • it is really expensive
      • it was slow
      • it's got a really, really stupid name
      • it's egg-frying HOT
      • Opteron kicks ass & takes names, even with existing, paid-for, software


      Thus, nobody except supercomputer geeks has any need for it.

      (VLIW fits vector processing like a glove, and the Itanium2 Madison has some very impressive floating point specs.)
      --
      "I don't know, therefore Aliens" Wafflebox1
    39. Re:compatibility by Anonymous Coward · · Score: 0

      Well, the 8086 is a decendent of the 4004: 4004 -> 8008 -> 8080 -> 8085 -> 8086

      Even so, the 8086 was a 16 bit processor, and DOS was a 16 bit OS. (well, 16 + 4)

      The joke is horribly broken, but some people find it funny anyway. Shrug.

    40. Re:compatibility by codeguy007 · · Score: 4, Insightful


      Oh well, I love AMD for their work, but I really think they barked up the wrong tree. I would have supported whole heartedly an implementation of PPC 64-bit or even some grounded up archetecture just as much as I supported Itanium, but they decided to go the cheapest route, faking it for the sake of performance.


      So what did AMD fake? The designed a 64 Bit processor with full backwards support to 32Bit code. That's nothing intel didn't do before remember 16/32Bit?

      Also AMD Opteron technology was designed by some of the brightest people to ever come out of DEC. These are the guys that designed Alpha. In fact there are designs for the next generation Alpha that would compete with anything currently out there. Compaq just couldn't afford to pay the large cost of converting the FAB.

    41. Re:compatibility by Fareq · · Score: 1

      riight...

      "Hey everybody, we want you to switch to this cross-platform language that runs all apps 85% slower. Then you will see the tremendous advantage our new $2000 processor provides... Instead of an 85% drop, its only a 40% drop!"

    42. Re:compatibility by MojoStan · · Score: 1

      In addition, the GP thinks "AMD has clearly won the market in terms of the consumer 64bit processor." IMO, I don't think anybody has "won" the consumer 64-bit processor market because 64-bit Windows is not widely used yet. But now that Intel has released 64-bit versions of the Pentium 4 500 series and Celeron D, I think Intel will win this market. I think Dell's 64-bit sales alone will outnumber the sales of Athlon 64 and 64-bit Sempron.

      --
      TO START
      PRESS ANY KEY

      Where's the 'ANY' key? I see Esk, Kitarl, and Pig-Up...

    43. Re:compatibility by Miguelito · · Score: 2, Informative

      Itaniums do run 32bit applications. At least for Linux.

      Yeah, and the speed sucks ass. Even Intel recommends against running any 32bit code on the Itaniums.

      I think the reason it's not doing as well as they hoped, and compared to the benchmarks, is because, in real-world performance, they're not that great. We've got 13 itanium boxes in house, all of them cost huge $ (we can't get the cheaper low-power ones, we need speed above all else) and their usage levels over the last few months has bottomed out.

      Before tools were available for the amd64 line, the IA64s were used pretty heavily by our engineers. Especially when near the end of a chip design, because they needed to be able to do things like have a single process malloc over 40Gig of ram.. yes, I said 40Gig! Seeing that in top on a linux box is something. The speed compared to SPARC boxes is a huge jump. However, now that the tools are all coming out with amd64 versions, they're all moving there. We can get boxes there with huge ram, and they get 64bit, and they're seeing better performance. This may be at least partly due to some steps in their batch runs being 32bit.. which can't really be changed right now, so the ia64 suffers heavily then.

      So who cares what the benchmarks say.. all that matters is how the apps the engineers need to run perform. Today, amd64 kicks the ia64's ass.

      --
      - My favorite error message: xscreensaver, running on an old Sparc 5 w/ 8bit color: bsod: Couldn't allocate color Blue
    44. Re:compatibility by Anonymous Coward · · Score: 0

      moron..

    45. Re:compatibility by timjdot · · Score: 1

      What I heard was INTC was supposed to release 1.6GHz already, 2GHz end of summer etc. revs but canned it. So, those who went itanium got burned. does it make AMD more attractive?

      --
      Expect Freedom.
    46. Re:compatibility by Anonymous Coward · · Score: 0

      "However, if your running a 32bit OS on a 64bit machine, something is not right."

      Well, people do it with AIX frequently. 32-bit kernel on a 64-bit capable CPU.

    47. Re:compatibility by Methlin · · Score: 1

      Dunno what cave you've been living in but XP Pro x64 has been available since late 2004. You can even download an 180 day trail version direct from Microsoft. There's also an x64 version of Server 2003 available.

    48. Re:compatibility by john_uy · · Score: 1

      where's the 64-bit? :)

      --
      Live your life each day as if it was your last.
    49. Re:compatibility by bakes · · Score: 1

      I think the original joke was referring to Windows 95, which is a 32bit OS.

      Windows (95) is a 32-bit extension to a 16-bit graphical shell (Win 3.1/3.11) for an 8-bit OS (DOS) ... etc.

      --
      Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
    50. Re:compatibility by TykeClone · · Score: 1
      Although I did a poor job of it, I was relating that we had a similar situation to the 64bit Itanium/32 bit WinXP situation with the 386 family of CPUs (32bit CPU/16 bit or 8 bit OS).

      I really wasn't trying to joke :)

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    51. Re:compatibility by hjf · · Score: 0
      I'm not so sure that the IA64 ISA is all that great. THe main problem is the VLIW instructions.

      Let me translate for you "Must Be New Here"s. This guy, who apparently calls himself "AuMatar" is the typical ultra-conservative slashdotter. He thinks he knows better than the rest of us. I happened to click on 3 random comments on his profile and found him bashing perl and praising C, and talking shit about innovation on Wolfenstein. So disregard his opinions about what HE thinks is right. Let me put it this way. The guys at intel decided to do the processor that way for some reason, which we, the rest of the mortals, maybe will never understand, because -- well, most of us mortals don't design processors.
      IMHO (that is, *I THINK*), the VLIW stuff was decided in an very early stage of development, and the engineers said, well, if this isn't the processor for Joe Sixpack and will not be running your regular, generic, one-size-fits-all code, then we can do a processor that will be exceptionally efficient when it's correctly programed, a situation that WILL happen in the environment Itaniums are used. Take for example, particle simulation. The guys using that kind of app will squeeze every last drop of performance they can get -- and if that means coding some parts in assembler, they will.
      So, new people here, take my word and try to ignore comments from people who think they know it all -- at least I say "I THINK INTEL DID THIS BECAUSE OF THAT" and not try to play smart and say "INTEL IS WRONG, WHAT I THINK IS RIGHT".
    52. Re:compatibility by petermgreen · · Score: 1

      well amds architecture won. intel is now the clone builder. (intel find this rather embarrasing which is why the chips they make that support amd64 aren't heavilly marketed as such)

      otoh there is no doubt that intel can out-produce amd and will make 64 bit chips simply because they can make more in total.

      switching to native amd64 will probablly take quite some time. driver issues are much bigger now than in the 286/386 days when people ran dos and there isn't a hugely pressing need at the consumer end yet but its the way things are headed.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    53. Re:compatibility by Grishnakh · · Score: 2, Informative

      Fluid simulation, finite-element stress analysis, nuclear warhead testing simulation, galaxy formation...all of these types of calculations are fairly easy to make parallel and will keep the Itanium pipes running quite efficiently with Intel's VLIW compiler.

      That's all well and good if you're a government researcher with access to an Itanium-based supercomputer. But the rest of us don't spend our time testing nuclear warheads; we're just reading email, surfing the web, working on office documents, etc. These types of tasks haven't been shown to perform very well on an Itanium system; in fact, they don't seem to work that well on Intel's lower-end CPUs using the Netburst architecture either, because of the high cost of context switches. For most people, what we need is a CPU with multiple cores, fast context switching, and a nice-sized cache so we can have lots of web browser windows open along with our music player, email client, word processor, etc.

    54. Re:compatibility by jayloden · · Score: 1
      However, if your running a 32bit OS on a 64bit machine, something is not right.
      Not that I don't agree with your statement, however:

      I own an AMD64 machine, and I have for quite a while. However, it runs 32bit versions of Linux and always has, for two reasons:

      1. Linux in 64bit wasn't available (for free) in my first OS of choice at the time. I've since switched distros
      2. When I did finally run 64bit Linux on it, I ended up reinstalling the 32bit version after three days. Libraries weren't easily available, and other things like firefox and certain multimedia codecs didn't exist at all. You could run the 32bit Firefox, sure, but when it came to codecs, your only option was to run a chroot environment with 32bit binaries and libs inside your 64bit OS. Pardon me for not being geeky enough here, but I prefer "apt-get install w32codecs" when I want to watch some videos.
      I agree, you ought to run a 64bit OS to take fulle advantage of your hardware...but sometimes it's not always that feasible. I'll give you another example. The company I work for makes a enterprise level software product that is only supported in 32bit environments (and indeed, at the moment only compiles properly in 32bit). Companies have expensive contracts to run our software, so they run 32bit OSes, regardless of the hardware, until we can port our product.
    55. Re:compatibility by Xabraxas · · Score: 1
      I couldn't get a double-core Intel offering for a good price.

      I am an AMD fan but that is simply not true. You can get a dual-core Pentium D computer for $999 at an electronics retailer.

      --
      Time makes more converts than reason
    56. Re:compatibility by Anonymous Coward · · Score: 0

      Plenty of people run a 32bit OS on 64bit machines, WinXP32 and AMD64 chips, it's not right, but it's what an awful lot of people choose to do and it does work reasonably well, most end users wouldn't see a huge benefit from having a native OS anyway.

      With an Itanic, things are far different, IA32 apps run in an extremely slow emulation mode. That's not to say that a 64bit non-x86 chip can't run IA32 code through emulation at a fair pace, there was the Alpha, until intel killed it off to make way for the hideous itanium.

      as far as adoption goes, it's a big commitment, you really have to target your software specifically at IA64 in order to benefit from any of the peformance available, and avoid the drawbacks, and it's highly unlikely that any other chip makers are going to pick up IA64 as a basis for a competing chip, itanium is a complete intel lockin.

    57. Re:compatibility by Guppy06 · · Score: 1

      "On the other hand, we can thank AMD for keeping us stuck on x86 to begin with, for without AMD we'd almost certainly all be on IA64 today."

      Personally, I'm thanking AMD for making the AMD64 architecture hardware-compatible with the 32-bit instruction set, just as Intel made the Pentium backwards-compatible with the 16-bit 486. It's nothing but hubris on Intel's part to expect the world to change overnight for just a processor, any processor.

      I've got an AMD64 box, and I've tinkered with 64-bit NT 5.2 a little bit. My conclusion right now is that it gives me all the "joys" of Windows with all the "advantages" of Linux-esque driver support. Until Microsoft can remember how they got 16-bit drivers to work in Windows 95 in compatability mode, today is not the day to jump to 64-bit hardware and software on the desktop.

      However, I can still dual-boot with NT 5.1, and it works fine while waiting for the rest of the world to catch up. This is not an option on Itanium.

      Now that I think about it, Intel's "64-bit only!" stance is exactly what's holding back 64-bit applications to begin with. AMD64 can handle 32-bit drivers just fine, it's because of Itanium that Microsot rigged their 64-bit OS to require 64-bit drivers. If Microsoft would simply drop support for the Itanium in its products, save the resources spent on "Windows on Windows" emulation (a non-issue on AMD64 machines, so sayeth Microsoft's own documentation), I could see the world moving on to x86 64-bit machines within two years, tops.

      Can't Microsoft at least fork 64-bit Windows? After all, they maintained different codebases for NT for how long now? It was only with NT 5.x that they dropped Alpha support...

    58. Re:compatibility by booch · · Score: 1

      Isn't performance the goal here? How can you fault AMD for increasing CPU speeds and reducing costs? If you're wanting to find a fault, at least find it in their short-term gains leading to a long-term dead end. And AMD aren't keeping Itanium from you. AMD has very little control over Itanium. Do you think Intel would ever let AMD make an Itanium? Come on.

      The real question is: what will replace x86? Obviously not Itanium. But like you, I don't see x86-64 lasting all that long either; but maybe we're wrong. So what will be the next CPU architecture? I guess it depends on where software goes. In the small/mobile/gadget space, I think ARM has a lot of room to grow. In the server market, it depends on whether Microsoft will port to any other architecture, or if Linux on another platform becomes popular. The only likely contender in that space is POWER/PowerPC. I had hope for SPARC at one time, but I don't have much confidence in Sun at this point. For PCs, I don't see any clear choice. The interesting thing about all these markets is that power consumption will be a major factor.

      Maybe the answer is that we won't really get much faster, or much improvement in architecture. There really isn't all that much demand for significantly faster PCs. And the current trend is toward multiple CPU cores. I think that trend will be significant in the PC and server spaces over the next several years. We also seem to be on the edge of a major shift toward mobile computing devices. So perhaps a slow-down on the PC won't even matter that much. That still leaves the matter of server CPUs, but even there, it's more about I/O than computation.

      I miss the DEC Alpha.

      --
      Software sucks. Open Source sucks less.
    59. Re:compatibility by Macka · · Score: 1


      Huh? Compaq didn't have a FAB. The one that DEC had got sold off to Intel as part the DEC vs. Intel law suit way before Compaq took over the helm.

      Compaq killed the Alpha because of two reasons:

      1) bad, visionless (small) box-pushing mentality of its senior management. All the flim flam about cost was just an excuse. At the time Compaq announced the death of the Alpha chip and the move to Itanuim, the Alpha server line was enjoying its biggest growth numbers for many years, and it was making strong profits.

      2) Compaq management, being so close to Intel and all, believed the Intel hype about IA64's mass market appeal, and the economies of scale that would bring. If nothing else, Intel managed to convince a competitor to commit an act of infanticide and in so doing, removed a serious threat to the adoption of IA64. Just imagine if Alpha had not died. What little market share IA64 has managed to grab would have been beaten to death by faster, stronger and cheaper Alpha chips.

    60. Re:compatibility by Ty_Berg · · Score: 1

      One question that I have is "was the Itanium really built for windows"? However you will probably not get an Intel Exec to admit this, my bet is the Itanium has made a stance in the HPC arena with Linux. Had they made the open development with the Linux community i.e. like IBM's cell has been doing it might have been accepted more into the community. So other that for HPC what do you want the Itanium to do, be a desktop processor? But you can't deny the fact that once Itanium was rolled out there was more interest in the x86 community on 64-bit computing; AMD did well on this with their x64 extensions, which rolled later on that year. (I believe that it was within a year maybe not that year) Plus the inherent transport system that AMD rolled as well to allow transparent upgrade to dual core when the technology was still not available (or just to high in price to market) now you have the new Pentiums with the 64MT (--correct sp?) extensions that allow the x64 like performance. So how many versions of M$ winders are you now going to have? I count three, M$ will _love_ to market that. Even though I harp on windows I still use the x64 version of XP Pro on my laptop since you got the free trade in to x64 if you had a valid XP Pro 32-bit license. I have to say the performance for _native_ 64 bit is _really_ good but absolutely bogs when you run as well with the windows-on-windows (Microsoft solution to run 32 bit apps in a 64 bit space) I learned this first hand when I tried to run a 32-bit virus scanner on 64 bit windows (_Dum@$$_Idea_) Games run kind of messed up to sometimes needing a patch like Far Cry did. Or you notice visually that the video will outrun the sound (leisure suit Larry). My point here is that I've had some mixed haphazard results with it but have been pretty happy once I started getting 64-bit native apps. So until you get software vendors to ship _native_ software then you will run into this issue a lot! So what AMD has made now is a market for what I call the 64-bit desktop market and will get vendors more on board to compile 64-bit friendly versions of their software, which will then create the demand for the 64-bit environment that is pretext by the Itanium. Then the drive will be the 64-bit _only_ desktop, followed by a 64-bit only offering by AMD. Of course who do you know would run the Itanium on the desktop?

    61. Re:compatibility by Ham_belony · · Score: 0

      Wow, sounds like their profit margin on their products year after year : 1 - 2 - 4 - 8 - 16 - 32 - 64? - 128?

    62. Re:compatibility by Anonymous Coward · · Score: 0

      Look at CPU history.

      ISAs that have been designed so that compilers can optimize for a specific implementation have usually ended up with annoying legacy crap when CPU technology changes sufficiently that the assumptions no longer apply (e.g. exposing branch delay slots, register windows).

      The best ISAs are the straightforward ones; future CPU enhancements will inevitably have to be done at a CPU hardware level and will perform significant transformations on the code, anyhow.

      Additionally, any ISA that's hard to compile efficiently for will suffer from the fact that only C, C++ and Fortran compilers will make proper use of the CPU, compiler writers for less mainstream languages (such as myself) are unlikely to have the resources to tune their code generators. Not to mention JITs (not that I particularly like them), where compilation speed matters a lot.

    63. Re:compatibility by Devistater · · Score: 1

      I think he's referring to the fact that the memory address width in amd64/opteron is I think 40 bits or 48 bits or some such that only allows something like 64 gigs of RAM instead of 1 TB or whatever is allowed in full 64 bit addressing. I dont know the exact numbers, I just know the generalities which is that it doesn't have a full 64 bit addressing space for memory. That being said, does it matter? How many people have more than 4 or 8 gigs of RAM anyway? lol

    64. Re:compatibility by Anonymous Coward · · Score: 0

      and has 0 bits of ingenuity

    65. Re:compatibility by codeguy007 · · Score: 1

      True, they use Samsung's FAB but they still had to pay for the conversion. Samsung wasn't going to front the captial.

    66. Re:compatibility by codeguy007 · · Score: 1

      Opteron has 40 Bit Real Memory Address and 48 Bit Virtual Memory addressing.

      That allows for 1TB of Real and 256TB of Virtual Memory Access --- not 64GBs.

      Also that's per CPU. A quad opteron could theoretically access 1024TB (Thats a PetaByte Right) of Virtual Memory Addresses.

      I think it is fair to assume that they allowed for enough head room. Also you could always up the number of address lines in a future design if the need arose. It's been done before.

    67. Re:compatibility by prisoner-of-enigma · · Score: 1

      That's all well and good if you're a government researcher with access to an Itanium-based supercomputer. But the rest of us don't spend our time testing nuclear warheads; we're just reading email, surfing the web, working on office documents, etc.

      Very true. And for that kind of person even a 300MHz Pentium-II with 256MB of RAM would do nicely. However, there are those of us who do CAD work, signal propagation simulations, and -- above all -- gaming. Itanium can do very well in these situations, to the point of overkill.

      Also, don't constrain yourself into considering IA64 and Itanium to be the same thing. They are now, but they don't have to be and originally weren't planned to be. IA64 could have been implemented in a wide variety of chips, many much less expensive than the current Itanium. Intel wanted IA64 to become the x86 of the next generation, both from an architectual and a marketing perspective. IA64 would've freed us from the embarrassing limitation of the old x86 design (limitations we are working around today but they are still work-arounds). And, as a handy side-effect, AMD couldn't clone IA64 like it did with x86. AMD's only choice would've been a clean-room reverse engineering of IA64. AMD had no such funds (and still has none) for such a monumental undertaking. It would've left Intel completely and totally in the driver's seat for a long, long time. Thank God it didn't happen.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    68. Re:compatibility by Grishnakh · · Score: 1

      Very true. And for that kind of person even a 300MHz Pentium-II with 256MB of RAM would do nicely.

      Not true. With the current eye-candy-filled websites, Flash animations, animated ads, etc., a 300MHz P2 will slow to a crawl. Don't forget movies (like movie trailers), P2P apps, etc.

      Also, if you're like me, you will have lots of browser and application windows open at once, consuming a lot of memory. My 2.4GHz P4 with 512MB is already terribly slow when changing windows or workspaces.

    69. Re:compatibility by prisoner-of-enigma · · Score: 1

      Not true. With the current eye-candy-filled websites, Flash animations, animated ads, etc., a 300MHz P2 will slow to a crawl. Don't forget movies (like movie trailers), P2P apps, etc.

      I'm sorry to disagree with you but I must. A 300MHz P-II with 512MB of RAM and a good AGP 4X video card will not slow to a crawl during any of the above activities. In fact, the minimum specifications for software decoding of a DVD MPEG-2 bitstream is a 233MHz P-II. The slowdowns you're describing are either (a) greatly exaggerated or (b) easily fixable with a decent video card, probably one costing less than $75.

      Also, if you're like me, you will have lots of browser and application windows open at once, consuming a lot of memory. My 2.4GHz P4 with 512MB is already terribly slow when changing windows or workspaces.

      Again, I believe you're either exaggerating or having issues with another portion of your system. For example, one of our in-house-built Linux servers is running an Athlon 2500+ with 512MB of RAM on Fedora Core 4. Running X on this system isn't snappy at all. Why? Because it's using a 16MB PCI video card, that's why! You might try to blame this on the CPU or RAM, but it's eight-tenths the fault of the video card and two-tenths the fault of just how old and outdated the entire XWindows system is.

      Further, if you're one to keep a ton of things open and running all the time, and these things are consuming lots of resources, you do not fit the mold you earlier described, namely that of a user browsing a bit here and there, composing a document or two, or answering an email. Therefore your point of bringing this up is...what?

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    70. Re:compatibility by Macka · · Score: 1


      Intel also produced them for a while too, as part of the FAB-6 sale. At some point (I don't remember when) IBM got in on the act too. The new Alpha systems that are sold today (and they are still selling some) contain Alpha chips produced by IBM.

    71. Re:compatibility by Anonymous Coward · · Score: 0

      Intel still sell Intel branded motherboards, but manufacturing (and maybe design too?) are sub-contracted to Foxconn.

    72. Re:compatibility by FatherOfONe · · Score: 1

      Wow, I just read that you replied...

      85% slower than native code?

      Care to back that up with any stats?

      You won't be able to. The JVM's in the last 8+ years have improved a ton. In some benchmarks they beat C!

      In our own test we found Java performed on par with C code for "our" apps. It did take more memory, but the performance was on par with C. We did use GCC, not the Intel compiler. The core reason we didn't use the Intel compiler was that we run on AMD. :-)

      You do realize that a ton of code that Apple creates is, in fact written in Java. My point is valid, in that if they would have written more code in Java they would have less to "port" to a new platform.

      --
      The more I learn about science, the more my faith in God increases.
    73. Re:compatibility by Lucractius · · Score: 1

      thats wonderful But the rest of them no longer design those brillant multi modular high performace systems that literaly defined the alpha as a killer proccessor.

      The wonderful Opteron Doesnt Run OpenVMS, or seem to be arriving in machines that have quad proccessors 12 gig of ram standard, fiberchannel backbones, and all the trimmings in one neat modular, hot swapable package, rolling off the assembly lines.

      If someone does make opteron based hardware like that. Link me to it. I want to see it.

      --
      XML - A clever joke would be here if /. didn't mangle tag brackets.
  5. It is true for processors as it is for people... by ratta · · Score: 5, Funny

    the dead ones were always much better :)

    --
    Wondering why i am doing so strange posts? I am trying to get a "+5,Flamebait" or "-1,Insightful" rating.
  6. Brand issues? by darth_MALL · · Score: 4, Insightful

    I have certainly noticed a general move away from Intel in the past few years. I think they may have had a run of bad press and serious competition from other manufacturers lately.
    They just aren't the juggernaut they used to be. There was a time when they built it and people came. I presume choice is what's keeping the sales down.

    1. Re:Brand issues? by Anonymous Coward · · Score: 1, Insightful

      Except for Apple....eh, speaking of which, has Apple said exactly which Intel processor they'll be using?

  7. Follow the herd! by bwalling · · Score: 4, Insightful

    Why do we see so many disparaging opinions of the Itanium processor (all those 'Itanic' jokes, etc.)?

    Because people repeat what they hear. Many people here only know what has been said on Slashdot about the Itanium. They've never used one. MrDicker64 said it was crap, so it must be!

    1. Re:Follow the herd! by pdbogen · · Score: 5, Funny

      Hey, bwalling is right! We shouldn't just take what other people say and assume it's true!

      Wait...

      *brain asplodes*

    2. Re:Follow the herd! by digidave · · Score: 1

      No, it's because there is no need for anyone to every try an Itanium. Even supercomputer users can get more bang for their buck by clustering more x86s together.

      --
      The global economy is a great thing until you feel it locally.
    3. Re:Follow the herd! by MrDicker64 · · Score: 5, Funny

      I protest! For the record, I have *never* publically stated that Itanium was "crap". I reserve such sentiments exclusively for products from Microsoft.

    4. Re:Follow the herd! by chrismcdirty · · Score: 4, Interesting

      I only ever called it the Itanic because one of my professors, who works (or worked) at Intel and researched the architecture very extensively to document it also called it the Itanic. According to him, it was basically what everyone else has been saying so far.. great idea, bad execution.

      --
      It's like sex, except I'm having it!
    5. Re:Follow the herd! by jarich · · Score: 5, Interesting
      Many people here only know what has been said on Slashdot about the Itanium. They've never used one.

      I worked at a startup that was building a database ~70 gigs in size. It took 2 months to build said database. Lots and lots of very small lookups and inserts.

      Memory was our bottleneck. More ram equals more speed. So we spent BIG bucks and bought a quad Itanium with 12 or 16 gigs of memory (I forget exactly how much it had).

      The Itanium was slower than a dual X86 with 2 gigs of memory! And not just a little slower. We spent weeks trying to get the database optimized.

      Why does no one respect the Itaniums? Intel made a slow chip. Then they released the sequel. I've already paid my dues on that line once. I'm not playing this round.

    6. Re:Follow the herd! by PopCulture · · Score: 4, Funny

      you must be new here...

      --

      Here's to finally giving Bush his exit strategy in November
    7. Re:Follow the herd! by jav1231 · · Score: 2, Insightful

      Yeah, it's called research. Sorry, I don't have $12K to fork out for a machine that will run it. So yeah, I rely on what I read. You read and read and read and if you get a chance to see one you look for yourself. If not, you go with the preponderance of evident. So, how does the one YOU bought perform?

    8. Re:Follow the herd! by Anonymous Coward · · Score: 0

      Holy shiy. You were faster than me at registering that.

    9. Re:Follow the herd! by operagost · · Score: 4, Insightful
      Itanium I, right? You didn't mention when this was.

      Your anecdote probably has little to do with the current processor.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    10. Re:Follow the herd! by gnasher719 · · Score: 2, Insightful

      "Great idea, bad execution..."

      I don't think so. Itanium is a collection of everything that was a good idea in 1996. Many things that were a good idea in 1996 are not a good idea in 2005. And including _everything_ that was a good idea in 1996 wasn't a good idea in 1996!

    11. Re:Follow the herd! by tgd · · Score: 1

      Don't believe what you've read on /.

      Exploding brains are extremely uncommon. Asploding ones are even more so.

    12. Re:Follow the herd! by FyRE666 · · Score: 1

      Hmm, you know I was thinking the opposite, but now I've completely reversed my opinion! Well said!

    13. Re:Follow the herd! by Bradee-oh! · · Score: 1

      Itanium I, right? You didn't mention when this was

      Quote from grandparent -

      Why does no one respect the Itaniums? Intel made a slow chip. Then they released the sequel. I've already paid my dues on that line once. I'm not playing this round.

      I believe the grandparent's point is exactly the answer to this entire question - Intel screwed up once. And big.
      "The Itanium was a disaster and a big waste of money for my company - Why should I blindly trust Intel again for a 2nd go around?"
      If they had pretended that they were designing a new processor and released Itanium 2 with a completely different name, came up with completely unrelated marketing material, and merely advertised "Itanium compatibility," Itanium 2 would've had better chances from its launch.

      --
      "This is Zombo Com, and welcome to you who have come to Zombo Com" - www.zombo.com
    14. Re:Follow the herd! by CptNerd · · Score: 4, Funny

      "Howard Johnson is right!"

      --
      By the taping of my glasses, something geeky this way passes
    15. Re:Follow the herd! by bani · · Score: 1

      Why should he trust intel again? They already blew a huge wad on intel's promises for itanium 1, which turned out to be complete bullshit.

      FWIW itanium 2 is better than itanium 1, but it's *still* a mediocre processor.

    16. Re:Follow the herd! by fermion · · Score: 2, Insightful
      I know some people who were very excited about getting the Itanium. Mostly in CS academic circles. It is a fast processor that could do some things very well.

      But, to recoin a phrase, if you live the MS Windows, then you die by the MS Windows. It is the understanding of the poeple, not me, not those on /., that the itanium was not needed for windows desktop, and only sometimes for server. Perhaps not true, but perhaps MS or the OEM did not push this technology enough. So the Itanium was left to compete in the sever market with little marketing, and failed there.

      I think people who liked Intel bougt the Itanium. Everyone else compared it against other high performance 64 bit chips and choose the best chip for thier application, which apparently was not the Itanium.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    17. Re:Follow the herd! by empaler · · Score: 5, Funny

      Yes yes! We're all individuals!

    18. Re:Follow the herd! by Short+Circuit · · Score: 1

      I didn't realize anyone here liked SCO UNIX.

      (And before someone get's a +3 Funny, Linux doesn't count.)

    19. Re:Follow the herd! by Junior+J.+Junior+III · · Score: 1

      *brain asplodes*

      Brain asplosion. n. When you've got your head stuck up your ass, and fart... while lighting a cigarette.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
    20. Re:Follow the herd! by Hythlodaeus · · Score: 5, Insightful

      Memory was our bottleneck. More ram equals more speed.

      Don't blame Itanium that you picked the wrong chip for your needs. A little back-of-the-envelope calculation could have saved you a lot of money. With your 70 gb database and 2 gb of ram, assuming there wasn't much locality in the lookups you have about a 2.85% chance that your next lookup is already in memory. Up it to 12 gb and you have 17.14% - still not much, so either way your main bottleneck is going to be the bandwidth of your memory system. There was no secret that the first batch of Itaniums used 133 MHz RAM while DDR ram for x86 was up to 266 or maybe even 333 MHz by that time. Itanium's niche has always been floating-point intensive applications, which yours was not.

      --
      For great justice.
    21. Re:Follow the herd! by pla · · Score: 4, Insightful

      Many people here only know what has been said on Slashdot about the Itanium.

      You only need to know three things about the Itanium to pretty much automatically rule it out:

      1) Heat (and the related, power consumption). Not a joke, not a rumor. The Itanium makes the Prescott core look cool and energy-efficient by comparison.

      2) Not designed to run the software in use by 99.5% of the PC market. Great for a custom supercomputer, okay for some servers, complete shit for normal desktop use.

      3) Price. They hope to make it competitive by 2007? How long has it existed now, at 3-10x the price of the highest end x86 CPU? And someone actually needs to ask why it hasn't hit mainstream use yet?


      That about does it for me, anyway. Did I miss something obvious here? I don't see this as a case of the rumor mill damning it, just its own HUGE shortcomings to offset its single good point (namely, good performance for a very limited set of uses).

    22. Re:Follow the herd! by RexDart · · Score: 2, Funny

      I'm not.

      --
      "Yes, Jayne, she's a witch. She's had congress with the beast..."
      "She's in Congress?" - Firefly, "Objects in Space
    23. Re:Follow the herd! by OrangeSpyderMan · · Score: 1

      Don't blame Itanium that you picked the wrong chip for your needs.

      And if you're spending that kind of money without getting a benchmarking machine from the company you're buying it from before you sign - you deserve to get stung :-)

      --
      Try NetBSD... safe,straightforward,useful.
    24. Re:Follow the herd! by Anonymous Coward · · Score: 1, Insightful

      It's funny how so many system 'architects' fail to do these little back-of-the-envelope calculations and end up with poorly performing systems or software.

    25. Re:Follow the herd! by einhverfr · · Score: 1

      Of course.

      The problem is that the Itanium (original) chips were bad. Intel has had a lot of trouble recovering from the bad experiences of the original chips.

      I have never said anything about the Itanium 2 chips. In fact I don't even know anyone who uses them.

      --

      LedgerSMB: Open source Accounting/ERP
    26. Re:Follow the herd! by Jozer99 · · Score: 1

      Maybe you should try running Itanium code on the Itanium. Most OSes for the Itanium include very slow x86 emulation.

    27. Re:Follow the herd! by Anonymous Coward · · Score: 0

      Yet they stay employed and they stay getting paid big bucks. I saw this with contractors a few years back. They know they aren't the most qualified, but they shove their nose right up the boss' ass and make him smile. A real big grin. They never get fired. The IT industry sucks.

    28. Re:Follow the herd! by Anonymous Coward · · Score: 5, Insightful

      I have to concur. System and memory bandwidth are often overlooked when designing a system.

      "It's got 2 xeons and 4 GB of ram! :P"
      It sounds great to management.

      As my colleague noted above, db operations are IO bound. This means you have to get data from point a to point b very quickly, whether from memory or disk.

      To do that job you need high memory and system bus clock speeds, so there is no vaccuum happening at the cpu in.

      There is a point of diminishing returns with adding memory. Sometimes adding too much memory can slow things down, considerably.

      The CAS latency increases as does the latency due to memory management overhead.

      With a db you face the same exact issue that professional audio engineers do. Getting lots of data to the cpu, and back out somewhere.

      Anecdote:
      my buddy, a pro dj, got a dual xeon 2.4 Ghz (I think it was) 4GB memory for producing music. at around 47 audio streams, snap crackle pop. cpu usage was around 10% or so. It was a 12000 dollar mistake on his part.

      I walked in with a $700 amd 64 3200+ (thats 2Ghz) with 1/4 of the memory, one cpu, and I loaded up a project with 134 audio streams and it played like butter.

      Both were running windows xp 32, both were running Steinberg Cubase SX.

      Xeon specs:
      FSB 533
      DDR 133 on 4 1GB sticks

      AMD 64 spec:
      FSB 800
      DDR 400 on 1 1GB stick

      Read the specs for VIA K8T800 chipset and compare it to any Xeon chipset. This time period was a year ago Christmas. Read up on how the memory architecture works for both CPU's.

      Database tests were similar. Just about any IO bound process will produce a similar result. Music, video, db, etc.

      It isn't that the xeon sucks, it's a computations per second centric architecture. Unfortunately for intel, they focused on clock speed when they should have been removing architecture bottlenecks which would allow people to take advantage of all those cycles. The G5 has similar issues but not as bad.

      It's all about the memory and bus architecture... The sad uninformed people say (pinch airflow from nose so you sound geeky) "It's a 64 bit processor, you need a 64 bit OS to take advantage of it, period".

      What they fail to realize is the 64 bit memory and bus architecture happen *below the HAL*. the OS doesn't even see it, let alone need to be 64 bit to take advantage of it. I politely let them flap their gums and went out and bought one anyway, then proved them wrong.

      Computationally = intel, tho that gap is narrowing
      IO = AMD64 or opteron.

      I don't care if you are running windows 95, amd64 will be faster for IO bound stuff, than any 32 bit architecture is capable of even getting close to.

      If you are crunching spreadsheets, word processing or videogaming, *generally*, intel is better, tho that gap is getting smaller. It will likely disappear when 64 bit OS's get apps caught up to them.

      For DB, working with large files, shunting lots of streams around the mobo, AMD 64 *smokes* intel 32 right now, 32 bit apps notwithstanding. There is simply no contest.

      l8,
      AC

    29. Re:Follow the herd! by snwcrash · · Score: 1

      It seems a bit odd to be moving from a commodity hardware, like x86, to a vendor specific environment. Most people have spent a good amount of time and effort moving away from expensive Unix vendor specific hardware (Sparc, PA/Risc etc), why go back to the old way?

      --
      Save a life, sign your organ donor card.
    30. Re:Follow the herd! by Listen+Up · · Score: 1

      Every human being is physically individual and unique. There is no scientific argument against that. What most people are trying to say when they make the statement you made in your post, without thinking, is that in general most humans are not socially or mentally individual. To make the point even more clear for you, most of the human race has a general 'herd mentality'. That is not the same as implying that 'every person is the same' because that is simply not true.

      Also, what ticks some people off is the over-abuse of the false notion that since everyone is individual and unique it must also mean that everyone is equally individual and unique. That is not true.

    31. Re:Follow the herd! by CyricZ · · Score: 1

      As a former SCO system administrator, I'd say that UnixWare and OpenServer/OpenDesktop were some of the best PC UNIX systems I'd used. Until about 1993, that is. Before then they were fantastic. Far better than ESIX or Coherent or XENIX.

      Indeed, it is interesting to consider the history the old SCO had with the Itanium chip. The failed Project Monterey, which involved providing a UNIX implementation targetting the Itanium platform, directly lead to many of the issues involving the new The SCO Group today.

      --
      Cyric Zndovzny at your service.
    32. Re:Follow the herd! by Anonymous Coward · · Score: 0

      Memory was our bottleneck. More ram equals more speed. So we spent BIG bucks and bought a quad Itanium with 12 or 16 gigs of memory (I forget exactly how much it had).

      The Itanium was slower than a dual X86 with 2 gigs of memory! And not just a little slower. We spent weeks trying to get the database optimized.


      I don't doubt your experience... but I also recognize that this would only be true if the RAM really weren't the factor that you claim it was.

      If a DB is trashing on more than 2GB of DATA then a system with more RAM is going to blow away no matter how slow the CPU.

      RAM is so much faster than diks...

      To get the point: it sounds to me like your database was CPU bound more than RAM bound...

    33. Re:Follow the herd! by Short+Circuit · · Score: 1

      I often wish I was old enough to have experienced those days. I feel like I missed out on an exciting period.

    34. Re:Follow the herd! by kublikhan · · Score: 1

      That begs the question, why hasn't anyone used one?

    35. Re:Follow the herd! by MS-06FZ · · Score: 1

      (Ssh!)

      --
      ---GEC
      I'm but the humble pupil, seeking to snatch the scratchbuilt pebble from the master's fully articulated hand
    36. Re:Follow the herd! by bwoodard · · Score: 1

      It isn't just follow the herd. There are a number of reasons why developers really don't like itanium.

      1) they are very very very sensitive to compiler optimizations to get performance. Tuning your app to run quickly on an itanium is more challenging than it is on other arches. One thing that isn't shown on the top500 numbers is the fact that linpack is well optimized for ia64 and people compete for the best linpack scores. Being able to get real codes to perform as well as linpack is very difficult.

      2) the ia64 code is more difficult to debug. I can't really pin this one down. Like porting to other architectures, you uncover bugs when going to ia64. However, the way that the register stack works and the way things execute seem to make it just a little more frustrating to debug problems on ia64.

      3) Function pointers are weird. They are pointers to a structure that includes both a pointer to the function and a pointer to its register stack. This makes some things rather difficult. It is different than what you expect.

      4) The documentation, while thorough and complete is daunting. There is a lot more to the ia64 architecture than just the processor and the chipset. It seems like Intel is sort of backporting some of that to the ia32. So moving to the ia64 wasn't just porting your app, it included retraining your staff to one extent or another. Things work differently in the ia64 world.

    37. Re:Follow the herd! by Anonymous Coward · · Score: 0

      I'm sure there are even more back-of-the-envelope calculations which caused more problems than they solved.

    38. Re:Follow the herd! by PReDiToR · · Score: 1

      "CptNerd Johnson is right about Howard Johnson being right!"

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    39. Re:Follow the herd! by codeguy007 · · Score: 2, Interesting

      Don't forget that an IBM employee called Itanium a science project when IBM dropped there line of Itaniums.

      The problem is and will remain that you don't get enough performance for what you pay for from Itanium.

      When I can build a Athlon64 X2 cluster for under $500,000 that can place somewhere around 150 on the top 500 list. It's hard for itanium to compete pricewise.

    40. Re:Follow the herd! by mholt108 · · Score: 1

      rrrreevrenn!

    41. Re:Follow the herd! by Anonymous Coward · · Score: 0

      Your anecdote probably has little to do with the current processor.

      Nice little canard -- slipping in the accusation of "anecdote" to disparage the value of the information, then compounding the canard by adding the weasel word "probably" which really only diminishes the value of your own criticism.

      Was your mother so negligent in your upbringing that she never taught you about "Fool me once -- shame on you; fool me twice -- shame on me"?

    42. Re:Follow the herd! by Grishnakh · · Score: 1

      Was your mother so negligent in your upbringing that she never taught you about "Fool me once -- shame on you; fool me twice -- shame on me"?

      Exactly. If I buy a Chevy and drive it around for a while, and it turns out to be a piece of crap, why would I believe them when they tell me their next generation of cars is great? I'm going to buy a car from someone else.

      Customer loyalty is extremely important to a company's health, and the converse is true as well (and maybe more important): making your customers hate you is very bad for business. After someone's been screwed over by a company, it takes a very long time for them to decide their products may have improved and try them again.

    43. Re:Follow the herd! by CyricZ · · Score: 1

      Indeed, it was quite exciting. But unaccessible to the average PC user. The software itself cost quite a bit. That is why only admins were usually able to experience such things firsthand.

      --
      Cyric Zndovzny at your service.
    44. Re:Follow the herd! by sharkey · · Score: 1
      *brain asplodes*

      Wow. Ricky Ricardo reads Slashdot.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    45. Re:Follow the herd! by Anonymous Coward · · Score: 0

      Seriously, who's waiting on the Hurd anyway? Just use Linux and get over it. Oh wait...

    46. Re:Follow the herd! by Guppy06 · · Score: 1

      "They've never used one. "

      Give me one at a reasonable price and with the ability to use my current hardware and software with the chip, and I'll use it. There's no reason for me to "be fair" and try using it when I can't use it. It is, for my intents and purposes, useless.

    47. Re:Follow the herd! by Anonymous Coward · · Score: 0

      sco rulezzzzzzzzzzzz

    48. Re:Follow the herd! by Guppy06 · · Score: 1

      "Your anecdote probably has little to do with the current processor."

      "Fool me once, shame on you..."

    49. Re:Follow the herd! by Anonymous Coward · · Score: 0

      1) Heat (and the related, power consumption). Not a joke, not a rumor. The Itanium makes the Prescott core look cool and energy-efficient by comparison.

      The last time I looked, Itanium was more efficient than *PENTIUM M*, let alone mobile athlon(64)s. You can't fucking compare the energy efficiency of chips made with different size transistors, fuckwit.

      So before you fucking say any more fucking stupid shit, how about you check out the power consumption of an Itanium processor made in a 90 nanometer process, just like the Pentium M and mobile Athlon 64:

      http://en.wikipedia.org/wiki/Image:Montecito_power _breakdown.JPG

      yes - that's ~42.5 watts per core, but remember power consumption scales as roughly frequency to the power of 2.5 (some of this due to decreasing switching power, most of this due to the lower voltage you can use at decreased frequency)

      Once again, your argument is total, utter bullshit. Itanium (Montecito) is actually the most power efficient processor I am aware of with performance better than a Pentium 3 1000. There are more efficient processors out there but they are VERY slow.

    50. Re:Follow the herd! by Anonymous Coward · · Score: 0

      You only need to know three things about the Alpha to pretty much automatically rule it out:

      1) Heat (and the related, power consumption). Not a joke, not a rumor. The Alpha makes the Pentium Pro core look cool and energy-efficient by comparison.

      2) Not designed to run the software in use by 99.5% of the PC market. Great for a custom supercomputer, okay for some servers, complete shit for normal desktop use.

      3) Price. They hope to make it competitive by 2000? How long has it existed now, at 3-10x the price of the highest end x86 CPU? And someone actually needs to ask why it hasn't hit mainstream use yet?

    51. Re:Follow the herd! by Trejkaz · · Score: 1

      I guess most people aren't so keen to go to a sequel for a movie that sucked.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    52. Re:Follow the herd! by Anonymous Coward · · Score: 0

      PReDiToR Johnson is right about CptNerd Johnson being right about Howard Johnson being right!

    53. Re:Follow the herd! by scottgfx · · Score: 1

      Mongo goes where Intel goes!

      --
      It's mandatory to wash your hands before returning to the land of Dairy Queen.
    54. Re:Follow the herd! by stor · · Score: 1

      Asploding ones are even more so.

      Not at Homestar Runner

      Sheesh, get with the program, you.. you.. nonconformist, you!

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
    55. Re:Follow the herd! by wooger · · Score: 1

      "videogaming, *generally*, intel is better,"

      Thats bullshit, AMD smokes Intel for gaming and has done for a few years.

    56. Re:Follow the herd! by Anonymous Coward · · Score: 0

      No wonder the Alpha died!

    57. Re:Follow the herd! by pla · · Score: 1

      The last time I looked, Itanium was more efficient than *PENTIUM M*

      Ahahahahahaa... Good one. You guys crack me up, sometimes. Intel's own numbers shows the low voltage (aka "piss-poor performance") version as still drawing 62W. The last "real" version, the Madison core, draws an impressive 130W. Ah, but you meant to refer to the dual core one, correct? Well now, that changes everything! To realize the draw you gave (not quite half of 99W, but I'll let that slide for now), should I cut one in half with a hacksaw, or just smash a bit of it up with a really small hammer?



      more efficient than *PENTIUM M*, let alone mobile athlon(64)s.

      The 1MB cache LV mobile Athlon 64 has a TDP of 19W.
      The ULV Pentium M-753 (Dothan core) draws... 5W. Five. Stomp stomp stomp... stomp... ... stomp.

      5W<42.5W. 19W<42.5W. 42.5W<(99/2)W. 99W<130W. Please play again.



      You can't fucking compare the energy efficiency of chips made with different size transistors, fuckwit.

      Yes, actually, you can. I chose to measure it in terms of "Slashdot trolls I have to put up with per watt".

      You could also use a more meaningful number, such as megaflops per watt, or even FPS in Doom 3 per watt. But only considering the per-gate waste doesn't tell you anything particularly meaningful - Doing so strikes me as similar to trying to compare the brightness of a 100W incandescent light-bulb to an LCD monitor based on the worst-case draw of a single pixel.

      How many gates does it have total, how well does it make use of them, and does it keep idle sections of the chip active also matters rather a lot. Using half as much power per state change doesn't matter if it takes 10x as many transistors to get the same job done.

    58. Re:Follow the herd! by Nathan+Robertson · · Score: 1

      I've read that most of the performance gain from amd64 comes from the extra general purpose registers it has available to it in 64 bit mode. Hence, I'd like to see the evidence backing your claim that amd64 is faster than anything Intel on a 32 bit OS. Xeon is generally one generation behind on chipsets from the P4 for some reason. I guess they need to add features required by Xeon customers, and that takes time. Maybe?? I've found Java apps to be an exception. The amd64 JVM from Sun is much slower and less reliable than the 32 bit one. So the amd64 on my desk runs a fair bit slower than the dual xeon we have in production. YMMV - but the next Java app server I purchase in a couple of months will run a 32 bit copy of SLES regardless of which CPU it has. It'll probably be Xeon because I quite like Dell's 24x7x4hr support, and they don't to AMD.

    59. Re:Follow the herd! by Anonymous Coward · · Score: 0

      The ULV Pentium M-753 (Dothan core) draws... 5W. Five. Stomp stomp stomp...

      Did you even read what I wrote about power scaling? How do you think the performance of a Montecito core (dual threaded Itanium 2 with split/enlarged L2 caches, larger L3, and a faster bus) running at full speed would compare to a Pentium M 753 running at full speed? The Pentium M 753, FYI, is a 1.2GHz Dothan core. The Montecito at ~45W is a ~2.1GHz Itanium 2 core (with a number of improvements, e.g. TMT.)

      Here's a fun question for you: how much power do you think the Dothan core would consume to match the performance of a single Montecito core? Pentium Ms overclock well, right? remember: performance scales as frequency^2.5 given that you'll have to increase voltge

      There are numerous reports of people on x86-secret.com forums getting thir PMs to run at 2.5 or 2.6GHz, but only at 1.55V for a total dissipation of around 50W. That's up in Montecito territory. Now let me ask you: which do you think is the faster processor? A 2.6GHz Pentium M or a 2.1 GHz Montecito?

      In case the thought hadn't crossed your obviously deficient mind, Montecito can indeed take advantage of the ^2.5 scaling and it is in fact the first processor ever made, by anyone, ever, to do so on the fly! It's called Foxton - look it up. Let me just say that a Montecito can and will run happily at low clock speeds drawing tiny amounts of power (again, remember the scaling.)

      You could also use a more meaningful number, such as megaflops per watt

      That sounds great but is actually fucking useless, because all you have to do to get bette megaflops per watt is simply run at a lower voltage and frequency. You get fewer megaflops - linear in frequency (or damn close to it) - but you get MUCH lower power draw, and thus a MUCH higher MFLOPS/watt rate.

      What would be sane is to set some target level of performance, and then compare processors efficiencies at that level. Given that Montecito is an in order processor (low power), with lots of cache (expensive, but still low power), and will be the first microprocessor ever made to vary its voltage and frequency continuously at runtime (at a frequency of >1kHz), for most performance levels (i.e. anything above "hand calculator") you'll find Montecito will win out.

      Anyway, I'll be happy if tell me what you think the power draw of a Montecito chip at 1.0GHz will be, and how that processor might compare in terms of performance with a Pentium M 753. (I already know the figure, and if you know what ISSCC stands for, you can too!) One core running or two - you choose. I'll get you started: at 1.7GHz (so, still faster than today's fastest shipping Itanium 2 processors, even forgetting all the microarchitectural improvements), Montecito's power draw (the whole chip, both cores running) is 57W.

    60. Re:Follow the herd! by BoneOfconTroll · · Score: 1

      (Ssh!)

      --
      I don't want to sell you death sticks.
  8. Itanium2 by Anonymous Coward · · Score: 5, Interesting

    I had to study the chip in one of my EE class. The technology in it is really really impressive. I love the memory architecture provisions!

    1. Re:Itanium2 by markhahn · · Score: 2, Insightful
      yeah, but when it comes to buying machines, who the heck cares about fancy design unless it gives a clear, measurable performance boost on real codes? for instance, in SPEC FP, the It2 looks pretty impressive, until you realize that:
      • you lose most of the speed advantage if you ignore those codes whose working set is entirely in-cache on the It2 (and not so on other processors.)
      • Intel's compilers have been tuned extensively to make SPEC FP look good, so these numbers are unrealistic upper bounds for real user code.
    2. Re:Itanium2 by EvilTwinSkippy · · Score: 4, Funny
      If it was anything like my EE class (1998 era) they were also handing out Itanium architecture manuals, Itanium platform reference guides, a book about Processor Architecture written by a guy from Intel, taught by a professor who drank out of an "intel" mug, and the cute female grad student had an "intel inside" t-shirt on with an arrow pointing down.

      Yeah, I had that class.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    3. Re:Itanium2 by Anonymous Coward · · Score: 0

      wait. did you get the grad student's phone#?

    4. Re:Itanium2 by joib · · Score: 4, Insightful

      Well, after you take the "Compilers" course maybe your love for IA-64 will have, uh, dimished a bit.

      The VLIW architecture is beautiful in many ways, but creating a compiler that creates fast code for an in-order VLIW processor is a seriously difficult undertaking.

    5. Re:Itanium2 by Marc2k · · Score: 1

      Yeah, I read an article on either Tomshardware or Anandtech at least a year and a half ago, comparing the Opteron and the Itanium, and I was thoroughly impressed with the technology surrounding the Itanium, straight down to the IA64 instruction set's design.

      --
      --- What
    6. Re:Itanium2 by jandrese · · Score: 5, Funny

      ...cute female EE grad student...

      I recognize all of the words, but it still doesn't make sense.

      --

      I read the internet for the articles.
    7. Re:Itanium2 by dhasenan · · Score: 1

      Are those compiler optimizations especially difficult to reproduce? If Intel were reasonable, they'd add a flag to the Intel C compiler that enables Itanium2 optimizations all in one go. More reasonable, and they'd share some of the information with the GCC developers.

    8. Re:Itanium2 by bani · · Score: 1

      itanium is a very pretty architecture, but "pretty" rarely means performance.

    9. Re:Itanium2 by BasharTeg · · Score: 0, Troll

      Yes, clearly making compilers work hard and have complex optimization code to generate high performance output is asking too much of them.

      You must be a fan of gcc.

    10. Re:Itanium2 by ma_luen · · Score: 1

      I am not extremely familiar with gcc's support for the Itanium. However, to get good performance out of the chip the compiler has to do a lot of extra work in the scheduler (since the Itanium is an in order processor) and use a lot of special features in the chip that do predicated execution, boosting, etc.

      All of these things require substantial changes to large portions of the compiler. This means that the gcc people would have to do a lot of work for a small percentage of users and it goes against the goal of flexibility that gcc has.

      Mark

    11. Re:Itanium2 by Anonymous Coward · · Score: 0

      I'm guessing that our moderators gave this guy a score of 5 and the previous a score of 4 because the latter said something *against* Intel...

      even though they commented on exactly the same level.

    12. Re:Itanium2 by Anonymous Coward · · Score: 0

      Stop posting this crap to Slashdot.

      Oh, and take a compilers class sometime or play with one in your spare time.

    13. Re:Itanium2 by thsths · · Score: 1

      > The VLIW architecture is beautiful in many ways,

      That is true. It is similar to RISC, but it makes more efficient use of execution units and code size. However, in one aspect VLIW is even worth than RISC: the predicted efficiency is only realised if the ISA matches the CPU architecture. Otherwise, a translation layer is required, and the main advantage against CISC evaporates.

      Sun had big troubles with than on SPARC. The ISA worked well for the SPARC processors in the early nineties, but it is difficult to execute efficiently on a modern CPU.

      I am sure that Intel ran into that problem when designing new revisions of the Itanium, and eventually it is doomed. The marked place just doesn't permit to change the ISA with every CPU architecture, binary compatibility is to important for that.

      So: ISA does not matter for efficiency, unless you want to recompile your apps for every new CPU. And most people don't want to do that for a meager performance advantage.

    14. Re:Itanium2 by Urusai · · Score: 2, Interesting

      All those academic losers in CS departments across the country can't be bothered to write a compiler to prove their pet theories? Gimme a break. Sure it may be hard, but doing hard stuff is why these big-brained Einsteins are making the big bucks. I guess expecting results from domain experts is too much to ask nowadays; much better to spend your time recompiling Linux on esoteric architectures and writing papers on what pivot is best for Quicksort.

    15. Re:Itanium2 by Anonymous Coward · · Score: 1, Insightful

      One must bear in mind that "cute" is a relativistic function. As n (female population) decreases, the entire attractiveness bell curve moves a few notches to their advantage.

    16. Re:Itanium2 by Anonymous Coward · · Score: 1, Interesting

      One of the biggest problems with any in-order microarchitecture is stalling due to L1 cache misses. What does an in-order machine do when a memory operation misses in L1 and a dependent operation is next in line? Sits there. An OOO machine can continue to do useful work on non-dependent instructions in its instruction window.

      In some instances, an advanced Itanium/EPIC compiler can play around with the memory latencies and try to hide them - for example, schedule a bunch of non-dependent instructions right after a long-latency load from memory. This requires a lot of program and pointer analysis, and is doable only sometimes (things like heavy array-based computations, for example).

      So, on real-world programs that may have varied memory access patterns, the Itanium family isn't going to do very well, but on many of the scientific and floating-point benchmarks (regular memory access patterns that the compiler can understand), it flies.

      Granted, this memory latency thing is becoming a problem even on OOO microarchitectures, because there's only so much the processor can do before it has to stall waiting for the data to come back from memory. Check out a few papers on runahead execution, which helps to mitigate this problem on either OOO or in-order microarchitectures. I wouldn't be surprised to see the next major incarnation of the Pentium or Athlon line have this feature.

    17. Re:Itanium2 by Anonymous Coward · · Score: 0

      The VLIW architecture is beautiful in many ways, but creating a compiler that creates fast code for an in-order VLIW processor is a seriously difficult undertaking.

      Couldn't agree more. The basic idea of the Itanium (or Merced, back then) is to put most of the "intelligence" into the compiler: like VLIW and especially EPIC - explicit parallel instruction computing. The very idea is so 1990!

      Now that we've got hot-spot optimizers, JIT (just-in-time) compilers, real good branch prediction, out-of-order execution, and all of this can be (and is being) done in silicon, EPIC just doesn't cut it anymore.

      I pity the poor bastards to manually optimize their code for four pipelines. Yukk!

  9. Physics. by Anonymous Coward · · Score: 0

    What we need for gaming is a Physics chip more than anything else right now, not some general purpose crap.

    Its the next big thing, not a bigger horse, rather a few horses and some that specalize in Phyics, Multiple cores, and Vector processing for graphics and DSP for Audio.

    Multi core GFX chips, Multi core CPUs, and Physics processing. Offload that general processor.

    Its easier to harness the power of many horses than grow one 100 times as powerful.

    1. Re:Physics. by kfg · · Score: 5, Insightful

      Its easier to harness the power of many horses than grow one 100 times as powerful.

      No, it is easier to grow 100 horses than one horse 100 times as powerful, and yet we've gone ahead and done it anyway, because, in point of fact, it is easier to harness and control one horse than 100.

      See The Wheel of Reincarnation.

      KFG

    2. Re:Physics. by Anonymous Coward · · Score: 0


      Its easier to harness the power of many horses than grow one 100 times as powerful.

      No, it is easier to grow 100 horses than one horse 100 times as powerful...

      Are we talking about Itaniums or horses now?

    3. Re:Physics. by kfg · · Score: 1

      Are we talking about Itaniums or horses now?

      1960's BRM engines.

      KFG

    4. Re:Physics. by Jeremy+Erwin · · Score: 1

      Physics processors? GPUs? What if your application isn't centered around physics, or graphics?

      Yes, yes, one can program a GPU/VPU to perform general purpose calculations. And one might be able to pervert the Physics processor to do more than calculate trajectories of bullets. But the further one ventures beyond the conceptions of the designers, the slower the end result.

    5. Re:Physics. by chrismcdirty · · Score: 1

      See The Wheel of Reincarnation.

      I hope I get Keira Knightley's underwear!

      --
      It's like sex, except I'm having it!
    6. Re:Physics. by Anonymous Coward · · Score: 0

      Hehe, no mod points but what an excellent post. I was transferred temporarily to higher plane and could hear trumpets, timbrals and the sound of a one handed man clapping. Thank you sir.

  10. No x86 Compat is the Achilles' Heel by Thornkin · · Score: 5, Insightful

    I think the big problem is that it cannot run x86 software very quickly. Most software that people want to run in the mass market is precompiled, binary x86 software. That stuff just does not run well on the Itanic. That, combined with the fact that the mass market still doesn't really benefit from a 64-bit address space means that the Itanium was a more expensive, slower processor. It's no wonder that it didn't sell.
    Early versions also had problems with heat. Where I work we have some Itanic workstations and in the winter, if we were chilly, we literally turned them on to help warm up our offices.

    1. Re:No x86 Compat is the Achilles' Heel by chrismcdirty · · Score: 1

      Have you ever disassembled them? They have at least 2 5-inch diameter fans, along with a lot of styrofoam in order to pipe heat to the correct locations. And stickered all over the styrofoam was warnings saying that it is functional to the design and to remove it would be certain death for the machine (not in those words exactly).

      --
      It's like sex, except I'm having it!
    2. Re:No x86 Compat is the Achilles' Heel by Anonymous Coward · · Score: 0
      It was overpriced. A friend of mine that develops this small finance application, that needs CPU power, considered buying one. But after HP said they could not go under $12000 for a workstation with 4GB RAM he decided to drop the idea.
      His customers were also sceptical about the price on Itanium workstations. At that time they bought Xeon workstations with lots of RAM and two LCDs for around $5000. Itaniuns would be more like $15000 after discounts. Intels idea that it might be a market segment (enterprise, finance, energy, research etc.) that is willing to pay extra for better performance is fine in teory, but it's hard to gain enough momentum in the real world for the market to "take off". Everyone is sitting on the fence waiting for someone to take the first step and then take the risk of failure.

    3. Re:No x86 Compat is the Achilles' Heel by hackstraw · · Score: 4, Interesting

      I think the big problem is that it cannot run x86 software very quickly.

      Yeah, that is why semi trailers don't get respect like Dodge Neons. They use diesel fuel instead of unleaded!

      My point is that if your buying a 64bit system that is fast in order to run your old 32bit programs slowly. Wrong tool for the job.

      I've got 65 Itanium processors downstairs. They are fast and reliable for high memory bandwidth floating point calculations, which is what we use them for. They may be a disappointment with running IE or Outlook, but for crunching numbers they are great. I have yet to of tried an Opteron but will in the next couple of weeks. From what I understand those too have become great at high memory bandwidth number crunching, but I'll wait for the numbers vs marketing speak. Now, Itaniums do suck in the power consumption and heat dissipation department.

      Itaniums get such a bad rep here on Slashdot because its cool to do so. Itaniums are made by the "big guy", Intel. If they were made by AMD they would not get the same rap as they do.

      The other big thing against the Itaniums is market need. A generic x86 that you can throw in the trash and replace for about $1k if there are any problems are sufficient for 99% of the servers out there. If not even preferred. Now, what other market would want a fast 64bit architecture with high memory bandwidth -- databases. Sun and Oracle fill this void. Well except for the fast and high memory bandwidth part, but Oracle+Sun is a proven combination with years of experience. Solaris does not run on Itaniums. Linux does (flawlessly), but even Oracle+Linux is not that widely adopted. I have no clue about Windows state on an Itanium. I see no real use to run Windows on an Itanium, but someone else might, but I doubt its very common.

      Although Intel has some more to go with the low-voltage Itaniums because they are capped at 1.3GHz, but they are working on that. Also, Intel has dropped the price of these guys considerably. This too was an issue with Itaniums, but they have dropped by about 1/2 the price over the years.

      IMHO, Intel should continue on the power management issues and price and market these chips more for number crunching. Their performance on the top500 site is impressive, but even if all of the top 500 computers used 4,000 Itanium processors each, that would only be 2,000,000 processors total, and a super computer that size is not purchased very frequently.

    4. Re:No x86 Compat is the Achilles' Heel by QuickFox · · Score: 1

      I think the big problem is that it cannot run x86 software very quickly.

      Why is the standard solution to this problem to let the processor interpret x86 code? Why not first let a JIT recompiler read through the x86 code and recompile it as native Itanium code? This could be fully automatic and transparent, just like a JVM-to-native JIT compilation.

      That should be very much faster than interpreting x86 code all through the program execution!

      Is there some fundamental problem that makes this impossible?

      --

      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    5. Re:No x86 Compat is the Achilles' Heel by Foolomon · · Score: 1
      Maybe they should have combined the Itanic with the Transmeta offering. The result?

      A Transitanic Chip.

    6. Re:No x86 Compat is the Achilles' Heel by MynockGuano · · Score: 1

      Unfortunately, finding 64-bit commercial programs for the architecture is nigh-impossible, so you almost have to be able to run a lot of 32-bit code. The problem lies in the fact that ALL of your software has to be compatible, and that's not even close to feasable currently.

      Some problems we run into with program support for our Itanium2-driven Altixes (Altices? Altixen??):
      PTC Products System Requirements
      Alias Maya 64-bit Requirements

    7. Re:No x86 Compat is the Achilles' Heel by bani · · Score: 4, Insightful

      Itaniums get such a bad rep here on Slashdot because its cool to do so. Itaniums are made by the "big guy", Intel. If they were made by AMD they would not get the same rap as they do.

      bullshit. itaniums get a bad rep on slashdot for any number of reasons, and they cannot all be distilled down to "because it's hip and trendy to bash itanium".

      slashdot would still be bashing itanium if it were from amd.

      few people like paying $1000+ for a cpu alone, for example.

      itanium is a niche processor filling a tiny tiny tiny market. and it is already hitting scaling issues.

      itanium also has yet to deliver on most of its performance promises. just about the only one it's delivered on so far is memory bandwidth :-)

      intel gambled itanium's future on its dependency of a number of risky and unproven technologies (eg VLIW). in order for itanium to succeed, ALL of these technologies had to succeed. instead what happened is virtually NONE of them did.

      it's quite telling when a lot of the intel engineers and scientists involved with itanium are calling it a huge mistake. the p4 guys aren't impressed either :-)

      itanium is doomed longterm. most of intel's itanium partners have long since bailed on the architecture, most projects for itanium have been killed off (including windows), which guarantees itanium has no longterm future.

      some lessons from itanium may be rolled into other intel mainstream products, but as a product itself itanium's days are numbered. itanium has been a huge black hole sucking billions of r&d from intel while amd has been constantly chipping away at intel's market share with x86_64. itanium has never turned a profit, in over a decade of development on the damned thing. it's only a matter of time before stockholders demand itanium be hauled out to the barn and given both barrels.

      most people who have studied itanium closely conclude itanium is an r&d project that should have remained in the labs as pure r&d, and never turned into a product.

    8. Re:No x86 Compat is the Achilles' Heel by bbbl67 · · Score: 1
      When Intel first announced IA-64 around 1994, everybody assumed that it was the successor the x86 architecture, which means that it has to also be able to run x86 binaries. That also means being able to boot up into an x86 operating system and run it natively, and then run all of that OS's applications, etc. Basically it should've been able to let us keep running vanilla x86 seamlessly until we were ready for more powerful stuff. If we wanted to go to another architecture, then Power, Sparc, MIPS, and Alpha already existed at that time. Since nobody on x86 wanted to migrate to any of those other architectures, why would they want to migrate to Itanium?

      Turned out that that promise was kept by the AMD64 architecture, which is really what people on x86 wanted to go towards.

    9. Re:No x86 Compat is the Achilles' Heel by drgonzo59 · · Score: 1
      I think it is "cool" to bach Itanic on Slashdot not just because it is from the "big guy" but because most people here know the real value and the real performance numbers of the hardware. Most people simply own an AMD because it offers better performance at a lower price - as simple as that. In my oppinion AMD already beat Intel in the 64bit consumer processor market and also is beating it in the double-core offerings (try buying a double core Intel processor off pricewatch for the price of a double core offering from AMD with the better performance). And geeks on Slashdot will "side" with the chipmaker whose chips they have bought .

      In other words I don't really see AMD as the "small guy" that needs support and pity. I just root for the brand I chose because I did the research and spent my money well. You root for the guy that you chose and spent your (your company's) money on.

      Tomorrow if Intel comes on top with a better processor for me, I will go and buy an Intel product, or VIA or whatever gets my job done faster and cheaper.

    10. Re:No x86 Compat is the Achilles' Heel by QuickFox · · Score: 1

      The word "of" is not a verb, you stupid illiterate moron.

      Now you of gone offended him you insensiti clod!

      --

      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
    11. Re:No x86 Compat is the Achilles' Heel by qengho · · Score: 1


      Now you of gone offended him you insensiti clod!

      To be precise: "Now you of done gone and offended him you insensitive clod!"

    12. Re:No x86 Compat is the Achilles' Heel by MynockGuano · · Score: 1
      Threw together some raytracing (mental ray) benchmarks awhile ago. License was for two processors; the first two machines had plenty more than that, the last one (my PC) only one. Since all the ia64 experts are in here, thought I might see if any of you can explain these:
      SGI Onyx3900 MIPS R16000

      Wall: 00:04:36.58
      CPU : 00:09:10.00
      Load: 198.8%

      SGI Altix3700 ia64 Itanium2

      Wall: 00:08:30.92
      CPU : 00:00:18.51
      Load: 3%

      Pentium 4 2.0GHz

      Wall: 00:05:41.90
      CPU : 00:05:04.34
      Load: 89% (was using the computer for web browsing, etc. simultaneously)
      I know there's (intentionally) woefully little background info here, but the discrepancies would seem to indicate something really screwed up. Is the problem obvious to anyone here? Configuration is more or less stock.
    13. Re:No x86 Compat is the Achilles' Heel by corngrower · · Score: 1

      When Intel first announced IA-64 they were quite up front about stating it would not be x86 compatible and that they wanted to rid themselves of a lot of x86 baggage with this architecture. Anyone who assumed that it would be x86 compatible must not have been paying attention.

    14. Re:No x86 Compat is the Achilles' Heel by poot_rootbeer · · Score: 1

      My point is that if your [sic] buying a 64bit system that is fast in order to run your old 32bit programs slowly [sic]. Wrong tool for the job.

      You've just answered the question put forth.

      Why doesn't the Itanium get respect? Because if you want to run your existing 32bit programs, it is the wrong tool for the job.

    15. Re:No x86 Compat is the Achilles' Heel by Frumious+Wombat · · Score: 2, Informative

      It's not popular because previous generations were Hot, Expensive, and Hard to Program. Adoption was slowed mainly by #2, as it was a significant investment for many research groups to even put one on the floor for testing purposes. The Hard to Program meant that you had wonky versions of Linux, or HP-UX with new compilers, as your OS options, which just increased the resistance.

      I ran an Itanium-2 cluster (and had briefly an Itanium-1 loaner) and if the compilers were stable, the first generation easily outpaced the UltraSparc-III systems of the era, and the Itanium-2s kept pace or outpaced the Alphas. However, their power-draw was unbelievable, you had to rebuild the GNU toolchain from RedHat stock, then install whatever that week's version of Intel's C/Fortran compiler was, and on any code that was integer bound, they were barely faster than the late Xeons.

      Ah, but for floating point, nothing touched them, except possibly the late Power systems that we couldn't afford. A clean 64-bit architecture, and four floats per clock cycle, meant that for a certain class of problems, there were the cost-effective solution; US-III prices, and twice (at least) the performance. They were even pretty easy to port our codes to, as their pure 64-bit environment (8-byte Integers and pointers), meant that generally modifications to run on Alphas and Crays would run on the Itaniums as well. We would have preferred a next generation of Alpha, but the Itaniums work quite well for what they do.

      Discouragingly, now for most (but not all) of the simulations I do, AMD-64 or even EM64T systems are cost-effective, and just as fast. With this new price reduction, I may have to look into adding IA-64s back into the mix, though they're going to have trouble competing against IBM's linux-based Power-5 systems, which offer similar prices, and a more well-known and supported architecture.

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    16. Re:No x86 Compat is the Achilles' Heel by Anonymous Coward · · Score: 0

      in the winter, if we were chilly, we literally turned them on to help warm up our offices.

      We can figure it out for ourselves that you weren't turning them on metaphorically.

    17. Re:No x86 Compat is the Achilles' Heel by default+luser · · Score: 2, Informative

      In addition, real-world performance sucks without tons of cache and memory bandwidth. In fact, the original Itanium's entire bus and cache subsystem were redesigned for the release of Itanium 2, doubling the bus width, increasing the L2 cache size and tweaking the latency on the L3.

      No surprise, the Itanium 2 performs much better than the original Itanium, but it's name was alreay soiled by the mediocre preformance of the original.

      In addition, all that cache and high-performance bus architecture means the Itanium can't be priced competitively with anything, due to the hulking die size. I2 NEEDS a minimum of 6MB L3 cache to shine, and 9MB doesn't hurt. Note that the "affordable" I2 chips have a paltry 1MB L2 cache, and perform like crap.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    18. Re:No x86 Compat is the Achilles' Heel by HFXPro · · Score: 1

      Cause it wouldn't be able to do a good job at it. Some of the instructions in x86 rely on the way that instruction executes. Breaking the instruction into lots of smaller instructions to accomplish the same task may result in horrible performance even on new architecture. Secondly, JIT code is not as fast as everyone will have you believe. It still requires a lot of management to make sure things such as the code has not been modified leading to yet another runtime. Most JIT's also only compile functions which are being used heavily.

      --
      Reserved Word.
    19. Re:No x86 Compat is the Achilles' Heel by DSP_Geek · · Score: 1

      Itanium was a collaboration between Intel and HP, who had a workstation architecture (PA, I think it was called) running HP/UX, so as such x86 compatibility wasn't high on the agenda. I'll note that HP is one of the very few companies still shipping Itanium servers; they'd might as well since they sacrificed two outstanding architectures (remember Alpha?) to Intel.

    20. Re:No x86 Compat is the Achilles' Heel by gothamboy · · Score: 1

      Early Itaniums produced so much heat that replacing Sun, HP or other Intel Servers with Itaniums would strain a data centers AC by dramatically increasing the heat produced (and associated electricity needed). Many people at the time just didn't see the need to play with them and got their early impressions.

    21. Re:No x86 Compat is the Achilles' Heel by Anonymous Coward · · Score: 0

      Your post is utter, utter bullshit. Congratulations on the 4, Insightful - it's certainly not informative. Almost everything you say is incorrect, pure speculation, or irrelevant:

      slashdot would still be bashing itanium if it were from amd.

      this is speculation.

      few people like paying $1000+ for a cpu alone, for example.

      this is irrelevant. "few people" could mean 20,000 per year buying 10 CPUs each (200,000 is roughly how many Itanium 2 CPUs have been purchased in the last 12 months, and most people buying Itanium buy 8-way systems or higher. 2-way Itanium2s are quite rare and nobody _makes_ a 1-way Itanium system any more) for around $400million in annual sales, not too shabby for a "nice product" (the average Itanium CPU sale price is closer to $2,000

      itanium is a niche processor filling a tiny tiny tiny market.

      This is bullshit. $400million in annual CPU sales corresponds to way, way over $1billion annually in system sales. That is a niche market, yes. "tiny, tiny, tiny" it is not.

      and it is already hitting scaling issues.

      I suppose you're referring to Itanium 2, which is now a 4 year old product? That will be refreshed in ~5 months, where the next 4 years of scaling will be set up.

      itanium also has yet to deliver on most of its performance promises.

      This is total bullshit. Itanium's big performance promise was that by offloading complexity from the chip itself to software such as the compiler or virtual machine, you can gain improved efficiency as more of the CPU core can be dedicated to logic that does real, computational work. They delivered.

      it's quite telling when a lot of the intel engineers and scientists involved with itanium are calling it a huge mistake. the p4 guys aren't impressed either :-)

      Can you name even one Intel engineer who called it a huge mistake? You're just making up bullshit now. I suppose you might have been thinking of Bob Colwell but he certainly didn't say it was a huge mistake.

      From this point onwards actually, the rest of your post is just bullshit you appear to have made up because it sits well with whatever the hell prejudice you have - I guess that's why this whole article got posted in the first place.

      Anyway, you might want to try the "FreeBSD is dying" crowd, they are a bit better established than the "Itanium is dying" mob which is a bit younger (though over the years I'm sure it will grow to be every bit as respectable a trolling subcommunity! ;) )

    22. Re:No x86 Compat is the Achilles' Heel by Anonymous Coward · · Score: 1, Insightful
      " I have no clue about Windows state on an Itanium."

      It all comes down to the fact that an optimized compiler for linux came out of Intel. Microsoft, wanting to dominate the high end big data base market, got really pissed at Intel. The fact that Linux and Oracle optimize well on the Itanium is no secret. The fact that NT optimizations for the Itanium are essentially ignored is deliberate. If this were not the case then everyone in MS land would sing the praises of Itanium.

    23. Re:No x86 Compat is the Achilles' Heel by bbbl67 · · Score: 1

      Nope, they went out of their way to say that Itanium *would* run x86 software. It just turned out later that they were talking about emulating x86.

    24. Re:No x86 Compat is the Achilles' Heel by Anonymous Coward · · Score: 0

      LOL Pwned!!!!
      hahahahahahahaha

    25. Re:No x86 Compat is the Achilles' Heel by Anonymous Coward · · Score: 0

      You've got an encoded email address that I've traced back to the military. Now I want to know more! :)

    26. Re:No x86 Compat is the Achilles' Heel by Madoc+Owain · · Score: 1

      Something people don't mention is HP's IA64 server line, running HP-UX 11.23 . Why on earth would anyone want to run x86 apps on a box that's clearly designed for multi-threaded 64-bit apps? Use the server for the purpose it is designed for, don't malign it for not being able to run something it's not intended to. The Itanium is a processor meant for enterprise markets, not for the PC hobbyist market.

      Intel finally makes a chip that REALLY IS for the server market, doesn't that make John Dvorak's head explode or something? :)

      Now that the general commentary is out of the way, I have a question for the parent poster - you mention Oracle+everyone else, why not Oracle+HP? I work in an enterprise IT shop and we have numerous HP-UX PA-RISC servers running Oracle quite contentedly. We also have a number of SUN Solaris 7-8 servers running Oracle. Each department we're buying and building servers for has a different processing need and budget, so we get Solaris and HP-UX orders in varying numbers. Then again, we're known for claiming we're trying to match the rest of the industry then doing whatever the hell we want. Maybe we're the only shop running Oracle on HP-UX?

      Probably not.

      That being said, I don't particularly like the IA64 servers we've received, but that's more due to lack of support for our old-and-busted backup methods and the extremely painful process we have to undertake to mirror a root drive.

    27. Re:No x86 Compat is the Achilles' Heel by MynockGuano · · Score: 1

      Are you saying you willfully cracked military encryption?

      Marines are on their way; have a nice day.

  11. Two things: by grahamlee · · Score: 3, Interesting

    One, it gets no respect because nobody uses it. Where is the kudos for the transputer? Why does nobody love the Apple ///? Second, yes it beats the x86 into the ground. I'm not surprised. Now show me how it compares against a real CPU. We've already seen that the Itanium is competing in a different space (supercomputers), so show me how it compares with the MIPS that SGI have ditched in its favour. I wouldn't be surprised if an n GHz MIPS stuffs an n GHz Itanic into the floor.

    1. Re:Two things: by Iriel · · Score: 1

      You're probably right about the MIPS in performance (though I wouldn't know), I don't think this article is attempting to pull a "OMFG WTF! Why did you abandon this l337 chip?" The author is simply trying to state that it really isn't as bad as people say (whether that's proven or not, I am in no position to say).

      So while CPU X can beat the crap out of the Itanium, I don't think the author is trying to come out as the king of all CPUs now and forever here.

      Though I do think it's kind of funny that, given I have seen the original marketing for the chip, this article makes the Itanium look like somebody standing on your porch with a stack of benchmark scores and a highlighter asking for a cookie.

      "See? I was number 7..."

      --
      Perfecting Discordia
      www.stevenvansickle.com
    2. Re:Two things: by Anonymous Coward · · Score: 5, Informative

      Now show me how it compares against a real CPU. ... I wouldn't be surprised if an n GHz MIPS stuffs an n GHz Itanic into the floor.

      Guess what? It doesn't. Itanium really does outperform MIPS and if you'd care to look it up yourself, you'd see. Itanium and POWER have been rougly neck and neck in vying for the top performance spot since the Itanium 2 was first released. Each new processor from either vendor bests the other.

      As for your disparaging remarks about X86, consider that it offers the highest performance outside of Itanium and POWER on floating point and overall keeps pace on integer code. Topping X86 is, believe it or not, a real feat. Top of the line AMD64 and Intel chips are engineering marvels as far as processors go. MIPS certainly can't touch them.

      It may be fashionable to dis X86 but if you look at the numbers and the microarchitecture, you'll be hard pressed to find anything significantly better.

    3. Re:Two things: by Markus_UW · · Score: 1

      Wow, a processor thread, and nobody's mentioned SPARCs yet...

      As I recall, they tend to be neck in neck with the POWERs. Plus I can't wait for Sun & Fujitsu's new chips to come out this fall, should be sweet.

      P.S. Yes, I am a Sun Whore.

    4. Re:Two things: by Anonymous Coward · · Score: 0

      "As for your disparaging remarks about X86, consider that it offers the highest performance outside of Itanium and POWER on floating point and overall keeps pace on integer code."

      Uh, so out of the top three chip architectures x86 comes out...third?

      Congrats x86! You really aren't 'teh suck'!

    5. Re:Two things: by be-fan · · Score: 1

      Sun's SPARCs lag behind even cheap x86 chips in SPEC. The top UltraSPARC is a little more than half the speed of the top Power5 in integer, and less than half the speed in floating-point. The top SPARC64V edges out the top Power5 in integer, but is about 60% as fast in FP code. The top Opteron beats all three in integer, and beats the top UltraSPARC in FP (by a lot), and loses to the top SPARC64V in FP (by a few percent), and to the top Power5 in FP (by a lot).

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:Two things: by wickedmm · · Score: 1

      Could it be that we will see Apple jump on the Itanium bandwagon? OSX on an I2? What could it mean for the MSFT -vs- Apple fiasco?

      --
      Don't be a Hem, find some new cheese.
    7. Re:Two things: by bani · · Score: 2, Insightful

      sparc is no longer competetive. its major design win (register windows) turned out to be a liability long term. memory got faster, caches got better. register windows became obsolete, and sparc stopped scaling competetively.

      powerpc is an overall better (faster, cheaper, more scalable) design than sparc. it doesnt make the same kind of assumptions as sparc did and thus powerpc was able to scale along with the rest of the industry as technology developed -- powerpc was able to take advantage of new developments in silicon without having to lug around old cruft; powerpc had few fundamental dependencies on the underlying technologies. sparc has baggage (register windows) which are no longer architectural wins.

      powerpc assembler is really unpleasant to read and debug though. load/store is a pita. two instructions to load a single 32 bit value and _five_ for a 64 bit value(!). now consider that a compiler can completely reorder those instructions. not nice for readability.

    8. Re:Two things: by Anonymous Coward · · Score: 0

      Well Itanium beats the current generation of MIPS on a clock per clock comparison, this is however because the R16k (which recently made 1ghz) is basically a die shrunk R10k (a design that is nine years old)

      Now the R18k which SGI ditched back in jan 2004 even after promising all their customers (NASA etc.) and which had already taped out would have given twice the FP performance of the R16k at the same clock speed. That versus itanium2 would be very interesting.

      Awh well back to playing on my R12k SGI Octane2 :)

    9. Re:Two things: by bemenaker · · Score: 1

      Do you apple boys ever read a press release? Apple is going to pentium 4. Not even apple fans are crazy enough to buy a $1000+ processor. Not box, processor.

    10. Re:Two things: by buzzazz · · Score: 1

      Hey! Find one foo! to second your statement "Why does nobody love Apple///?" I disagree wholeheartedly.. Apple is the object of many nerd's affection@@ Tell that to a windoze freak, and they might let you get away with it.. ;-)

      --
      The Wisest Men Follow Their Own Direction. ~ Euripides http://www.linkedin.com/in/buzzaz
    11. Re:Two things: by sl3xd · · Score: 1

      load/store is a pita.

      Sure, if you're on the software side of the road.

      On the hardware side of things, it's GREAT.

      It's funny hearing compiler guys complain about how woefully hard it is to create a good optimizing compiler for ; yet the same group will gleefully throw the task at hardware designers and tell them that it's much easier to handle the same code optimization in instruction decode.

      Riight. Let's compare the difference in resources a compiler has to toss at a problem, and compare that to what a subsystem within the CPU die has. It's also quite wonderful to hear people who have no clue how to design silicon telling hardware guys that they need to take a compiler class (something most 'new' silicon designers do, in fact, take).

      Don't complain about how hard it is to make an optimizing compiler, until you've been tasked with designing hardware to do the same job -- the difference being that the compiler has megabytes of memory and all the time it needs, wheras the hardware has a few bits, and a few hundred picoseconds.

      Yes, there are some (and they are few) optimizations that really are only doable on the CPU core -- but there are far, far too many optimizations that should be done at compile time, that the CPU has to optimize/schedule/re-order instead.

      --
      -- Sometimes you have to turn the lights off in order to see.
    12. Re:Two things: by bani · · Score: 1

      ok, lets try this again.

      ppc: load 64 bit constant
      5 instructions = 20 bytes to load an 8 byte value

      x86_64: load 64 bit constant
      1 instruction = 10 bytes to load an 8 byte value

      not only do you have considerably more scheduling issues on ppc, but you also have to burn far more memory bandwidth to do it. suddenly ppc doesn't look so hot anymore.

      not to mention ppc has some rather silly design misfeatures which make position independent code not only slower than other processors, but ridiculously difficult to debug as well. the blame for these misfeatures lie solely with the hardware guys.

    13. Re:Two things: by Anonymous Coward · · Score: 0

      It may be fashionable to dis X86 but if you look at the numbers and the microarchitecture, you'll be hard pressed to find anything significantly better.

      Absolutely.

      In fact, the POWER and Itanium products do better than x86 in floating point NOT because of some "superior" microarchitecture, but because of their expensive memory heirarchy.

      Compare cache sizes of top of the line x86 vs POWER or Itanium. Then compare memory bandwidth. You'll see a HUGE advantage for Itanium and Power systems.

      Slap those memory systems onto an x86 and they'll smoke those Itaniums. Of course, the supercomputer market is microscopic, so it makes no economic sense to beef up the memory system of x86 processors.

      Itanium sucks. It is the worst idea Intel has ever come up. Compiling efficient code is NP-hard and heuristics just don't compete against a dynamically scheduled out of order machine. For example - It takes 3 days to compile GCC for the SPEC benchmark.

      It is power-inefficient. It is fetch-bandwidth and memory bandwidth inefficient. Predication adds complexity and burns way more power and buys you nothing over branch prediction.

      Itanium does well on supercomputer workloads because any moron can build a compiler that does dot-products and cross-products efficiently. Memory accesses are also linear and very predictable. They also have 2x the floating point execution bandwidth of top of the line x86 processors. It's embarrassing that they don't score even higher.

      PS - I work for Intel.

    14. Re:Two things: by sl3xd · · Score: 1

      Hey, I was talking about Load/Store in general.

      Not the problems that the PPC's implementation has.

      One favorite is that while the PPC is 'RISC', it has a larger number of instructions than an Opteron; but since 'RISC' is usually slapped on any load/store architecture, it still is considered a 'RISC' chip.

      x86_64: load 64 bit constant
      1 instruction = 10 bytes to load an 8 byte value


      You mean one instruction that the program issues. A modern 'CISC' chip (such as the x86_64) accepts the one instruction; that doesn't mean that only one instruction is executed, and that only 18 bytes of memory get used to perform the operation. The CPU has to then translate the programs 'instruction' into the actual instructions that the CPU executes, using a much larger number of internal registers (and memory) than is visible through software. The PowerPC (and to a greater extent, VLIW chips) expose this to the software level. But just because an x86 doesn't expose this to the developer doesn't mean that it isn't happening.

      Of course, this isn't as apparent with an operation as simple as 'load'. It (rapidly) becomes apparent the moment you start using instructions that do a load, operation, store, (and more!) all in one instruction.

      Which brings me back to my point of hardware being forced to do things that the compiler should have been doing in the first place. There's nothing like having to translate each 'input' instruction into multiple real instructions to be executed.

      --
      -- Sometimes you have to turn the lights off in order to see.
    15. Re:Two things: by bani · · Score: 1

      doing all optimizations in the compiler would be just dandy if all programs were 100% static and linear.

      since they're not, runtime optimizations in hardware need to be done.

      you ph.d hardware types want to push all optimizations into the compiler, so it "simplifies the hardware". great. you got itanium. see how well that worked? oh wait, it didnt.

      Which brings me back to my point of hardware being forced to do things that the compiler should have been doing in the first place. There's nothing like having to translate each 'input' instruction into multiple real instructions to be executed.

      oh great, now you want compilers to emit u-ops to make your life easier. and you hardware guys wonder why we call you unhinged?

    16. Re:Two things: by Anonymous Coward · · Score: 0

      > you ph.d hardware types want to push all optimizations into the compiler, so it "simplifies the hardware". great. you got itanium. see how well that worked? oh wait, it didnt.

      What it got was MIPS, SPARC, POWER and others...

      Are you going to say they didn't work?

    17. Re:Two things: by sl3xd · · Score: 1

      I'm well aware there are few programs that are 100% static and linear. There is a lot to be said for runtime optimization; all I'm saying is there needs to be more done at compiler time instead.

      now you want compilers to emit u-ops to make your life easier. and you hardware guys wonder why we call you unhinged?
      You realize this argument goes both ways, right? That turf war aside, emiting a 'u-op' as you put it, is exactly what a compiler for a 'RISC' processor does, because there are no u-ops -- this is one of the key characteristics of a RISC processor. It's not like it's something that isn't done; x86 is not the entire universe, or even close to 1% of it. Most of the world's CPU's are a RISC machine, and a RISC cpu's compiler dispatches the equivalent of a CISC u-op.

      And it isn't really a case of making my life any easier-- run-time optimization isn't going away. But there are costs involved with doing optimizations at runtime rather than at compile time. First is the consumption of electricity, and there's the closely tied generation of heat from the extra circuitry. It significantly increases the size of the CPU die, the transistor count, etc. In fact, that's the whole reason the RISC methodology came about -- at the time, it was noticed that the instruction decode stage was taking up some-odd 17-20% of the CPU -- and most of those transistors did nothing but suck power and produce heat 99.999% of the time. By making the compiler smarter, and the chip dumber, chip costs, chip complexity, power consumption, heat produced, transistor count, and cost were all slashed -- with no drop in performance.

      People care about how long the battery lasts on their portable devices, how hot their notebook gets in their lap, how much cooling is required to keep a rack of servers running, things like that.

      Taking that much more effort ONCE at compile time is cheaper (for everybody involved) when contrasted to doing the same optimization trillions of times while executing the program. There are far more negative consequences that come as a result of having the hardware optimize code -- not that it doesn't have its uses (as you stated, not all programs are static and linear); but that doesn't excuse a substantial portion of what is being offloaded to the CPU for optimization.

      The Itanium takes the offloading tasks to the compiler a bit too far; you miss out on the optimizations that can really only be done at execution time. Most of the other complexity problems with Itanium compilers are more related to its VLIW design than the Itanium itself; there are few who are familiar with writing a VLIW compiler, because it's a more difficult problem to wrap one's head around.

      A pure comiler-optimized execution isn't really a practical thing; but compilers can (and should) be doing more, as they have a much better opprotunity to take a larger view of the code.

      The fact is that in either case, the algorithm to implement a given optimization is nearly the same in either case -- The only substantial difference is in its implementation, and the corresponding tradeoffs. Obviously, I believe if a compiler can do the particular optimization, it should be doing it-- not the CPU.

      It doesn't take additional energy at runtime if the optimization is done by the compiler. It does require energy each time the optimization is executed during a program's run -- which is fairly non-trivial, espescially over time.

      This doesn't matter much to those who will only be programming to a 'PC' plugged into a wall. But for those who make any kind of battery-powered, consumer, or embedded device, the extra energy consumption is a very big deal, as are the extra costs involved with a larger die, higher transistor count, and larger amount of heat dissapated.

      --
      -- Sometimes you have to turn the lights off in order to see.
    18. Re:Two things: by bani · · Score: 1

      Most of the world's CPU's are a RISC machine, and a RISC cpu's compiler dispatches the equivalent of a CISC u-op.

      er no... CISC uops arent anywhere NEAR as complex as RISC instructions. mips, sparc, ppc, alpha instructions are all VERY complex compared to CISC uops.

      and eh, the die space you "win" with a smaller instruction decode stage doesnt make up for the space you lose having to add enormous caches because of the increased bandwidth your RISC instructions take. save a few % in instruction decode and lose tons of % in added cache to make up for it.

      besides the fact that die space for instruction decode is tiny these days compared to the multiple execution units, the fpu, cache, etc. instruction decode takes vanishingly small amounts of space. so again, that RISC "win" is no longer existent.

      RISC looked very "n3at0" in the late 80s as it appeared CISC was running out of steam, but we learned a lot since then. a lot of the assumptions which were the foundation of RISC design turned out to be not true in the long term.

      and heh, if you really get down to it none of the modern "RISC" architectures are really "RISC" by the classic definition. so really, RISC is dead by most definitions of the term. it only lives in uops and maybe the embedded space -- and even that is being eaten up by a growing CISC market (motorola coldfire for example).

    19. Re:Two things: by Anonymous Coward · · Score: 0
      Where is the kudos for the transputer?

      Thank you for using the word "kudos" correctly, as a singular noun meaning (in the original) honor, fame or glory.

    20. Re:Two things: by quarkscat · · Score: 1

      Face it. Intel's Itanium is a special purpose processor that would never make its way into an everyday workstation -- except when bundled in "market-speak" also as a space heater. The 32-bit
      "compatability" mode runs like PII-300.

      OTOH, 64-bit MIPS and PowerPC and UltraSPARC do a credible yeoman's service with 32-bit applications, without the kooky VLIW pipeline and branch prediction issues for the compiler to deal with.

      Having used 32-bit and 64-bit applications on both the MIPS and UltraSPARC platforms, I can tell you that overall performance and throughput do count towards usability. The ia64 cannot make such a claim. It has a place in specialized supercomputers dedicated to specific hand-coded applications, and little else. This is a fact that Intel tacitly admits -- just look at their depreciated "roadmap" for this processor.

      Netcraft should predict its early demise -- they would be much more correct than their *BSD prediction.

    21. Re:Two things: by veliath · · Score: 1
      powerpc was able to take advantage of new developments in silicon without having to lug around old cruft...sparc has baggage (register windows) which are no longer architectural wins.

      Could you point me to documentation that explains why SPARC's register-windows scheme is harder to implement in todays technologies?

      two instructions to load a single 32 bit value and _five_ for a 64 bit value(!).

      This is true of the SPARC too. Infact I think its true of all fixed width instruction ISAs. I understand compilers very rarely need to load 32 or 64bit immediate values into registers. Addresses can usually be generated using PC relative addressing, no?

      Anyways do post links or point me to documentation that describes the difficulties in implementing the SPARC ISA on todays technologies.

      veliath

    22. Re:Two things: by bani · · Score: 1

      Could you point me to documentation that explains why SPARC's register-windows scheme is harder to implement in todays technologies?

      No, because it doesn't exist.

      register windows scheme isn't harder to implement. register windows scheme is utterly pointless on modern systems.

      register windows assumed these things:
      1) function calls are incredibly expensive due to saving/loading registers between calls.
      2) task switching is incredibly expensive due to saving/loading registers between task switches.
      3) compilers would not get appreciably better.

      except that in the long run, experience showed that none of these were real issues -- only imagined ones.

      other architectures made fewer assumptions like this and did much better in the long run (mips, powerpc).

      This is true of the SPARC too. Infact I think its true of all fixed width instruction ISAs. I understand compilers very rarely need to load 32 or 64bit immediate values into registers.

      depends on the code, but it happens far more often than you think. especially if you're dealing with fp code.

      try objdump on some binaries. it's a real eye opener.

      Addresses can usually be generated using PC relative addressing, no?

      sometimes. not always. and don't get me started on PIC code for powerpc -- it's a real mess.

      Anyways do post links or point me to documentation that describes the difficulties in implementing the SPARC ISA on todays technologies.

      its not difficult -- its pointless. i cant point you to documentation describing the difficulties in implementing the 68k ISA on todays technologies either -- but it's just as relevant.

    23. Re:Two things: by grahamlee · · Score: 1

      Erm, Apple /// refers to a particular computer (the one that came out after the Apple ][, hence its name). Find me someone who has seen an Apple /// running; that's hard enough.

    24. Re:Two things: by grahamlee · · Score: 1

      No problem. I have British citizenship as my guide, and Nazism as my grammar methodology.

    25. Re:Two things: by grahamlee · · Score: 1

      I think you may be mistaken. Apple have announced a switch beginning at the end of next year to Intel processors, not Pentium. At no point was the word Pentium specifically used. Yes the Developer Transition Systems appear to have Pentium 4 3.6GHz in (I'm not signed up for the DTS program so can only go by what the rumour sites report - besides even if I were signed up I like NDAs. They're fun) but the focus of those systems is not to port to Pentium 4 - the focus is to produce Universal binaries. Once you've written code that doesn't depend on being sat on a big-endian register-rich RISC processor with an Altivec bolted on the side, but instead relies on the existence of cross-platform APIs to take implementation detail into account, you can go wherever you want. Yes it seems likely that Pentium is where we're headed in the near future. But people thought NeXT were moving toward being Intel-only, but then the SPARC and PA-RISC ports appeared (and the Alpha and m88k [mmm....Harvard architecture] ports nearly appeared...).

    26. Re:Two things: by veliath · · Score: 1
      I suppose the delay slot in the SPARC ISA is also not really necessary. Yes?

      other architectures made fewer assumptions like this and did much better in the long run (mips, powerpc).

      When you say they did much better, what do you mean? Did the ISA limit the creation of faster processors? Did the ISA limit possible compiler optimizations? Once again, could you point me to a comparison of ISAs?

      I realize its harder to code for the SPARC ISA and a lot of what it exports are assumptions from a certain era that do not hold. But did this really contribute to it being less successful? Is the SPARC less successful?

      Thank you,
      veliath

    27. Re:Two things: by bani · · Score: 1

      PowerPC never had them afaik. MIPS used to have delay slots but got rid of them, and afaik recent SPARC ditched delay slots too. I would have to say yes, delay slots are really not needed anymore. they are probably considered a liability -- or at the very least archaic.

      When you say they did much better, what do you mean? Did the ISA limit the creation of faster processors? Did the ISA limit possible compiler optimizations? Once again, could you point me to a comparison of ISAs?

      By better I mean much more successful. They also scaled much higher. Look at how widespread MIPS and PowerPC are, versus SPARC. Look at how high SPARC (didn't) scale, versus PowerPC.

      MIPS (and x86, and others) benefited greatly from advances in compiler architecture, as it didn't make the assumptions that SPARC made (eg, that compilers wouldn't get better) and thus didn't dedicate fundamental architectural designs (register windows) to "combating" shortcomings of compilers. it was also a much simpler design overall than SPARC.

      also, the enormous register sets of SPARC are vastly underutilized. they're largely a waste. hell, the powerpc register set rarely gets 1/2 utilized under even under the best of situations.

    28. Re:Two things: by sl3xd · · Score: 1

      the die space you "win" with a smaller instruction decode stage doesnt make up for the space you lose having to add enormous caches because of the increased bandwidth your RISC instructions take. save a few % in instruction decode and lose tons of % in added cache to make up for it.

      This isn't the problem you seem to believe -- at least not for a RISC design. A VLIW design, however, is another story entirely. VLIW (ie Itanium) != RISC; VLIW needs massive amounts of cache (and bandwidth).

      On a RISC chip, the amount of die size increase due to the instruction cache is negligible compared to the die shrink from reduced instruction decode. And in terms of actual usage, instruction caching is a tiny fraction of the space taken; data cache is (overwhelmingly) the majority holder -- and data takes up the same amount of space reguardless of the chip paradigm.

      RISC looked very "n3at0" in the late 80s as it appeared CISC was running out of steam, but we learned a lot since then. a lot of the assumptions which were the foundation of RISC design turned out to be not true in the long term.

      CISC did run out of steam. Entirely. The only vestigal part of a CISC design that exists today is the programmer's instruction set -- but after the programmer's interface has been passed, everything is entirely in RISC country. A CISC uop is the CPU's RISC core execution instruction. The only place CISC exists is to the programmer -- it doesn't exist at all after the instruction has been chopped up into RISC instrucitons for execution. There is no CISC vs. RISC war; RISC won -- and won so convincingly that the only popular CPU that even looks like a RISC chip anymore is x86 -- but it only looks like a CISC chip to the ignorant who choose to delude themselves into believing that CISC still has relevancy. CISC chips are notoriously difficult (and often impossible) to pipeline; one of the key goals of the RISC model was to make pipelining almost trivial -- which is the biggest reason why nearly all modern chips (including x86) are, at their core, RISC designs (with a bit of circuitry to chop CISC instructions into a series of RISC instructions).

      That's not to say that there aren't elements of both; one of the key goals of a CISC design was to have the assembly act much like a higher-level language like C. On other side of the coin, RISC doesn't provide high-level instructions at the assembly level -- the developer isn't supposed to be writing in assembly -- compiling the code from a higher-level language such as C was the intended path for RISC machines. RISC chip design assumes a good, optimizing compiler would generate fast code (so much for that assumption)...

      And as for your contention about a RISC instruction being very complex compared to a CISC uop... RISC instructions (such as 'add', 'load', 'store', or 'is greater') can't be made more atomic. The 'complex' instructions of a PPC, MIPS, Alpha, or SPARC processor aren't a RISC instruction at all -- but rather an attempt to provide a way for developers to use the 'new gee-whiz-bang SIMD idea'. Since a RISC chip assumes the use of a compiler, then compilers would have to add support to SIMD operations -- but the timeline to get compilers to support SIMD was so long that the decision was made to make a high-level (CISC) series of instructions and bolt them onto the RISC core; in this way the new SIMD features could be used immediately, rather than years down the road. Considering the time it took compiler developers to support SIMD outside of inline assembly, this decision seems to have been well-justified.

      --
      -- Sometimes you have to turn the lights off in order to see.
    29. Re:Two things: by Anonymous Coward · · Score: 0

      Most kind, kind sir. Should have known the /// wouldn't be meaningless.. not here..

    30. Re:Two things: by bani · · Score: 1

      This isn't the problem you seem to believe -- at least not for a RISC design. A VLIW design, however, is another story entirely. VLIW (ie Itanium) != RISC; VLIW needs massive amounts of cache (and bandwidth).

      On a RISC chip, the amount of die size increase due to the instruction cache is negligible compared to the die shrink from reduced instruction decode. And in terms of actual usage, instruction caching is a tiny fraction of the space taken; data cache is (overwhelmingly) the majority holder -- and data takes up the same amount of space reguardless of the chip paradigm.


      All modern CPUs have anywhere from 512k of cache to several megabytes. In terms of die space the instruction decode is vanishingly small compared to everything else.

      So thank you for confirming that this 'design win' of RISC is no longer significant or even relevant anymore.

      And as for your contention about a RISC instruction being very complex compared to a CISC uop... RISC instructions (such as 'add', 'load', 'store', or 'is greater') can't be made more atomic.

      Yes they can. uops are like "increment program counter" "emit address out the memory bus" "submit read command to memory bus" "retrieve word from data bus into memory bus register" "transfer word from memory bus register into cpu register" etc.

      your typical load/store powerpc or mips or sparc "risc instruction" may decode to 3 or more uops (typical x86 might be 4-6)

      uops are _very_ low level, bare metal. RISC instructions are fairly high level abstractions by comparison.

    31. Re:Two things: by sl3xd · · Score: 1

      In terms of die space the instruction decode is vanishingly small compared to everything else.
      So thank you for confirming that this 'design win' of RISC is no longer significant or even relevant anymore.
      On the original Opteron, Instruction Decode was about the same size as one of the FPU pipelines, or about 10% of the total die space; this is not 'vanishingly small.' Of that, about 75% of the ID was strictly for translation of x86 into 'native opteron.' So that's a 5% power and heat penalty that is entirely unnecessary.

      RISC still does have a design win here, and is quite significant -- an extra 15-20 minutes of battery life on a notebook computer isn't unappreciated. It's just that the win isn't as big as its proponents anticipated, largely due to the fact that modern superscalar/superpipelined CPU has multiple (frequently identical) execution units. RISC assumed (quite reasonably, at the time) there wouldn't be such duplication of resources within a single CPU core. Reguardless, that few percent reduction of complexity, size, and power do matter, and does add up when you ship a few million chips.

      The other design wins of RISC was in pipelining and promoting(requiring) good compilers -- both of which are the biggest wins of the RISC evolution, and are very, very far from being insignificant or irrelevant.

      Yes they can. uops are like "increment program counter" "emit address out the memory bus" "submit read command to memory bus" "retrieve word from data bus into memory bus register" "transfer word from memory bus register into cpu register" etc.

      Apparently we're talking a difference between operations and instructions. These are not instructions, they are hardwired operations that tend to use the clock as a trigger. Many (such as the program counter increment) happen with each and every clock tick, and are only overridden with an instruction.

      What I was speaking of are what were termed 'RISCops' by AMD -- meaning a CISC instruction like:

      add

      would be translated into its RISC equivalent for execution in the Opteron's core:
      load
      load
      add
      store

      Of course pipelining ends up breaking even these down into the operations of shuffling bits into and around registers until the actual 'add' takes place; then moving the result back to a register, which is in turn moved to cache, and if it's really lucky, back to main memory.

      The number of operations within the instruction (setting address pins, wait for ready, read data pins, store value in register, etc, etc.) are of course still there. And the number of these operations has only increased with AMD putting the entire memory controller on the die; life used to be so much simpler... just set the pins and wait for the memory controller to do its job...

      --
      -- Sometimes you have to turn the lights off in order to see.
    32. Re:Two things: by bani · · Score: 1

      by your definitions and criteria a 6502 is RISC. :-)

      it is interesting to note that in the most recent generations of chips, x86/"cisc" designs tend to be much smaller, lower power, etc. than their "risc" counterparts. take the behemoth alpha 21364 for example.

      the big wins in power savings come not from shrinking instruction decode space, but going to new fabrication technologies and materials and other technologies. you get orders of magnitude savings there, versus a few %. pure "risc" designs (sparc, mips, etc) have proven diminishing returns vs effort over the past decade or so.

    33. Re:Two things: by sl3xd · · Score: 1

      the big wins in power savings come not from shrinking instruction decode space, but going to new fabrication technologies and materials and other technologies. you get orders of magnitude savings there, versus a few %. pure "risc" designs (sparc, mips, etc)

      I won't argue otherwise; but every microwatt counts (espescially to the embedded world).

      And for diminishing returns vs. effort for a RISC design vs. a CISC design -- CISC is intrinsically harder to design (pipelining, decode, optimization, etc.) That's why everything AMD designed from the Athlon to the Opteron are, in their heart, a RISC chip; it's much easier (and therefore cheaper) to pipeline a RISC design. A major argument of RISC was that it's a cheaper/easier design methodology; something that is no less true today. While the proportion of the savings are diminished, the savings are still there.

      it is interesting to note that in the most recent generations of chips, x86/"cisc" designs tend to be much smaller, lower power, etc. than their "risc" counterparts. take the behemoth alpha 21364 for example.

      Comparing Alphas to Athlons is really quite apples to oranges... it's not even the same market.

      When I first read this, I was wondering what you were on; then I read the qualification of 'x86/cisc'. Recent x86 designs are neither CISC nor RISC, (since they are both and neither) so it's inaccurate to call it a CISC cpu. The same is true for PowerPC, SPARC, and just about every other desktop/workstation processor out there.

      But I have yet to see a true/fully CISC design that is smaller and has lower power requirements than an equivalent pure RISC design. For that matter, I haven't seen a new and true CISC design in ages. However, the embedded market is dominated with true RISC chips -- precicely because they are smaller, cheaper, and use less power.

      Like I've been saying from my first post -- the desktop/workstation and server market is less than 1% of the total CPU market (in both dollars and quantities); the rest are variations of embedded processors, whose market is thoroughly dominated by fairly pure RISC designs.

      --
      -- Sometimes you have to turn the lights off in order to see.
    34. Re:Two things: by bani · · Score: 1

      But I have yet to see a true/fully CISC design that is smaller and has lower power requirements than an equivalent pure RISC design. For that matter, I haven't seen a new and true CISC design in ages.

      Motorola Coldfire

      it's wildly popular in the embedded market because it's extremely low power and cheaper than RISC in the same form factor and performance realm.

      it's not new (it's 68k ISA). but it proves RISC is not a default win.

      as for "new" cisc designs, they are probably out there. microchip's PIC comes close to CISC (it has a small instruction set, but it's not pure load/store and it has no u-op engine). just because you havent seen one doesnt mean they dont exist :)

  12. Sure, it's cheap NOW. by Proc6 · · Score: 5, Interesting

    Probably because when it mattered a single CPU Itanic was more like $12,000 and not $2,000. After fucking up all their marketing and delivering strategies no one wants one anymore.

    --

    I'm Rick James with mod points biatch!

    1. Re:Sure, it's cheap NOW. by Anonymous Coward · · Score: 0

      $12,000???? Damn. Did they only make four of them?

    2. Re:Sure, it's cheap NOW. by Foolomon · · Score: 1

      [Sniff sniff]

      I smell..

      [Sniff sniff]

      I smell the MCA architecture all over again.

  13. Easy Answer: It started as a flop by drhamad · · Score: 5, Insightful

    Hundreds and hundreds of products have been killed or permanently crippled because their first versions were terrible. Itanium is the same thing. With the public perception of the Itanium still the same as it was for the first (pathetic) iteration of it, how are you going to convince your manager to spend the money to get it? Benchmarks only go so far.

    --
    -Daniel
  14. Here are.. by th1ckasabr1ck · · Score: 5, Informative
  15. because it's a failure by danheskett · · Score: 3, Interesting

    Itanium was a huge project jointly developed with many partners, most of the significant ones have long since abandoned the effort.

    It was supposed to be the future of Intel - shipping units on the order of the pentium line. A redesign from scratch of how processors "should" be designed.

    It's taken far longer, cost far more, and yielded far less than promised.

    That's basically it.

    Also, I'd be willing to bet Intel staked a bigger part of its decision on the availablity of platform independent binaries making serious inroads, which hasn't really materialized. Platform independence of the major OSS and commerical apps is obtained through porting and source-level compatability.

  16. 64-bit Gaming by Anonymous+Custard · · Score: 2, Insightful

    http://techworthy.com/PCUpgrade/SeptOct2004/64-Bit -Gaming.htm

    Because for Itanium compatibility they'd have to port everything over to the Itanium proprietary instruction set. You can see how eager they've been to do that for Macs, so guess how likely they are to port it for Itanium.

    1. Re:64-bit Gaming by MojoRilla · · Score: 1

      Porting games to the Mac means porting to different API's as well as a different CPU. Plus there are very few Mac's compared to PC's in the market. Would you do 30% more effort to support 5% more audience?

      Modern games are mostly written in a higher level language anyway (C or C++) and probably would require very little tweaking to work on Itanium. The problem is market share. It is not work creating and testing a port if no one will buy it.

    2. Re:64-bit Gaming by Nasarius · · Score: 1
      Because for Itanium compatibility they'd have to port everything over to the Itanium proprietary instruction set.

      That's what compilers are for. Really, it's not such a big deal for most programs.

      --
      LOAD "SIG",8,1
    3. Re:64-bit Gaming by mike260 · · Score: 1

      Porting something to a different ISA is pretty trivial, excepting endian issues. It's switching OS and graphics/audio/input API that's the hard part.

    4. Re:64-bit Gaming by tleps · · Score: 1

      Ummm, the compilers are 90% of the problem - read the link above a bit titled "a few reasons" about how much fun the researchers had trying to optimize ANYTHING. And it's not like the game coders are known for giving us great, stable code - ask any of us who play. Driver issues & crash to desktop or worse are almost a given for the high end games (at least prior to a patch or two...), and they certainly aren't going to spend lots of cash on programmers writing assembly like they used to in order to get around the chips scheduling issues - if they can even get the information to do such.

    5. Re:64-bit Gaming by Anonymous Coward · · Score: 0
      That's what compilers are for. Really, it's not such a big deal for most programs.


      And where are these compilers? Do you know of any compiler that can optimize real code (not just benchmarks) to run well on an Itanium?

    6. Re:64-bit Gaming by Nasarius · · Score: 1

      Most "real code" isn't optimized specifically for x86. I imagine the Intel compilers do a good job of optimization for IA64, as they do for x86.

      --
      LOAD "SIG",8,1
    7. Re:64-bit Gaming by HuguesT · · Score: 1

      Well yes it is a huge, enormous deal.

      I run AMD64 FC3 Linux at home and a host of things simply don't work, at the source level. For instance simply compiling a KDE application on this platform is a black art.

      Tell Microsoft they only had to recompile windows for it to work on AMD64 and Itanium. Right. Take a look at how long it took and at how well it works, how many drivers are available, etc.

      Tell Apple they only had to convince supplier to recompile their code for the G5. Hint: it doesn't work that way.

      New chip, new chipset, new platform = more work to do and more testing. It costs money, vendors only do it if they see a sizeable return.

      There is essentially no return on Itanium today outside of a few server apps.

  17. 32-bit Xeon's have 64 bit extensions by voodoo_bluesman · · Score: 1

    32-bit processors are shipping with 64-bit extension which allow them to break the 4GB memory limit.

    This was main reason people wanted to see 64 bit chips, and since it has been resolved cheeply, there isn't nearly the market for it.

    1. Re:32-bit Xeon's have 64 bit extensions by cbrocious · · Score: 1

      We've been able to address more than 4GB of memory on x86 for many years. In fact, you can address up to 64GB of memory (36-bits) on modern x86 chips (P2 and up IIRC) in the kernel. A given process (or thread on certain OS's I believe) can address only 32-bits, but that's easily circumvented if you _need_ to do it.

      --
      Disconnect and self-destruct, one bullet at a time.
    2. Re:32-bit Xeon's have 64 bit extensions by Erbo · · Score: 1

      You're thinking of the Xeon EM64T (Nocona) processors. They're pretty much Intel's knockoff of the AMD Opteron, which they came up with, I gather, because the Opteron was kicking the Itanium's ass.

      --
      Be who you are...and be it in style!
    3. Re:32-bit Xeon's have 64 bit extensions by voodoo_bluesman · · Score: 1

      Yes. Due to the limited market for the pure 64-bit chip, they decided to go along with added the EM64T extensions instead.

  18. Inertia. by AsbestosRush · · Score: 2, Insightful

    Inertia, would be my answer to this question: Inertia of the technological kind keeps x86 on the desktop, even with the 64 bit extensions.

    Inertia keeps Microsoft on the desktop, even though it being low hanging fruit for crackers.

    Inertia can be a good thing... in this case, it's a bummer. I can safely say that my next game rig will be A64 powered, simply because of... inertia.

    --
    EveryDNS. Use it. It works.
    AC's need not reply
  19. No technical details... by robslimo · · Score: 2, Interesting

    but my understanding, from the rumor mill, says that the Itanium was too little, too late and was partially aborted in an effort to get it out of the lab. It was a joint HP/Intel effort that was supposed to be the "next big thing" in processors, but dragged on so long in the lab (more than 10 years) that, by the time it was released, contemporary competitors already had nearly comparable horsepower and an established mindshare.

  20. Everyone else is doing it! by hoborocks · · Score: 1, Troll

    Because it's cool to hate Intel.

    I love Intel. I wouldn't use another chip because I've had bad experiences with them, and never a single (notable) one with Intel. But for some reason, people love to bash Intel, simply because it's the big behemoth.

    Less costly doesn't necessarily imply better - I'm an avid hater of Microsoft, definitely, but it's not solely because they're huge.

    --
    AccountKiller
    1. Re:Everyone else is doing it! by Anonymous Coward · · Score: 0

      Though I don't hate Intel. I currently prefer AMD because their CPU's are faster, cheaper, and produce less heat than Intel chips.

      As for Itanium, it flopped because it simply didn't perform well for typical computer usage.

    2. Re:Everyone else is doing it! by Guysmiley777 · · Score: 1

      Well said. Its not hate of Intel, its that AMD is superior in many ways, but is being held back because of Intel's iron grip over the market.

      --
      Coding with assembly is like playing with Legos. Coding an application in assembly is like building a car with Legos.
    3. Re:Everyone else is doing it! by paitre · · Score: 3, Informative

      In my case, this is actually a load of bull.
      I've never had a significant problem with a CPU that couldn't be pointed at some external issue with the platform - be it cooling, the MB chipset sucking, etc. Things that Intel -does- try to "Do Right" by us on.

      That said - I use AMD CPUs pretty much exclusively in my work. Xeon 64bit wasn't there when we needed it (Feb of last year) and Opteron beats the shit out of Xeon on the stuff we do and finally, I can get -real- dual-core Optys -now-, not bolt-ons using the same damned broken shared bus that Intel x86 has been beating on forever.
      Price, as a matter of fact, is no longer a consideration. I know I'm paying more for AMD. I'm also getting the product I want and need.

      Itanium -could- actually fit into my DC. Everything we do is compiled by us, locally, and it's entirely possible that we'd benefit from it. However, even at 2k/CPU I can't justify the cost when we're looking at driving the CPU number up (our jobs are of the type where the more chunks you can divvy your dataset up into, the faster things get done - so the more processers, the better - it doesn't matter if that Itanium gets my process done in 45hours while it takes that Opteron 55 hours if I can throw twice as many Opterons at the problem and get it done in 30 due to smaller data chunks).

    4. Re:Everyone else is doing it! by Shazow · · Score: 1

      Not on topic of the article, but I love AMD for the same reason you love Intel. I wouldn't use another chip because I've had bad experiences with them, and never a single (notable) one with AMD. I don't necessarily bash Intel, most definitely not because they're big.

      Surely, I recommend AMD to all my friends, but they want my opinion and I'm giving it.

      Aside from monopoly strategies, I have no problems with Microsoft software. I don't use it, but I don't mind if others do -- it's their choice.

      Similarly, I hate ATI, but I love NVidia. Both are approaching roughly the same size, yet opinions clearly vary, so size is not an issue. One provides good drivers and hardware, the other one prays on the uninformed and tricky bundles (remember the Free HL2 voucher?).

      Lastly, cost is an issue. I am willing to shell out an extra 10-20% for better quality, but there's a limit. I'm not willing to pay double for 15% performance gain.

      And final point, which is the only one really on topic: I agree with the people that say Itanium limits people too much. I can see Linux users adopting it, as much of software is ported to be 64-bit friendly, but most users aren't linux users. And most users don't have the money to spend, especially on an unproven product (in terms of popularity).

      - shazow

    5. Re:Everyone else is doing it! by chrismcdirty · · Score: 1

      I prefer AMD, too, but come on!

      Faster, possibly. I've never tried one of those $1200 P4EE CPUs.
      Cheaper, definitely. It's the main reason I go with AMD.
      Produce less heat?! Since when? Every Intel machine I've seen runs cooler than a supposedly equal AMD machine.

      --
      It's like sex, except I'm having it!
    6. Re:Everyone else is doing it! by NaruVonWilkins · · Score: 1

      Actually, I buy AMD (which I find to be more expensive to maintain when you take into account manpower to set up systems) because they treat their workers better overall.

    7. Re:Everyone else is doing it! by poot_rootbeer · · Score: 1

      But for some reason, people love to bash Intel, simply because it's the big behemoth.

      Yeah, that must be it. When somebody doesn't like the same thing you like, it can't be because they have legitimate complaints about the thing. It must be them following the herd and trying to be "cool".

    8. Re:Everyone else is doing it! by rpdillon · · Score: 1

      Compare an Athlon64 with a Pentium 4 in terms of heat. AMD chips used to be the king of heat 4 years ago...they were dethroned by Intel and the Pentium 4 line some time back...

    9. Re:Everyone else is doing it! by Neoprofin · · Score: 1

      It's even cooler to hate Intel becuase they brag about their chips costing more.

      There was a not-quite-recent article in News Week or a similar magazine with the new president of Intel boasting that almost 50% of the price you pay for Intel processors is profit for Intel. If they dropped their desktop processor prices even 20% they'd be competitive for the money with AMD chips and you'd still be looking at monster profits. Why bother though when you can just stick a celeron in 50,000 Dells because nobody will notice the difference?

    10. Re:Everyone else is doing it! by SpamJunkie · · Score: 1

      it's cool to hate Intel.

      You must have missed Steve's WWDC speech. It is no longer cool to hate Intel.

    11. Re:Everyone else is doing it! by chrismcdirty · · Score: 1

      I see. I've never actually had the pleasure of using an A64 yet.

      --
      It's like sex, except I'm having it!
    12. Re:Everyone else is doing it! by Anonymous Coward · · Score: 0

      Produce less heat?! Since when? Every Intel machine I've seen runs cooler than a supposedly equal AMD machine.

      (I'm the AC you were responding to)

      This may have been the case a few years ago, with Thunderbird cores, and Athlon XP's probably (never owned an AthlonXP myself). But an Athlon64 system I just recently put together runs incredibly cool even with minimal air cooling (stock heatsink). Cooler than any other AMD CPU I've owned or used (K5, K6, Athlon's, Durons) and cooler than the P4 I use at work. I've done tests with full CPU load for an entire week and it stayed cool the whole time.

      The Athlon64 at full load with AC set to 80F runs 4C cooler than my P4 at idle with AC set to 75F. (sorry for mixture of C and F). Both using stock heatsinks. I am normally the type who advocates getting a better heatsink (big fan of Thermalright's products), but in this case, its not even necessary for the Athlon64.

      My tests may not have been scientific, and motherboard sensors aren't to be entirely trusted, but I've heard the same things from many other sources.

      AMD simply has done a great job reducing power consumption with the processors that use the 90nm process. Their stigma of having hot-running processors is no longer the case. I'm pretty impressed.

    13. Re:Everyone else is doing it! by Anonymous Coward · · Score: 0

      Oh, and note that I said "currently". I'd use Intel if they produced a better (and more cost-effective) product. I actually have much love for the Pentium 2 (and maybe the P3). IMO, the P2 was much better than what AMD had to offer at the time. But that was quite a while ago, and Intel started fumbling with the P4's and eventually lost the advantage in all areas.

    14. Re:Everyone else is doing it! by hoborocks · · Score: 1

      oh look. http://yro.slashdot.org/comments.pl?sid=155593&cid =13042906 This guy says, plain and simple, what I was making my point about!

      I'm glad AMD is pursuing this action against Intel just because I like rooting for underdogs, ...

      There are PLENTY of people who do this. PLENTY of people who attack the large-and-in-charge simply because of that status. This single post proves that there is at least one.

      And, oh yeah. When someone comes out with a statement like mine, it must be that they're being cry-babies. It can't be because people do this all the time (hint hint WHINY TEENAGERS hint hint). Of course people NEVER go against things that are in the majority because they are in the majority.

      This is not a debate of whether Intel's cock is bigger than AMD's cock! I never meant for it to do that!

      All I'm saying is that people can tend to root for the underdog and bash the big guy simply because of that status. And that, sir/ma'am, is an absurd thing to do.

      --
      AccountKiller
    15. Re:Everyone else is doing it! by Anonymous Coward · · Score: 0

      As much as I'd like to jump on the Intel hatefest, they at least care enough to produce a useable bios when they release their shiny new chips.

      Anyone who's suffered though one of the more unuseable chinese bios incarnations (VIA, Ali, SiS, etc.) on their Athlon systems ought to still have a sour taste in their mouths.

      That doesn't make Itanium any more palatable, but it doesn't sour me on Intel. For joe consumer PC the choices are P4 or A64, both of which are fairly competitive with one another.

    16. Re:Everyone else is doing it! by Anonymous Coward · · Score: 0

      Apparently now its cool to say "its cool to hate [insert large corporation]"...

      Their are idiots and trolls on Slashdot, stop being one of them.

  21. No good compilers for EPIC by Anonymous Coward · · Score: 5, Interesting

    I may be entirely wrong, but I believe the dislike for the Itanium stems from the fact that you can't compile any decently optimized code for it. Apparently, even Intel can't create a good compiler/linker and toolkit for creating machine code that makes good use of EPIC. Even though the processor itself is more efficient and faster, the same thing compiled to machine code running side by side with an Opteron or any other x86-64 chip will see the x86 win. If somebody could come up with a decent compiler/linker that provided full EPIC optimizations, they would be bangin, but they don't have it so we don't use it.

    1. Re:No good compilers for EPIC by hackstraw · · Score: 1

      I may be entirely wrong, but I believe the dislike for the Itanium stems from the fact that you can't compile any decently optimized code for it. Apparently, even Intel can't create a good compiler/linker and toolkit for creating machine code that makes good use of EPIC.

      Well, a linker has little to do with CPUs or performance, they just glue modules together.

      Intel's compiler is excellent. I've witnessed a 100% speedup by going from -O2 to -O3 optimization level on one code.

      The GCC compiler is not bad on the Itanium. Usable for system stuff.

      Even though the processor itself is more efficient and faster, the same thing compiled to machine code running side by side with an Opteron or any other x86-64 chip will see the x86 win.

      Maybe under some situations (with small memory programs with highly coupled CPU cache utilization), but as a general rule, this is not true.

      If somebody could come up with a decent compiler/linker that provided full EPIC optimizations, they would be bangin, but they don't have it so we don't use it./i.

      As a general rule, the best compilers for a CPU come from the people that make the CPU. The biggest exception to that is AMD, because they do not provide compilers, however the Pathscale and Portland Group compilers are good for AMD chips. Also, its ironic that a majority of the AMD Athlon and Opteron benchmarks that are published are done with code compiled with the Intel compiler. This was especially true when the 1st Opterons came out. The benchmarks that were published were often 32bit codes compiled with the Intel compiler.

    2. Re:No good compilers for EPIC by mkramer · · Score: 2, Interesting

      Trimaran, originally developed for the Itanium, has also proven to be an extremely capable compiler for parallel processors.

    3. Re:No good compilers for EPIC by Mr.+McGibby · · Score: 2, Insightful

      Well, a linker has little to do with CPUs or performance, they just glue modules together.

      Wrong.

      Having used Intel's compiler, I would think that you would know better. What about inter-module optimizations? Who's going to do that? The compiler or linker. It's the linker buddy. Optimizations aren't just source level. Once you have the assembly, there is still a lot of stuff you can do. Instruction reordering, vectorizations, etc.

      --
      Mad Software: Rantings on Developing So
    4. Re:No good compilers for EPIC by Glonk · · Score: 1

      [i]Wrong.

      Having used Intel's compiler, I would think that you would know better. What about inter-module optimizations? Who's going to do that? The compiler or linker. It's the linker buddy. Optimizations aren't just source level. Once you have the assembly, there is still a lot of stuff you can do. Instruction reordering, vectorizations, etc.[/i]

      I don't know Intel's compilers very well, but IBM's compiler does inter-modular optimizations (inter-procedural analysis) as part of the "compiler". It's a tool that is only included with the compiler and is not part of the linker -- in fact, the linker team at IBM is on a completely different continent from the compiler team and they don't do any optimizations.

    5. Re:No good compilers for EPIC by Nathan+Robertson · · Score: 1

      Yep, while I was at ANU, we had an HP/Compaq guy full time with us to help maintain a ~500 CPU Alpha cluster we had. HP were keen to show us Itanium, so they loaned us one. Changing between the release version of the Intel compiler at the time to the beta of the next version yielded a 30% increase in performance for no code change at all.

      The HP guys were saying that they were expecting these machines to get faster with age, because the compilers were making code run faster with each release. So yes, Itanium performance is largely dependant on the compiler.

  22. Apple by Anonymous Coward · · Score: 0

    Wouldn't surprise me to see this processor showing up in powermacs in some time.

    1. Re:Apple by MynockGuano · · Score: 1

      Hmm, yea. The price is right...

      /duck

  23. the problem is those are well optimized benchmarks by Surt · · Score: 5, Interesting

    The people who work on scientific applications take performance seriously. They put a lot of effort into optimization. The itanium architecture is hard to optimize for, and the compilers just aren't there yet for the general case. So you wind up with a disparity between the performance in scientific applications and general purpose applications.

    Other reasons itanium can't compete:

    1) Compare the performance of itanium with xeon/opteron in running native x86 code.

    2) Compare the costs of building real end user systems.

    3) Compare the availability of windows xp drivers.

    --
    "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  24. interesting by Anonymous Coward · · Score: 0

    Wonder how much of their performance comes from their R&D investment in compilers

  25. A few reasons: by NaruVonWilkins · · Score: 5, Informative

    One, market penetration. Windows *kind of* works on Itaniums. Code has to be compiled specifically for the platform - they're not very good at x86 code through WoW.

    The BIOS replacement they use is not functional. It's very difficult to set up disks for use, and if you lose the disk that the BIOS data is kept on, you're screwed. As far as I know, there is no way to make that fault-tolerant short of manually storing the contents of that partition on another drive.

    Support for the Itaniums has been terrible. The HP systems are riddled with hardware problems, and their support personnel (at the enterprise level) have no idea how to comprehend that they don't operate quite like any other workstation.

    1. Re:A few reasons: by hackstraw · · Score: 1

      The BIOS replacement they use is not functional. It's very difficult to set up disks for use, and if you lose the disk that the BIOS data is kept on, you're screwed.

      Maybe this is a Windows thing, but otherwise, I don't know what you are talking about. To my knowledge, all Itaniums use EFI and not a BIOS. BIOSes are a hippie 70s thing.

      Support for the Itaniums has been terrible. The HP systems are riddled with hardware problems, and their support personnel (at the enterprise level) have no idea how to comprehend that they don't operate quite like any other workstation.

      Again, this may be a windows thing. I've had a very good relationship with HP and our Itaniums. If you consider the problems I have had over the past 2.5 years or so with things like commodity harddrives and memory, which were quickly fixed onsite. I've found HP's support to be exceptional, and the hardware has been exceptional as well. I guess your experience was different.

      Now, what was the topic again????

    2. Re:A few reasons: by NaruVonWilkins · · Score: 1

      I'm using the term "BIOS" here to refer to the EFI system (which I couldn't remember the name of). We've had a number of problems with it - especially because nobody at Microsoft seems to have written remote management apps for power management via EFI.

    3. Re:A few reasons: by bani · · Score: 1

      you do remember microsoft cancelled windows xp for itanium, don't you?

    4. Re:A few reasons: by NaruVonWilkins · · Score: 1

      Yes, in fact, I was working for Microsoft at the time. We're currently using Windows 2003 Server SP1 for Itanium.

    5. Re:A few reasons: by bani · · Score: 1

      i offer my deepest condolences on both counts.

    6. Re:A few reasons: by myukew · · Score: 1

      they're not very good at x86 code through WoW.
      Why would I run x86 code through a *game* anyway? No wonder the performance sucks!

    7. Re:A few reasons: by Molf · · Score: 1

      The parent is joking of course, but for those who actually have no idea what this means, try http://en.wikipedia.org/wiki/Windows_on_Windows

    8. Re:A few reasons: by NaruVonWilkins · · Score: 1

      Thanks - I do appreciate it. It's not exactly a happy situation. I've made a compelling case to switch over to AMD hardware, and if sales pick up in this quarter there's a chance we'll have the budget next year.

  26. What market was it aimed at? by tolkienfan · · Score: 1
    I think the issues are:
    1. It was aimed at a saturated market that wasn't about to make a big-time investment in changing architecture.
    2. The slow momentum gave it a bad name.
    Of the two, I believe the latter is the more damaging.
  27. It's simple... really by rtkluttz · · Score: 2, Insightful

    People don't want a processor whose main purpose in life was to artificially refresh Intels control on much of the Intellectual Property associated with the processors. AMD is getting too close, so they change everything and hope to charge royalties.

    --
    Digital is, by definition, imperfect. Analog is the way to go.
  28. Quick Research by MikeSty · · Score: 0

    I google'd "Itanium Problems" and found several reasons as to why the Itanium doesn't gain much respect. Rather than post tons of links and issues, I'd advise you to click your new google toolbar and search away :D

  29. It's the integer performance by GGardner · · Score: 3, Informative

    While, the IA64 has always had great floating point performance, there's an awful lot of us out here that don't need fast FPUs -- e.g. code development, database, web serving, network i/o etc. Sure, IA64 is a winner for the teraflop oriented supercomputing community, but for the rest of us, integer performance matters more. And for price/performance, x86 and x86_64 beat ia64.

    1. Re:It's the integer performance by hackstraw · · Score: 1

      While, the IA64 has always had great floating point performance, there's an awful lot of us out here that don't need fast FPUs -- e.g. code development, database, web serving, network i/o etc.

      1) Code development. Well, being that the compiler does most all of the optimizations on the IA64 platform, and compilation takes a long time because of this, well, developers will just have to make good Makefiles and wait on long compiles like they always have.

      2) Database. Its good to have contiguous large (> 2Gigs) of RAM on a process. Its good to have fast disk IO (independent of CPU). Its good to have high memory bandwidth. Itaniums are pretty good for the job, and aside from number crunching, databases are the #2 use for Itaniums.

      3) Web serving -- hmm, usually web servers are IO or database bound. See #2 for databases, but I think anyone using an Itanium as a dedicated web server would be pretty dumb.

      4) network IO -- not an issue for Itaniums.

    2. Re:It's the integer performance by Anonymous Coward · · Score: 0

      1) Code development. Well, being that the compiler does most all of the optimizations on the IA64 platform, and compilation takes a long time because of this, well, developers will just have to make good Makefiles and wait on long compiles like they always have.
      Nobody is going to pay a developer to sit and twiddle his thumbs for long compiles if there's an alternative. That long compile wait is lost productivity. So the developer works on a more productive platform and IA 64 is, at best, an afterthought. That stunts your developer mindshare right there, and if Microsoft has learned one thing correctly besides marketing, it's to keep your developers happy.
      2) Database. Its good to have contiguous large (> 2Gigs) of RAM on a process. Its good to have fast disk IO (independent of CPU). Its good to have high memory bandwidth. Itaniums are pretty good for the job, and aside from number crunching, databases are the #2 use for Itaniums.
      Databases are integer workloads, and AMD64s give you almost the same 64-bit integer performance as Itanic for a small fraction of the price. All the other things you mention for databases (fast disk I/O and large physical memory capacity) are available for AMD. This was the market Intel was hoping would push Itanic's growth in the business sector, but nobody aware of the technical merits of the two platforms, as opposed to the marketing hype, (which unfortunately does exclude some CIOs and IS directors) is going to pick Itanic for this workload in the future.

      So that leaves Itanic as a small (FP/HPC) niche market player which will never recoup its R&D costs, and as the laughingstock of the industry.

    3. Re:It's the integer performance by GGardner · · Score: 1
      2) Database. Its good to have contiguous large (> 2Gigs) of RAM on a process.

      Yup.

      Its good to have fast disk IO

      Yup.

      Its good to have high memory bandwidth.

      Yup.

      IA-64 does well enough in all these areas, but not well enough to justify the price differential. You can do just about as well in all three of these categories with x86_64, and Intels Iem64t cpus, for a lot less money.

      Now that there are 64-bit commodity-class CPUs, ia-64 has to compete on more than 64-bitness.

    4. Re:It's the integer performance by iggymanz · · Score: 1

      more laughter for HP getting rid of three architectures which are primarily used for business computing (non-floating point, non-vector), thinking they could force the customers of nonstop-mips, hpux-parisc, and vms-alpha to go to pricey, unproven, largely unsupported by vendors and poorly performing itanic. The customers are staying away in droves.....

  30. Apple and Itanium by ndansmith · · Score: 1

    Dvorak speculated in 2003 that Apple would indeed switch to Intel and that they would use the Itanium line rather than x86. That does make sense, because it would mean a high quality Intel processor without much risk of homebrew Macs.

    1. Re:Apple and Itanium by jellomizer · · Score: 1

      But it seems all the development software that cross compiles makes x86 code. The test development systems have p4s in them. It would make no sence to give developers test systems to make compatible applactions for a chip that isn't optimised for it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:Apple and Itanium by digidave · · Score: 1

      Yeah, that makes a lot of sense. Macs with even higher price tags that suck at integer operations.

      --
      The global economy is a great thing until you feel it locally.
    3. Re:Apple and Itanium by Anonymous Coward · · Score: 0

      They're not going to be using anything close to Itanium processors, Dvorak's still wrong in that regard.

    4. Re:Apple and Itanium by Massacrifice · · Score: 1

      Did Dvorak also happen to think that Intel would go out of their way to make an iBook friendly version of Itanium?

      I didn't think so. Itanium doesnt scale that low, at least, not for now.

      The only non-x86 chips Apple will use for Intel are the XScale CPUs, for future iPods.

      --
      -- Home is where you eat your heart out.
    5. Re:Apple and Itanium by Jeremy+Erwin · · Score: 1

      One of the advantages of the MacoSX environment is that the programming tools are free, often in both senses of the word.

      Does gcc produce fast Itanium code? If not, how much would it have cost Apple to bundle in a good VLIW compiler with their systems?

    6. Re:Apple and Itanium by Anonymous Coward · · Score: 0

      Unfortunately for you and dvorak, last time I checked the apple guys (was it Jobs that said it?) said they were switching to quote "x86". Last I checked, thats not itanium. All you mac lovers trying to find a shred of news that means that mac will be better than standard intel desktops are grasping at straws.

  31. It's a pain in the ass by unsinged+int · · Score: 5, Interesting

    to compile for Itanium. Speaking as a compiler researcher, Itanium is great for generating research papers because there are all sorts of things that you can do from a compiler perspective. The problem is, outside a research environment, someone has to implement a lot of the ideas in an Itanium compiler to make it useful. Unfortunately, most of the stuff in the Itanium research papers isn't easy to implement and most of what gets put into commercial compilers are the easily implementable ideas.

    1. Re:It's a pain in the ass by Jeffrey+Baker · · Score: 5, Interesting

      Yeah, nice CPU, difficult for software authors. I read a paper recently wherein the authors managed to reduce L4 microkernel message passing (up to 8 bytes) to 36 clock cycles, which is far faster than any other platform. But this was done by hand, and the compiler blurted out a routine that required 508 cycles. The gulf between what you can really do with an Itanium, and what normal software writers can do with it, remains huge.

    2. Re:It's a pain in the ass by multipart · · Score: 1

      This is so true!

      Add to that the near-total lack of participation and support from HP and Intel for third-party compilers, and you know why so few good IA-64 compilers (if any) exist.

  32. Feel good factor by jellomizer · · Score: 3, Insightful

    Why anything doesn't get the respect that it is due. It is because people don't want to give it respect. The Unix People go Well Sun Ultra Sparc (Or any other of the 64 bit Unix platforms) has be 64 bit for many years before the Itanium. The Apple crowd went well the Power PC is now 64 bit (although this is changing, and may possibly give Itanium some respect). The windows users are afraid of Itanium because it may break a lot of compatibility in their legacy apps. The Linux users are afraid of a complete Intel Dominance and put their development efforts to AMD 64bit chips. It is a state where you see the old king dieing and this is your only opportunity to get a change in government before the kings son gets in power. Why doesn't FreeBSD get the respect it deserves, or why doesn't Python get the respect it deservers. The winner is not always the best or even close to the best, the winner is often the one that people feel good about.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Feel good factor by Ubergrendle · · Score: 1

      Mod parent up. A comparable example was microchannel architecutre by IBM... it certainly beat the pants of the ISA bus of the day, but it was proprietary and the genie was out of the bottle...the market opted otherwise.

      Only now, years and years after Itanium was supposed to rock our worlds, is the Itanium2 now available in quantity at competitive prices...and I attribute that to the presence of a solid AMD Opteron offering.

      If I was building a supercomputer I'd pick the Itanium2 based on the performance identified, but for most of my other datacentre tasks I can get away with better alternatives.

      --
      John Maynard Keynes: "When the facts change, I change my mind. What do you do?"
    2. Re:Feel good factor by DSP_Geek · · Score: 1

      Microchannel was a joke. You needed some serious glue logic to get onto the bus, no worse than PCI, but at the time there were no off the shelf interface chips so you ended up using a lot of card space, which was in short supply since the cards themselves were quite a bit smaller than the standard AT form factor. All in all you could count on having maybe 55 to 60% of AT card space to play with, all this before surface mount silicon was readily available.

      This made expansion cards more expensive, and adding in the licence fees IBM charged manufacturers set the price of a system+cards beyond most markets, especially when competing AT-bus boxes had a much broader selection of accessories. One or the other extra expense would've been doable given IBM's decent reputation at the time, but both together passed people's squick threshold.

  33. Mass Market Trouble by sigloiv · · Score: 2, Insightful

    With a single-CPU Itanium2 system at around $2000 their price is already reasonable, and the price would come down (and software would be ported) if the Itanium ever became a mass market chip. Well, it's sort of like Linux. The only way it people will use it is if it's already a mass market chip, but it will never become a mass market chip if people don't use it. Sort of an infinite loop.

    --
    Software is like sex. It's better when it's free. -Linus Torvalds
  34. Why as why by D3 · · Score: 2, Interesting

    May as well as why Linux/Mac/*BSD/etc. doesn't get the "respect it deserves." There is no real answer.

    My personal thought is that price:performance was not in line with other choices available to the end consumer.

    --
    Do really dense people warp space more than others?
  35. Because by unixmaster · · Score: 1, Interesting

    Itanium is broken by design. Its asm syntax etc is different from amd64 on *purpose* which was to create to incompatible 64bit system where Intel would keep AMD out of the market. Oh well, they failed badly.

    --
    Never learn by your mistakes, if you do you may never dare to try again
    1. Re:Because by wangmaster · · Score: 2, Informative

      That's a neat trick. Considering the AMD64 architecture was released about 2 years after the first Itanium.

      While you're right that Itanium was meant to keep AMD out of the market by essentially creating a new "proprietary" architecture, it's hardly made to be different from amd64 "on purpose" since they didn't really have any clue what amd64 was (since it didn't exist).

    2. Re:Because by 21mhz · · Score: 1

      Its asm syntax etc is different from amd64 on *purpose* which was to create to incompatible 64bit system where Intel would keep AMD out of the market.

      I can't see your logic here. How ould that possibly keep AMD out of the market?
      And, is this your only argument as to how Itanium is "broken by design"?

      --
      My exception safety is -fno-exceptions.
    3. Re:Because by multipart · · Score: 1

      The parent poster is wrong. IA-64's assembler syntax _has_ to be different from the AMD64 syntax because it is a totall different architecture with a completely different instruction set and many features that no x86* chips have. For example you need to mark bundles and add stop bits, and so on. So what the heck is the parent poster talking about. Flaimbite, if you ask me.

      FWIW, the IA-64 assembler syntax (at least the form used by the GNU assembler) is much easier than all x86 and AMD64 assembly I have seen and worked on.

    4. Re:Because by cant_get_a_good_nick · · Score: 1

      This is a bad argument. It's a brand new chipset that's supposed to be a clean break from ia32, whereas AMD did the more evolutionary approach in creating x86-64 (now generally renamed AMD64). Do you congratulate Motorola for it's input in PowerPC creating a new desktop class RISC chip, or do you fault them for creating something incompatible with 68K. THere are sometimes you need to break compatibility

    5. Re:Because by bani · · Score: 1

      thing is, powerpc really was a huge performance win over 68k. it also was not much more expensive than 68k

      itanium is not a huge performance win over x86. in many cases it is a huge performance loss. and it is supremely expensive.

      intel has been beating the itanium dead horse for over a decade now.

  36. Bias by Anonymous Coward · · Score: 1, Insightful

    The first Itanium was too late, too slow, and too costly. This led to a bias being developed against it based purely on misinformation. Don't forget to factor in the typical hypocritical resentment of Intel...

    People are always complaining about X86 for its legacy cruft yet when Intel designs a bold new architecture based on an extension of the VLIW approach, they get slammed for ... wait for it ... poor legacy compatibility. Legacy support is certainly a valid and very important issue but why must people constantly hammer away at this when considering the Itanium at face value: A very capable high-performance processor which would be ideal for UNIX workstations, servers, and supercomputing applications.

    The biggest drawback of Itanium is the fact that it's a proprietary architecture. But then again, so were Alpha and PA-RISC. POWER and SPARC might not technically be so but if you want workstation-class POWER CPUs, you've got no choice but IBM (I don't see anyone else jumping on the PowerPC bandwagon and producing competing compatible chips) -- with SPARC there's just Fujitsu and Sun's inferior offerings.

    But looking at the architecture for what it is, people should be excited about Itanium. It's new, it's fresh, it's fast, and it's interesting. Certainly far more interesting (and challenging) than RISC with a lot of unexploited potential.

    1. Re:Bias by TheRaven64 · · Score: 1
      if you want workstation-class POWER CPUs, you've got no choice but IBM

      Maybe right at the top end. Slightly lower down, you've got FreeScale. Then you've also got things like some of the Xilinx boards, with a few PPC cores and and FPGA in a single package.

      --
      I am TheRaven on Soylent News
    2. Re:Bias by Anonymous Coward · · Score: 0

      Ah but Freescale focuses on the embedded market. For general purpose and high-performance computing, only IBM has the resources to continue the POWER/PPC line. So realistically speaking, when we discuss the Itanium and its target market, the POWER architecture is also a proprietary architecture for all practical purposes.

  37. Yeah, Itanium tanked... So what? by 2$+Crack+Whore · · Score: 1

    I guess because (for some moronic reason) AMD are "good guys" and Intel are "bad guys" we just have to get all giggly and rub their noses in it. Shit happens. Sometimes you win, sometimes you lose. Some products take off, some don't. Itanium looks like a good architecture for transaction processing, at least on paper. Turns out the market was more interested in backwards compatibility.

  38. Poor Assembly language design by SirCrashALot · · Score: 2, Interesting

    My systems professor told us that they chose to create a very complicated assembly language, that while may be efficient, makes programming un-nesceissarly difficult. If people don't want to program on your platform, you have a problem.

    1. Re:Poor Assembly language design by dj_whitebread · · Score: 1

      IA64 assembly was never meant to be written by a human. It is a processor design driven by compiler research.

    2. Re:Poor Assembly language design by Dogtanian · · Score: 1

      My systems professor told us that they chose to create a very complicated assembly language, that while may be efficient, makes programming un-nesceissarly difficult.

      What do you mean by difficult to program?

      I am not an EE (so correct me if I'm talking out of my backside), but I assume he was talking about the processor relying on effective compilers (lo and behold, a post a couple of screens down says exactly this...)

      Although I understand that some assembly (i.e. machine code in human-readable form) programming is still required for certain embedded systems, I'd assume that the Itanium was never intended for that particular application.

      Yeah, it's nice to be able to say you've written a program in assembly language for your PC (I've done some *very* basic stuff), but I can't see that being an issue here.

      While we're on the subject, I'm not surprised that Intel would like to wipe the slate clean of the x86 architecture; from what I know of it, it must have been a major nightmare to improve performance whilst supporting all that baggage.

      Question is, how big a "free lunch" did Intel get when they switched cores from CISC (Pentium I) to RISC (Pentium Pro/Pentium II onwards)? Assuming RISC is reliant on compiler optimization, that would still mean some tricky optimization of the CISC x86 code before it was passed to the RISC unit for execution....

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  39. Because this is /. by Anonymous Coward · · Score: 0

    where AMD rulz, and Intel is teh sux!

    1. Re:Because this is /. by Anonymous Coward · · Score: 0

      Ah, yes, the counter-propaganda! "Holy shit! A lot of people on /. likes something! I'm going to go ahead and be a jackass and mock them, just because they're obviously wrong!"

      Until you realize that it's a bunch of people with their own opinions - opinions that are just as fallable as yours! Imagine that.

      So go ahead and patronize some more. It's really fucking worthwhile. Really. It's almost not as trite and pathetic as a "punk", raging against the system.

      Okay, I lied, it's even worse. At least punks came up with some fun music.

  40. Not to be a complete troll, but... by llamalicious · · Score: 1

    Linking to an article from over 1 year ago (April 19, 2004) while discussing pricing doesn't make me think the submitter went through any trouble to look up more current information on the Itanium series.

    A quick trip even to Google News

    While I understand they were trying to make a point about entry level pricing, lets at least have some current information to work with.

  41. Itanium by myrick · · Score: 5, Informative
    Itanium is definitely a brilliant architecture in many ways, and lessons will have to be learned from it some day. It takes a little history to know why it's called "Itanic," however.

    The Itanium was designed to change the way processors worked. Most processors today are some sort of dymically scheduled behemoth that are capable of detecting instruction collisions on the fly, and reordering instructions for optimal parallelism and thus performance in the light of those collisions. Itanium takes a completely different approach. It is an extremely wide processor that has absolutely no collision detection or reordering. All of the work in this respect is placed on the compiler's shoulders. In theory, a good compiler could make this chip very, very fast, and in reality, as you see, this can be the case. So why did it fail? Intel hyped the hell out of this processor, and then missed their release date by a full two years. That is microprocessor suicide in the land of Moore's law. So, when Intel delivered a chip too late that failed to perform the way they marketed it to, the chip died. In recent years, Itanium has really come around, but it's hard to escape your past in this industry.

    Other relevant problems for adoption are tied to this need for a good compiler. Making a compiler as smart as it needs to be for Itanium to live up to its potential is not cheap, and Intel is not known for just giving away such technology. I'm sure the fees to license Intel's compiler are nontrivial, and that does not encourage development. Realistically, Itanium will never become a desktop chip just because of the massive adoption effort that would go into such a switch.

    One thing to note, however, is that other chips aren't that far away. You suggest that a 2ghz or 3ghz Itanium would be incredibly fast, and I agree, but I seriously doubt Intel can ramp it that fast. Also, the Opteron specs you show are for 2.0ghz, and I believe Opteron is up around 2.6 or 2.8 ghz nowadays.

    Ultimately, Itanium is a great design, but wrapped in a poorly executed initial implementation. It does teach a good lesson that compilers can really help improve chip performance, and down the road, architectures that take this into account may reign supreme. But I wouldn't look to Itanium to do any more than instruct us for the future. She is not a desktop chip.

    --
    I'd rather be cycling.
    1. Re:Itanium by TheRaven64 · · Score: 1
      Most processors today are some sort of dymically scheduled behemoth that are capable of detecting instruction collisions on the fly, and reordering instructions for optimal parallelism and thus performance in the light of those collisions

      Note that the PowerPC chips found in the next generation consoles and the UltraSparc don't do out-of-order execution. It seems that compilers are beginning to catch up to the point that the performance gain is not that significant.

      --
      I am TheRaven on Soylent News
    2. Re:Itanium by myrick · · Score: 1

      Absolutely, but at the same time, it has a lot to do with other parts of the architecture. Reordering is pretty critical for a deep pipeline like the Pentium 4 because you can't afford to sit and wait for 20 cycles to get your add result back. It is similar to branch prediction in this way. The shorter your pipeline, the less important reordering and branch prediction are for the hardware, especially if, as you point out, you can get a compiler that avoids nasty dependencies and hard-to-predict branches. PowerPC has a fairly short pipeline (rough guess, 12 stages?) whereas the current generation of Pentium 4's checks in at somewhere around 32 stages (these numbers are educated guesses -- I really can't remember off the top of my head), and thus dynamic scheduling is much less important. This comes at the expense of clock speed, but it's clear that too is becoming less of an issue.

      --
      I'd rather be cycling.
    3. Re:Itanium by Anonymous Coward · · Score: 0

      I would agree that it has a brilliant design.
      I haven't seen an architecture that allows so much improvement through optimization. It's already a fast chip but you can do absolute wonders by tweaking it.

      We have a dual Itanium2 at work running HP-UX, it's awesome for development and it's our 2nd fastest machine. Even with newer machines with greater GHz coming along the Itanium2 holds it's own against them. Per GHz it's the faster we have and we have machines from Compaq Alpha, PA-RISC, Power4, Power5, Opteron, SPARC.

      I'm still a big Alpha fan, and a big 64-bit only fan, so the Itanium2 gets a lot of respect for it's speed. I didn't think much of the original Itanium we had, it was fast but just not good enough and that disappointed people and the press.

      One good thing for configurability but bad for GCC was that writing a compiler for it is very difficult. That keeps GCC from being amazing on it and puts some people off.

      I think Intel should improve it more and reduce its's power requirements.

    4. Re:Itanium by adam31 · · Score: 1
      In theory, a good compiler could make this chip very, very fast, and in reality, as you see, this can be the case.

      There is a lot of code a compiler just can't make fast. Code that will run fast has to be designed that way-- sequential memory access, predictable branches (or no branches), processing on multiple pieces of data at a time... Simply recompiling branch-heavy cache-agnostic pointer-aliased code with a smarter compiler will not give you huge gains.

      And the reality, as we can see, is that the chip can run fast... but it takes forethought, like the kind chip makers use when writing benchmark code.

  42. Many reasons.... by loony · · Score: 5, Informative
    Well, I can talk only for myself but...
    • Windows on itanium is a joke... What software are you going to get running well there? We tried it and 80% of the software we needed to certify a new OS wasn't there.
    • HP-UX is better off but still - if you have any legacy software at all in your system you're screwed.
    • Linux is doing alright - but if you use a Itanium box running Linux and pit it against new xeon with the same number of CPUs, the Itanium looks like a dog...
    • Most business apps are integer processing - itanium doesn't look that great in the int benchmarks...
    • I'm frankly just tired of hearing about it... Since 7 years we hear that itanium is going to be the future and all - hasn't happened yet and I doubt it ever will at the pace its moving. Why port to a platform that already feels dead before it even took off?
    • You can't compare a Xeon and an Itanium box by the per cpWe already support 5 different platforms - why would I want to add a 6th one if the performance gains are going to be pretty meger...

    Peter.
    1. Re:Many reasons.... by ivan256 · · Score: 1

      The X86 compatability increased boot times.... into the dozens of minutes.

      The boot time on a server with 4 Itanium processors and 64GB of memory was over an hour for a long time after the platform came out. Vendors that rely on selling a five-nines support contract with every server to make their margins couldn't do that with a server that has been down 0.001% of the time before it's even finished booting up.

  43. The name may have something to do with it... by dloflin · · Score: 1

    Why do we see so many disparaging opinions of the Itanium processor (all those 'Itanic' jokes, etc.)?

    Uhh, maybe because of the really stupid sounding name? It always sounds to me like something's been left off the name (ie the "Ti.." part). But of course they couldn't trademark "Titanium".

    Naming is important - IMHO, a big reason why many open source programs do not get used in corporate environments is due to odd/wierd names. Many otherwise worthy programs are never considered or evaluated, due to "silly" names, I believe.

    So if the name's a joke...maybe the processor is seen as a joke, too...I remember it was seen as the "next big thing" and there was lots of excitement & buzz about it, before it got the silly name...then it sort've dropped off the radar...

    1. Re:The name may have something to do with it... by Anonymous Coward · · Score: 0

      Wow. That's the stupidest thing I ever heard... I award you no points and may God have mercy on your soul.

  44. Re:because it's a failure by pete-classic · · Score: 1
    Also, I'd be willing to bet Intel staked a bigger part of its decision on the availablity of platform independent binaries making serious inroads, which hasn't really materialized.


    I'm hazy on what you mean by "platform independent binaries". Are you talking about .NET? Java? Some other thing I'm ignorant of?

    -Peter
  45. Two words by overshoot · · Score: 4, Insightful
    No applications.

    Microsoft apps are nonexistent, and open-source apps tend to have crappy performance due to the fact that IA-64 depends overwhelmingly on compiler optimization. Developers can use Intel's compiler, but it requires work to use with most Linux systems (the only other platform that supports IA-64 besides MS, AFAIK).

    Net result: no applications => no uptake, QED.

    Egg, chicken, all that.

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
    1. Re:Two words by Anonymous Coward · · Score: 0

      (the only other platform that supports IA-64 besides MS, AFAIK)

      SGI Irix, FreeBSD and NetBSD run on IA64.

    2. Re:Two words by PygmySurfer · · Score: 1

      HP-UX and OpenVMS are supported on IA-64, as well as FreeBSD and NetBSD (and maybe others).

    3. Re:Two words by PygmySurfer · · Score: 1

      SGI Irix, FreeBSD and NetBSD run on IA64.

      SGI has pretty much abandoned IRIX, and it doesn't run on anything other than MIPS.

    4. Re:Two words by Anonymous Coward · · Score: 0

      HP-UX runs on Itanium, and is probably a bigger share of the IA64 market than Linux.

  46. FLOPS isn't enough by timster · · Score: 5, Insightful

    You have floating-point listed there, which is great for science I'm sure, but where are the integer numbers?

    --
    I have seen the future, and it is inconvenient.
    1. Re:FLOPS isn't enough by ScriptMonkey · · Score: 1

      The reason for integer performance not being listed, is that it would undermine the article's thesis. All Itanium implementations have had AWFUL integer performance.

      When a Xeon box costs less, and performs better at integer heavy tasks, there's little motivation to shell out the bucks for an Itanic.

    2. Re:FLOPS isn't enough by ActionListener · · Score: 1

      Actually, flops is enough. Of course there are applications that could still benefit from better integer performance. However, most of the CPU intensive programs that I use are more floating point intensive. For example, my Athlon 64 3000+ is not quite powerful enough to decode 1080p HD content in real time. I would say that most of the software that "normal people" use is more numerically intensive than integer intensive. If general purpose CPUs had better floating point performance, we wouldn't need special purpose GPUs for 3D rendering. My office software (which only needs good integer performance) already runs fast enough.

    3. Re:FLOPS isn't enough by ergo98 · · Score: 2, Insightful

      For example, my Athlon 64 3000+ is not quite powerful enough to decode 1080p HD content in real time.

      Decoding video is a largely integer task. In fact, outside of a couple of iterative floating point benchmarks, there are very few tasks that aren't seriously impacted by a subpar integer unit.

      If general purpose CPUs had better floating point performance, we wouldn't need special purpose GPUs for 3D rendering.

      If GPUs had better and more general purpose, integer units, we wouldn't need a general purpose CPU for running Office! Pretty vague and empty statement.

    4. Re:FLOPS isn't enough by Anonymous Coward · · Score: 0

      I would say that most of the software that "normal people" use is more numerically intensive than integer intensive.

      You would say that, but without any evidence to back it up.

      For example, my Athlon 64 3000+ is not quite powerful enough to decode 1080p HD content in real time.

      Video encoding/decoding is all integer, so Itanic wouldn't help you here.

      If general purpose CPUs had better floating point performance, we wouldn't need special purpose GPUs for 3D rendering.

      In order to eliminate GPUs and get equivalent performance with software rendering, you'd need over 10x the FP performance of a high-end x86. Itanic can't provide that.

    5. Re:FLOPS isn't enough by Anonymous Coward · · Score: 0

      Itanic is decent for poorly structured floating point intensive calculations. For the highly structured floating point calculations you are alluding to, which doesnt include video codecs as someone else mentioned, it is hopelessly inefficient.

      GPUs get a magnitude more of peak FLOPS out of a mm2 of die than Itanic.

  47. Thread on the same question at RealWorldTech.com by Anonymous Coward · · Score: 0

    I asked the same question at RealWorldTech.Com about 6 months ago and got a fair number of replies - several of which I thought were fairly insightful.

    http://www.realworldtech.com/forums/index.cfm?acti on=detail&PostNum=2978&Thread=1&entryID=43600&room ID=11

    You can see the full thread at the bottom of the linked page.

  48. Itanium? by Anonymous Coward · · Score: 0

    Is that some new Itanic chip?

  49. Itanium Powering HP/Tandem NonStop Platform by ledbetter · · Score: 1

    I'd say the Itanium is getting a bit of respect in the highly available/high performance arena, with the HP/Tandem NonStop Platform moving to Itanium

    1. Re:Itanium Powering HP/Tandem NonStop Platform by cant_get_a_good_nick · · Score: 2, Insightful

      Not so much respect as a "we have to" thing.

      Itanium was supposed to be the new base chip, the thing to finally replace x86. Picture high performance and high volume, the other RISC guys weren't supposed to be able to compete. SGI and DEC cowered, shutting down ALPHA and MIPS.

      HP decied they wanted in on Itanium early. They partnered with Intel on chip design. Intel designed the first chip, while HP's was the much more highly regarded Itanium II. They bet the farm on it, in some ways more than Intel itself, phasing out PA-RISC, and now trying to force people to move off of Vax and Tandem onto Itanium. They pretty much have no choice, having fired the other processor guys they had.

      If you want to hear about respect, how about HP, the #1 Itanium vendor, killing off workstation class Itanium computers. If this isn't a white flag, resigning the chip into a nice market, i'm not sure what other interpretation there can be.

  50. It's the upgrade path, stupid by Anonymous Coward · · Score: 0

    The Itanium is the hardware equivalent of this Joel on Software parable, and a close relative to IBM's biggest blunder.

    AMD64/EM64T provides a solid upgrade path from x86, whereas the horrible x86 perfomance of the Itanium (first in hardware, then in software) makes it a clean break. In the real world, where we depend on cheap, commodity x86 server hardware and applications, a clean break to a more expensive, incompatible, unproven platform was just not attractive to customers.

    And don't discount the AMD factor. Even Intel-only shops benefit from the price and performance pressure any measure of competition in the x86 market provides. Moving to an Intel-only platform would remove the last barrier to permanent hardware lock-in.

  51. Too much hype, too long to deliver by stienman · · Score: 4, Insightful

    The itanium is an amazing architecture with so many performance boosting upgrades that it would have blown everything out of the water.

    If it came out on time.

    It was so late that by the time it came out it was still better than existing processors, but not by a large enough margin to justify its cost.

    As the clock speed goes up, and as the other processors find their limitations and drop out of the race, the Itanium will look better and better. There is, however, a large investment in time and software that must be made before it becomes truly useful. It is unlikely that MS is going to support more than one architecture simultaneously for the desktop or server as it tried to do for x86/alpha.

    The big marketing push and the number of companies signing on to the good ship itanic coupled with the constant pushback of the release date caused Intel to lost a lot of the press attention they should have received when it did come out.

    It'll be interesting to see what happens over time, especially as Intel wants it to be a server chip.

    Of course, this could all be a big leadup to the announcement that Apple is going with the Itanium.

    -Adam

    1. Re:Too much hype, too long to deliver by Anonymous Coward · · Score: 0

      Here are some other reasons that Itanium did not
      take off.

      1) The processors forced a recompile of code which did not appeal to HP-UX PA-RISC customers.

      2) New versions of database software would be required from Oracle, so as a result the cost was not just a hardware expense, but a software expense also. Renegotiating licenses with Oracle is a pain in the rear, to say the least.

      3) the PA-RISC roadmap keep getting extended, so the presure was not on HP-PA customers to upgrade.

      4)HP's competition would not embrace this as an industry standard processor since it seemed that HP benefited the most from this happening.

    2. Re:Too much hype, too long to deliver by femtoguy · · Score: 1

      I think that Intel's real problem is that it did not count on competing with AMD. When they started the Itanium project, it was slated to come out at faster clock speeds than the Pentium II chips. By the time they released it, AMD had produced 1 GHz chips, and Intel had to follow. In the end the choice between a 2.0 GHz Pentium 4 and an 800 MHz Itanium made it look bad.

      The bigger problem, though, was the software support. If you want to run Windows, don't bother. If you want to run Unix, you have a lot of choices, of which Intel is only one. If Microsoft had quickly released a highly optimized version of Windows NT/2000, that showcased the Itanium's strengths, the story might have been different. The is especially interesting in light of the big new story of the last few months. I believe that Intel has made major concessions to get Apple to port OSX to Intel to guarantee that there is no repeat of the Itanium episode. Apple engineers are known for using every little feature of a CPU to get maximum performance. Microsoft is known for trying to write as little new code as possible. Imagine that Intel produces the Itanium 3 tomorrow. Microsoft will do as they always have, and do a minimal make to get a working version. Apple will produce a highly optimized version of OSX that will look and run great. Microsoft is now in the position of either having to build a good version to keep up, or admit that they are incompetent programmers.

      I believe that this is the biggest reason that Intel has been a big supporter of Linux, and why they have supported Apple in the transition.

    3. Re:Too much hype, too long to deliver by Ciel · · Score: 1

      As the clock speed goes up, and as the other processors find their limitations and drop out of the race, the Itanium will look better and better. There is, however, a large investment in time and software that must be made before it becomes truly useful. It is unlikely that MS is going to support more than one architecture simultaneously for the desktop or server as it tried to do for x86/alpha.

      That was said about every other rival architecture to x86 - and every single one of them has either been marginalized or killed off.

      The brute fact of the matter is that a chip's ISA just isn't that important to its performance. When the limitations of an x86 chip's microarchitecture become too great, its designers are free to create a new one and slap on a (now cheap) x86 decoder. If they need a few more instructions, they add them.

      Because we tend to classify microprocessor hardware by its ISA, it's easy to lapse (perhaps even subconsciously) into believing that chips of a common ISA must necessarily share some deep hardware heredity. But they don't have to, and history teaches that microprocessor hardware innovations are largely orthagonal to ISA. Most of the improvements to IA-64 chips will probably benefit regular CPUs as well (for an interesting parallel, consider Linus's comments re: Monolithic vs. Micro kernels). And with the absurd amount of money pushing x86 development, such improvements won't take long to trickle down either.

    4. Re:Too much hype, too long to deliver by antrik · · Score: 1

      > Most of the improvements to IA-64 chips will probably benefit regular CPUs as well

      I doubt it. Most of the improvements of IA64 are actually inherently bound to the ISA. They either do not work or do not make any sense on something like x86.

      > for an interesting parallel, consider Linus's comments re: Monolithic vs. Micro kernels

      I'm not sure this is a good parallel. While in theory every optimization introduced in a microkernel system could be also done in a monolithic one, only the reduced complexity and higher flexibility of microkernel system make many optimizations feasible in practice. I've no idea how you want to transfer this finding to processor architectures... :-)

      --
      All my comments get moderated +-0, spotless.
  52. No Ecosystem by Skjellifetti · · Score: 1

    Why do we see so many disparaging opinions of the Itanium processor (all those 'Itanic' jokes, etc.)?

    The jokes are not about Intel's processor so much as they are about Intel the company. Intel nearly bet the farm on the Itanium and for a while, it looked like that bet might sink the company. Too many folks have too much invested in x86 software and the Itanic had a bad rep for running those x86 apps compared with AMD's 64 bit x86 style CPUs. A new processor family can't expect to succeed based only on its speed. You have to consider the (warning, buzzword) ecosystem based around that processor. Itanium has the failed to become a mass market CPU for the same reason that sparc, mips, alpha, and others have. PPC seems to have done a better job by grabbing a large chunk of the game console market to complement or even overshadow its use in servers.

  53. guess again, Itanium 2 is really high. by Anonymous Coward · · Score: 0

    The SGI Altix at #3 is Itanium 2 also.

  54. Itanium was no failure. by team99parody · · Score: 4, Insightful
    From a business point of view, it was quite the success.

    When Itanium started, Intel was absolutely nowhere in 64 bit and high-end computing. Thanks to Itanium, over half Intel's competitors simply walked away from the market with little more than a few press releases from Intel.

    Consider that at the time, you had Alpha (Dec), PA-RISC (HP), MIPS (SGI), and Sparc as leading 64-bit computing platforms.

    HP in it's infinite wisdom was suckered the worst - giving up their own leadership position just to be strung along for many years in Intel's PR bluff. However Wall Street loved the "ooh, intel's story's so aWsUM that even HP is giving up" that SGI spun off and MIPS gave up on the high-end space; and Dec->Compaq->HP undervalued Alpha and it went away.

    This has to be the most successful come-from-zero-to-wipe-out-half-the-market story in the history of computing. How can it be considered a failure.

    1. Re:Itanium was no failure. by markhahn · · Score: 1

      indeed, as a monopoly-building tactic, it was a great success. though you could easily argue that the other processors were in their final stages of death anyway, since ia32 and eventually amd64 would certainly have killed them off.

      Alpha was a great chip (I still run hundreds!), but was flushed because HP was afraid of Dell.

      PA-RISC, MIPS and SPARC had nothing going for them - no competitive advantage, certainly not over AMD64. they were each tied to old-fashioned name-brand-Unix machines, which are now thankfully extinct.

    2. Re:Itanium was no failure. by danheskett · · Score: 2, Insightful

      It's a failure because Intel shrunk the market,. and doesn't sell any chips. Reducing competition is only half the battle.

      The number Itanium chips shipped is usually reported in hundreds, not the hundreds of thousands they anticipated.

      I can't find the numbers probably because Intel would be embarrased, but they've likely spent billions on development, with little appreciable sales.

      Sparc, as far as I can see, drastically outsells Itanium.

    3. Re:Itanium was no failure. by Anonymous Coward · · Score: 0
    4. Re:Itanium was no failure. by Sparohok · · Score: 2, Interesting

      PA-RISC, MIPS and SPARC had nothing going for them - no competitive advantage, certainly not over AMD64. they were each tied to old-fashioned name-brand-Unix machines, which are now thankfully extinct.

      PA-RISC, MIPS, and SPARC were killed off by the mere threat of Itanium about 5 years before AMD64 first shipped. MIPS scrapped Beast and Capitan back in 1998. AMD64 was barely a glint in its designers' eyes at that point.

      We'll never know if they would have been competitive. However, the one company that didn't shitcan their 64 bit RISC development, IBM, now holds a dominant position in high performance computing. Someone clearly thinks they have a competitive advantage or they wouldn't be selling supercomputers.

      Martin

    5. Re:Itanium was no failure. by Anonymous Coward · · Score: 0

      You don't know the history. Itanium is more a HP chip than a Intel chip.

    6. Re:Itanium was no failure. by SpryGuy · · Score: 1

      And let's not forget the poor (superior) Alpha chip. I guess it's still in its last death throes right now, but still...

      A lot of potential was killed and/or never realized over the last decade...

      --

      - Spryguy
      There are three kinds of people in this world: those that can count and those that can't
    7. Re:Itanium was no failure. by Anonymous Coward · · Score: 0

      HP was hardly chased off -- the Itanium is their own damn design. Intel bought it when HP decided to abandon it. They tinkered on it for years and years, and finally released it, and it was already obsolete.

      As a marketing effort, I doubt it paid off. It told the world "Intel can't get 64 bit right".

    8. Re:Itanium was no failure. by rsborg · · Score: 2, Insightful
      It's a failure because Intel shrunk the market,. and doesn't sell any chips. Reducing competition is only half the battle.

      GP poster was trying to say, that for Intel, shrinking the 64 bit market was a strategic goal. Why?

      1. If you as a purchaser of servers really didn't need 64 bit, and could do with many 32 bit machines, guess who you're buying from now
      2. After some time, when noone is around, Intel comes by and re-invents 64 bit (and everyone adores them for it)... this part of the plan was majorly fux0red by AMD64, tho.
      3. Like Microsoft, Intel is big... they can/will kill a market if it kills of competitors. .. and they have been known to use these kind of tactics before. Why do you think every new version of windows has approx. the same functionality but requires double the resources? AMD/VIA own the low-end market, so its best to keep the market moving upscale.

      Sparc, as far as I can see, drastically outsells Itanium.

      Yeah, and what is Sun trading at these days?

      --
      Make sure everyone's vote counts: Verified Voting
    9. Re:Itanium was no failure. by Pandaemonium · · Score: 2, Informative

      You know, I wish people would get this right. The Itanium was not *started* by Intel. HP created and began the work on the ISA as a successor to the PA-RISC line, and when they realized that they didn't have the design resources or manufacturing capacity to build the chip, they partenered with Intel. Since then, HP has been the big partner with Intel- first to get silicon, first to market. HP always intended to go forward with the VLIW setup, and depreciate PA-RISC. The Compaq merger just gave them another architecture, and they decided to kill it- Alpha (RIP).

      So, what's absolutely hilarious is that HP isn't the one getting fucked, or making the wrong decision- they actually pawned the risk onto Intel, and now Intel is the one in trouble if this arch doesn't fly.

      Very strange stuff.

    10. Re:Itanium was no failure. by Anonymous Coward · · Score: 0

      But VLIW did cost a lot of money. One wonders if itanium was created for a special niche role like signal processing in space. No way could this puppy be turned into a mass market GP processor. Now with AMD's and PPC's, buyers are taking the cheaper solution, because they can. Intel's dream of non-comodity priced cpu's is dead, now that GPU's can be co-opted. Maybe Intel should have bought AMD out a long time ago.

  55. Respect comes with fulfilling expectations! by Anonymous Coward · · Score: 0

    And I am NOT talking about performance
    or price/performance.

    I am not even talking about adoption rates.

    Look at what Merced (the real intentionally forgotten name of Itanium) was supposed to be:

    1. A complete replacement for x86 processors

    2. A complete replacement processor for HP, MIPS, Compaq/Digital (even before HP took them over), systems at the high and low end.

    It was to be a FORCED technological direction that rubbed a great number of people, including myself, in many different tech-influential places in the industry to HATE the new architecture.

    So when the prices stayed up, the performance delivered nothing special, and AMD came out with a brilliant alternative...

    No one was there to keep the faith.

    Just when Intel was to make it into the mainstream with it, its remaining leg was cut out from under it (picture the knight thrashing about with his limbs cut off one at a time, still trying to fight in Monty Python and the Holy Grail).

    It was doomed from the beginning.

  56. It's the "Edsel Syndrome" by Anonymous Coward · · Score: 1, Insightful

    Itanium is like the "Edsel" of cpu chips. It's too non-mainstream and while the geeks may ooo and ahh over its esoteric technical details, nobody really cares to actually buy one.

  57. Itanium is great! by DirkWessels · · Score: 1

    I've seen some nice tricks in the architecture of the Itanium. They can really improve performance on most code. One of the tricks is register-rotation, combined with rotation of the computation-flags. But I think the actual chip-level-design they used is a lot slower than the Pentium series. Using these tricks the Itanium should outperform 5x and not just 2x. So probably the cause of slow performance can be found in the design of the chips. I personally think that the designers were hindered by the cooperation with HP (?), because of patent-reasons, bad communication, office-policies etc..

  58. Blame it on premature marketing by Anonymous Coward · · Score: 1, Insightful

    I was associated with porting a Java appserver onto Itanium a while ago (3+ years). Intel invested in this effort (free servers, access to hardware/compiler experts etc).

    The problem was that, the JVM on this was very slow. It lacked JIT support and just crawled. Practically, speaking we would not have sold a single license on this platform. So, we decided to move away from being an early adopter to a market follower.

    If not for Intel's premature marketing effort in engaging partners this early, we would have waited until a more stable environment was available, resulting in successful product shipping.

    I talked to several presenters at an Itanium conference when I went to demo our product, I heard a similar story.

    Well the reasons may not always be technical for such debacles.

  59. Because it still sucks. by ahmetaa · · Score: 1

    First check this graphics: http://blogs.sun.com/roller/resources/JeffV/itaniu m_rev_ext.gif Itanium processor was pushed so badly in the past, there are 9 IDC estimates for the processor reenues. All those 9 estimates were terribly wrong. how come IDC makes 9 consecutive wrong estimates for a product? Itanium deserves al kind of jokes and bad remarks IMHO. - it is still an expensive product. Maybe CPU's are relatively cheap now but systems designed for it are at least double the price of an equally performing Opteron systems. Motherboards, chipsets are expensive. - PErformance numbers you presented from super computers does not reflect realities. For super computers performance metrics are depends on so many parameters (inter connection, application type etc). Nobody can claim itanium is the best bang for buck. - it is a power sucker. - Still no good native software support, no good OS support, people are reluctant to use Virtual machines either (Java etc.)

  60. not as good a design as your claiming by infonography · · Score: 1

    according to geek.com "Itanium 2 processors currently consume 130 watts of power during operation, double that of any existing desktop or server processor made by Intel." beyond that they are up against a already strong market in 64 bit processors. SUN and AMD are kicking their ass in that realm. SGI's recent slippage makes them a do-or-die target for Intel to snap up.

    True, Intel needed to make the change at sometime to 64 bit, their Pentium lines only doing 32bit will eventually be dropped by everybody as 64bit becomes a standard. SUN is eyeing the entry into the larger mid to upper end business market thru Linux on Ultrasparc and AMD Opteron making a nice growth path for businesses into their bigger box server market.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    1. Re:not as good a design as your claiming by cant_get_a_good_nick · · Score: 1

      True, Intel needed to make the change at sometime to 64 bit, their Pentium lines only doing 32bit will eventually be dropped by everybody as 64bit becomes a standard.
      Intel is currently shipping Pentium 4's with AMD64 extensions, renamed EM64T. We have a box or two in house, waiting for someone with time to recompile our base libs in 64 bit.

    2. Re:not as good a design as your claiming by infonography · · Score: 1

      Sound like Intel has admitted defeat.

      --
      Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    3. Re:not as good a design as your claiming by beezly · · Score: 1
      SUN is eyeing the entry into the larger mid to upper end business market thru Linux on Ultrasparc
      From this I can only assume that you don't have a clue what you are talking about. Sun are already a player in the "mid to upper end business market" and have been for the past 20 years. Their current marketing strategy suggests that they aren't particularly interested in Linux either, having recently pushed out OpenSolaris (not that I don't wish they would start pushing Linux in some sort of useful way :( ).
    4. Re:not as good a design as your claiming by petermgreen · · Score: 1

      afaict amd got together with ms and managed to persuade them to go with amd64

      once that was done intel had little choice but to implement amd64

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  61. Intel didn't learn from IBM Micro Channel by bADlOGIN · · Score: 4, Insightful

    Intel figured it was big enough to set the trend by making a radical change. It was wrong and paid the price when the market didn't follow. IBM thought it was big enough to set the trend by making a radical change with Micro Channel Architecture (replacement for the ISA Bus). It went nowhere and helped kill IBM's dominance of the X86 PC world it created. The fact that Intel didn't bet the farm and loose everything is either good planning or dumb luck on thier part.

    --
    *** Sigs are a stupid waste of bandwidth.
    1. Re:Intel didn't learn from IBM Micro Channel by EvilTwinSkippy · · Score: 1
      If you have picked up any trade rags from 8 years ago (damn, have I been out of school that long?) Intel WAS betting the farm on Itanic. Yes, they have been able to stay major in the market by continually warming over old designs, but it really hasn't had a major hit since the Pentium III. (The Pentium M re-uses swaths of the old PIII architecture.)

      What saved them was the fact that there are few, if any, applications for computers that required much computing power beyond 800 Mhz. Even video games generally are a strain on customized components like Graphics cards and DVD drives.

      If you look at applications where performance really matters, i.e. supecomputing clusters, they are running Alphas, Power5s, or Itaniums.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    2. Re:Intel didn't learn from IBM Micro Channel by Glock27 · · Score: 1
      If you look at applications where performance really matters, i.e. supecomputing clusters, they are running Alphas, Power5s, or Itaniums.

      While only one system in the top 10 is x86, if you look at the whole list there are plenty of x86 supercomputers out there. Even Cray is using Opteron in one of its lines.

      --
      Galileo: "The Earth revolves around the Sun!"
      Score: -1 100% Flamebait
    3. Re:Intel didn't learn from IBM Micro Channel by antrik · · Score: 1

      > Intel figured it was big enough to set the trend by making a radical change. It was wrong and paid the price when the market didn't follow. IBM thought it was big enough to set the trend by making a radical change with Micro Channel Architecture (replacement for the ISA Bus). It went nowhere and helped kill IBM's dominance of the X86 PC world it created.

      Such comparisions are silly. When IBM tried with PS/2, there market share on PCs was already down to 15 % or something. Intel is still at 80 % or so. There are many other reasons why the situations are quite different, including the fact Intel never believed or intended IA64 to replace x86 in a short run.

      --
      All my comments get moderated +-0, spotless.
    4. Re:Intel didn't learn from IBM Micro Channel by LarsG · · Score: 1

      IBM thought it was big enough to set the trend by making a radical change with Micro Channel Architecture

      Intel tried to set a new standard but flopped bad on the first iteration of the implementation.

      On the other hand, MCA was excellent tech but was killed by IBM trying to use it as leverage for regaining control of the clone market.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    5. Re:Intel didn't learn from IBM Micro Channel by EvilTwinSkippy · · Score: 1
      While only one system in the top 10 is x86, if you look at the whole list there are plenty of x86 supercomputers out there. Even Cray is using Opteron in one of its line

      Last I checked, the Opteron was an AMD offering.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
  62. Intel a victim of their own Intel Inside marketing by jmorris42 · · Score: 1

    Intel spent over a decade spending billions to convince everyone that it it didn't have "Intel Inside" it was crap. Ok, they won that battle and it is now costing them the war.

    What they didn't consider is just HOW the average person would perceive "Intel Inside", i.e. as an Intel processor running the Intel ISA. So when Intel itself tried to shift gears and say "no, we meant buy anything we throw out the front door" customers balked. The sad fact is that AMD understood the implications of what Intel's marketing dept had done to the marketplace better than Intel, hence AMD64.

    Plus there is the practical problem. Unless you are doing scientific computing you don't see a benefit from Itanic because there are few applications running native and emulated performance sucks. The scientific computing set tends to be writing and compiling their own code so they are in a position to benefit, hence their interest in buying clusters of Itaniums. The DEC Alpha died a similar niche market death and unless Intel manages a major marketing miracle Itanium is fated for the same sad end.

    Or has everyone forgotten Alpha? A totally kick ass CPU design killed by lack of natice apps? When Microsoft tried to push off the ia32 version of Office via emulation that pretty much killed it as everyone else decided emulation was good enough for a market that hadn't proved itself yet. So Alpha died in the mass market from underperformance and languished in large racks doing scientific computing until it could no longer sell enough volume to justify the R&D to continue ramping performance. Also pretty much the same story as Sparc.

    --
    Democrat delenda est
  63. Okay Einstein, answer me this... by Anonymous Coward · · Score: 0

    Why doesn't the Titanic get the respect it deserves? I mean, c'mon it was really really impressive technology for the time.

  64. bad or good, it wasn't handled well by Anonymous Coward · · Score: 0
    Even if it's not a bad product, it's still a botched product.

    And why all the Intel bashing? Well, they seem to screw up a lot these days. First Itanium, then clockspeed over core efficiency (giving us the awful pentium 4), lackluster dual core performance, etc..

  65. Intanium was introduced too late. And too early. by multipart · · Score: 1

    The problem with Itanium is that it was hyped as the greatest thing since sliced bread. But when Merced ("Itanium 1" so to speak) was finally released to the market, two years after its originally planned introduction date, it was already outdated and being outperformed by competing CPUs including x86-based ones. Also, Merced was overpriced, was over-designed, produced more heat than the sum of all its competitors, and the market was still not ready for Itanium because specifications were released so late (even to NDA signers).

    With over-designed, I mean it had way too many features that nobody would have cared about if Itanium would have been a success in its own right. Things like supporting ix86 on the chip; supporting HP-PA; supporting both big endian and little endian; supporting 32 bits pointers and 64 bits pointers (OK, the last one is perhaps useful sometimes, but still...).

    To illustrate how bad the heat was: At the company I work for, in the south-east of Germany, we had an entire floor that didn't need heating in the winters -- each room had an Itanium work station and that was enough. In the summer those machines were turned off whenever possible.

    Anyway, within a year after Merced, McKinley was released, and it was a huge jump forward compared to Merced when comparing heat consumption and performance. It was almost a competitive product, except for the price and the lack of easy hardware support for virtualization. Hell, it is not clear to me to this day what market Intel and HP were trying to attack, but it definitely was already a declining market at the time: Work stations (i.e. that market where Sun and SGI were performing so well in even then) and Big Iron, which is hardly a market large enough to sustain the huge development effort of Itanium.

    By now, AMD64 was coming to the market as well, and it was cheaper, it was 64 bits, it had a great memory controler, and as a bonus it was backward compatible with the mainstream architecture of the day.

    Now you make the business decision: What do you want to sell? Hot, underperforming, expensive Itanium-based machines for which no software exists? Or machines that are cheaper and which can run all the software on the market?

    I know it has been said that Itanium is too difficult to compile for, and that GCC is to blame for the failure of linux-on-ia64. Or that Microsoft pulled the plug on Itanium when they decided to drop Windows-on-ia64. But if you see the market hype of the late 1990s and early 2000, 2001, Itanium was a hot topic and everyone was on that boat. In the end, it was Intel and HP trying too hard to make Itanium compatible with everything (which was never really possible, so what were they thinking?!) and initially not living up to their words about the performance potential of Itanium.

    It is sad, because really if you look at it, there are some pretty good ideas in the Itanium.

  66. things don't add up by u19925 · · Score: 1
    1. the article quoted for $2000 itanium machine is 15 months old. i have not seen one in market.

    2. where is the performance data of $2000 itanium?

    3. quoting speed per mhz is meaningless. absolute speet matters.

    4. all spec, jbb2000, tpc-c, tpc-h etc favor amd for upto 8 processors. above 8 proc, itanium just competes sometimes up and sometimes down with sparc, power processors.

    5. with binary compatibility with windows not there and commonly available linux distros and apps not there, what is the appeal for itanium (other than forced migration of hp-ux)?

    yes, itanium has lots of potential, perhaps same as ia432 had in 1980s, but right now, nothing to be excited about.

  67. Infanticide by william_w_bush · · Score: 2, Interesting

    Itanium was killed by intel's megahertz marketing. Why get an expensive 1.4Ghz itanium when you can get 2 3.0ghz xeons for less? The amd-intel 1Ghz race hit it even harder, since intel had to totally sell out itanium's higher ipc for the p3's higher frequency, and meant the p3 could be brute-forced to equal or greater performance as the new, non-mainstream itanium architecture.

    In my opinion the p4 was the worst thing ever to come out of any microprocessor house in the last 20 years, as it not only comprimised microprocessor design for the horrible and blind-sighted goal of mainstream marketing, but essentially caused a large part of the current TDP crises the industry is in now, and reinforced our mentally handicapped reliance on single-threaded programming.

    The humor in the itanic label has nothing to do with the chips, it has to do with intel trying to have it both ways: intel chips are the most powerful, with the only metric that matters, frequency, and ipc and design efficiency matter little, but also that "oh yeah and we have this amazing chip that is so powerful but runs at half the clock speed." It was a blatent contradiction in marketing messages.

    For f*cks sake, they called their double-clocked alu "NetBurst"... seriously, why not add an onboard memory controller and claim it's "SuperBandwithMaker", which uses it's amazing technology to increase the speed of your dial-up connection...

    Yes, if you market to customers by treating them as idiots, expect them to choose the stupid product, and ignore you when you claim to offer another product that "no really this is a good chip, not like that other one which we said was the fastest", which is actually better for you in the long run, because you can set a new foundation for improvement.

    When amd came out with the opteron at 64-bit, and with surprisingly competitive performance while still running legacy apps at faster speeds, how do you compete with that?

    Here's hoping they do manage to resurrect the alpha lines, Ibm even went a little over to the marketing darkside with the g5, trading frequency scaling for TDP, but they usually manage to rebalance the two after a few years of revisions.

    --
    The first rule of USENET is you do not talk about USENET.
  68. Re:because it's a failure by danheskett · · Score: 2, Interesting

    Java. Mainly.

    Java is handy for many, many things. One thing it's not going to help is a large scale migration from one platform to the next. Years ago I am sure Intel thought it was going to be bigger, but it's not. Meaning more trouble migrating to new hardware platforms!

  69. You should also compare prices... by alewar · · Score: 1

    You are comparing a $2000 Itanium processor with a $500 Opteron. Now if you multiply the benchmark result of the opteron times 4, you will have the Itanium easily displaced for an Opteron solution of the same price.

  70. Fallacies in the article by vlad_petric · · Score: 4, Insightful
    1. transistor count. You do need more transistors for decoding x86 into micro(mu)-ops, but in the end your L2(3) cache is gonna be >50% of your chip area. Interestingly enough, Itanium chips are overloaded with L3, and in fact, the first chip to break the 1billion transistors is an Itanium II chip. The good performance of Itanium comes a lot from its shitload of caches; nothing's preventing Intel from loading the P4 with caches though.

    2. x86 is bad/ugly/dirty/whatever, however Itanium is not exactly clean either. The stacked register file is a good example of that. I personally prefer x86-64, which takes the evolutionary approach: fixes quite a few of the problems of x86, while still retaining the core features.

    3. x86 chips do out-of-order execution; Itanium, OTOH relies on the compiler to schedule instructions and bundle them together. The main problem here is that doing instruction scheduling statically is much, much harder than doing it dynamically. An average program has a basic block size that is less than 10 instructions. It's very hard to find parallelism within such small basic blocks, so to be efficient at all, you need to do profiling to build traces/hyperblocks. In fact, profiling on the Itanium can give you a performance boost of 30%. However, profiling is hardly desirable from a software developer's perspective

    --

    The Raven

    1. Re:Fallacies in the article by antrik · · Score: 1

      > The good performance of Itanium comes a lot from its shitload of caches; nothing's preventing Intel from loading the P4 with caches though.

      Actually, it's the other way round: Itanium needs larger caches to achieve good performance, because of the sparse machine code, and the fairly slow (compared to current x86 CPUs) FSB. P4 wouldn't profit nearly as much from larger caches.

      With multicore chips, the Itanium will probably get a considerable boost on this front, as the instruction cache doesn't need to be scaled to the number of cores. OTOH, the cores themselfs are quite simple, so it's possible to integrate a large number of cores without considerably increasing the transistor count and power consumption.

      --
      All my comments get moderated +-0, spotless.
    2. Re:Fallacies in the article by antrik · · Score: 1

      Oh, another thing:

      > x86 is bad/ugly/dirty/whatever, however Itanium is not exactly clean either. The stacked register file is a good example of that.

      What's wrong with the register file? It's actually a very smart (and clean) solution to the problem of explicitely parallelizing register usage.

      --
      All my comments get moderated +-0, spotless.
    3. Re:Fallacies in the article by vlad_petric · · Score: 1
      I'm a little bit confused. The problem is how to extract instruction level parallelism (ILP). The stacked register file doesn't really address this. The purpose of a stacked register file is to reduce the number of load/stores to the actual stack.

      The main problem with it, however, is that it makes register renaming very difficult to implement. Register renaming is quintesential for out-of-order execution. BTW, the other big player that has an ISA with stacked register file - Sun - still does in-order processing, and this is actually one of the reasons their processors were dubbed "UltraSlows".

      --

      The Raven

    4. Re:Fallacies in the article by vlad_petric · · Score: 1
      Actually, it depends heavily on the type of workload. For media/scientific stuff, a large cache can be detrimental, as larger means slower and in this case under-utilized. Itanium actually does well on these because it's easy for the compiler to VLIW-ize the very regular code.

      For OLTP-like server workloads, large caches are, however, crucial. Because they almost always wait for cache misses to resolve, these things barely manage to execute an instruction every couple of cycles, so actually having VLIW doesn't really mean much.

      This doesn't mean that a P4 won't benefit from larger caches in a server configuration. There have been research papers looking at these workloads, and in general larger caches always help in such a configuration.

      --

      The Raven

    5. Re:Fallacies in the article by Anonymous Coward · · Score: 0

      you're fucked in the head on two counts:

      the Itanium 2 doesn't have one billion transistors
      transistors are free, it's switching them that costs (in terms of power consumption, clock headroom etc) - cache transistors are nowhere near the problem random logic is (OoO etc) in terms of die area (you can pack cache transistors MUCH more tightly than random logic, we're talking a factor of >10x here), power consumption (>10x, again) etc.

    6. Re:Fallacies in the article by antrik · · Score: 1

      Obviously, larger caches will always increase performance more or less, under otherwise unchanged conditions. My point is that due to various reasons, you can't just expect the same performance gain when boosting a P4 from 1 MiB cache to 9 as you get with Itanium. Actually, there is even prove for that: The MP Xeons with lots of cache offer quite medicore performance in single CPU setups compared to P4, and only the higher cache demand in a UMA SMP system justify them at all.

      Nothing like an Itanium killer from a P4 with boosted caches, unlike the post I was replying to suggested...

      --
      All my comments get moderated +-0, spotless.
    7. Re:Fallacies in the article by antrik · · Score: 1

      The whole point of the EPIC approach is to avoid dynamic optimizations like out-of-order processing... And actually avoid the need for it as far as possible, using some tricks.

      The register set has some features (I agree that I am confusing them somewhat, as I don't remember the details), which actually help avoiding the need for register renaming in an EPIC environment.

      BTW, there was some important difference between the SPARC and the Itanium stacked register file IIRC; so I don't think the comparison is valid.

      --
      All my comments get moderated +-0, spotless.
  71. Re:Easy Answer: It started as a flop by dknj · · Score: 1

    Didn't the same thing happen with the Pentium Pro and it eventually became the P2 and P3. I wouldn't be surprised if Intel is becoming quiet about the Itanium to weasel it into the mainstream.

  72. Re:Easy Answer: It started as a flop by Usagi_yo · · Score: 2, Interesting
    It was worse then just a flop, it sank alot of companies bankrolls waiting for this technology -- meanwhile AMD delivered a fine performing chip for way way less, and lets face it, the big market in Desktop PC's is consumer electronics.


    Intel was so late in delivery that all the high performance workstation people abandoned the Itanic.

  73. Because it's low ROI by WillAffleckUW · · Score: 1

    I can get a TigerDirect reconditioned AMD 3.0 GHz laptop with 2 Firewire ports, USB, and top of the line wireless with 512MB RAM for about 25 percent less than the Intel version that runs apps at about the same speed (accounting for differences).

    So the reason noone respects the Intel chip you mentioned is it's still too expensive.

    --
    -- Tigger warning: This post may contain tiggers! --
  74. Not respected where? by Anonymous Coward · · Score: 0

    Certainly it has not been a do-all chip like it was originally said to be, but for the people who need performace, the chip is respected. Everyone who sells 16x and bigger boxes understand what the chip can do, and there is no shortage of buyers for 16x and up Itanium machines.

  75. No dynamic optimization. by canadiangoose · · Score: 1
    I hear a bunch of people talking about Itanium being hard to code for. What makes this problem even more difficult to deal with is that without dynamic execution hardware, any code that was optimized for Itanium 1 runs piss-poorly on Itanium 2. Likewise for code written and optimized for Itanium 2, it will run terrible on the Itanium 3.

    I'm sure that neither the server admin nor the software vendor wants to deal with the headache of finding the right versions of ever piece of software. Does Windows come with Itanium 1 optimizations, or Itanium 2 optimizations? How about HP-UX?

    I realize that all procrssors suffer the same optimization problems across generations, but the dynamic execution capabilities of most chips go a long way towards minimizing this effect.

    --
    Never eat more than you can lift -- Miss Piggy
  76. Apple/Intel....OS X/Itanium by Zemplar · · Score: 1

    Could Apple be planning on utilizing the Itanium and become the saving grace for this processor from Intel?

    Hrmmm....

  77. some reasons by ashpool7 · · Score: 1

    * Increasing pipeline stages to boost clockspeed. Doing this confused customers into thinking P4s were that much faster than AMD's offerings. AMD had to come up with the PR ratings to keep mindshare.

    * Killing Alpha in favor of Itanium. I like how the story poster didn't bother to factor in the Earth Simulator...

    * Processor ID. Consumer-hostile.

    * RAMBUS. Worse than DDR and was only because Intel had an invested stake in the company.

    * Thinking USB2 is better than FireWire and pushing it to sell more CPUs when FireWire would be better for just about all of the applications that require the high speed interface. USB2 requires a "master" (aka intel CPU) and FireWire doesn't.

    I'm sure I could come up with some more....

    1. Re:some reasons by Anonymous Coward · · Score: 0

      I think you have the Rambus thing backwards IIRC Intel took equity in Rambus when they chose them as a memory technology, not the other way around

    2. Re:some reasons by saider · · Score: 1

      USB is a _bus_. Firewire is a point to point connection. USB is designed to allow multiple items to share the bus in a variety of configurations. And it is designed to be inexpensive - materials wise. If you are going to make hundreds of millions of them, they had better be cheap. Intel knows how to sell things in huge quantities and knows how to make something "good enough". Firewire is technically better, but the costs associated with building it kept it out of most devices (excluding camcorders) until about 2 years ago.

      --


      Remember, You are unique...just like everyone else.
    3. Re:some reasons by ashpool7 · · Score: 1

      I don't think bus vs p2p really matters, but ok.

      My point was that while USB is fantastic for things like mice, keyboards, and other dumb stuff that used to have their own proprietary low-speed connection (scanners, tablets), marketing USB2 as great for things like hard drives, video transfer, and other demanding applications is a stretch. FireWire was designed for those applications *and more* while USB was designed to replace the PS/2 connector.

      As for costs associated with building it, that's a pretty ridiculous argument. The extra silicon needed per chip is miniscule in the grand scheme of things. The real reason it is expensive is because Intel didn't want to back it because FireWire devices didn't have to have a hugely profitable Intel CPUs to transfer data. USB is designed to be too stupid to be able to do that. If Intel joined the 1394 TA and shipped FireWire, there never would have been such a long "expensive period" that FireWire had to edure.

      Camcorders had FireWire and DV because USB wouldn't cut it, not because it was exotic and expensive. Who wants to haul around a computer on your belt in addition to your hard drive to store your live DV feed.

  78. Re:the problem is those are well optimized benchma by Donny+Smith · · Score: 1



    >1) Compare the performance of itanium with xeon/opteron in running native x86 code.

    Well for some apps Itanium is a faster solution.

    >2) Compare the costs of building real end user systems.

    Correct.
    If I'm not mistaken, next year we should see motherboards and systems that will work with either Xeon or Itanium CPUs. Then the processor cost will be the differntiating factor (and single CPU Itanium systems could cost about the same as dual CPU Xeon systems).

    > 3) Compare the availability of windows xp drivers.

    Yes. And the same goes for AMD64, tough to a much lesser extent. I think the answer to this lies in my comments on your second comment - once the chipsets and other infrastructure is unified, the Itanium drivers will become commonly available.

  79. GCC support? by spectrokid · · Score: 1

    How is GCC support for Itanium? If the chip leaves so much up to the compiler, then the easiest road to success would be for Intel to build support in GCC. Recompile your Gentoo, and you have a fully optimised OS to show off. Does anybody know how good Itanium does on GCC?

    --

    10 ?"Hello World" life was simple then

    1. Re:GCC support? by zoo · · Score: 1

      GCC's IA64 support is functional, but you can't call it much better than that. Intel's answer was their own compiler suite, which did much better than GCC.

      Note that on basic OS stuff, neither compiler was dramatically different in performance (so don't bother to recompile your whole system). But for application code, which is what all of the customers bought the system for, the Intel compiler was notably better.

      If I remember correctly, GCC breaks things down to the lower level RTL too early to allow the sort of optimizations that EPIC requires. I think the new internals format used in GCC 4 is supposed to make the sort of work that IA64 requires possible.

      Take the entire previous paragraph with a grain of salt.

  80. How about apple-to-apple comparisons by Waffle+Iron · · Score: 2, Interesting
    As in recent years the Itanium does well, easily beating x86 processors even at its low clockspeed (1.4Ghz)

    Itaniums also have up to 9 Megabytes of cache. And they come with super heavy-duty FPU units. It's unfortunate that we can't directly compare the core architecture of the Itanium vs. the core architecure of the x86 without influence of the extra cache and FPU resources that the Itanium target market supports.

    If somebody would build an x86 with that much cache, and increase the proportion of transistors in the x86 FPUs to match the Itanium's target market, then we could compare the relative benefits of x86 core vs. EPIC core. Until then, when you compare the two processors, you're most likely looking at differences in the logic units outside the core, which are determined by target market price/performance tradeoffs and which are largely independent of the core architecture.

  81. Re:Easy Answer: It started as a flop by Lostie · · Score: 1

    Not necessarily true. What about the Pentium 4 (willamette)?
    When it was first introduced, not only did it get badly beaten by the Athlon in the performance stakes, the 1.4 - 1.6Ghz versions were even slower than the previous generation Pentium 3 coppermine! Plus you had no choice but to purchase extremely expensive and high-latency RAMBUS memory (in pairs).

    Was the Pentium4 a failure? No. Because Intel really went to town on it turning up the Ghz and adding loads of cache to make up for a rather slow chip design. And being a monopoly over AMD sure helped, although the Athlon definitely hurt them badly...

    There is of course the Pentium PRO, but that does kinda fit in with what you said though ;)

  82. After having worked on them.... by zoo · · Score: 2, Interesting

    I spent a while working on building cluster of IA64 machines in the HPC space. I don't anymore, and I can't say as I miss them.

    First, as noted elsewhere, at the time when opinions were being formed, the cost of a decent dual processor machine with a useful amount of memory was about $30K (a typical HP cluster machine) while the comparable x86 box was about $3000. Today those prices are lower, but the x86 is still cheaper by several times.

    Second, the HPC folks were perfectly happy running Linux, while no one else seemed to be. And Linux works on the machines. But in general purpose computing the advantages of the IA64 aren't seen.
    Especially now when we have x86 with 64 bit memory addressing.

    Next, the hardware (when you're willing to pay for it) was lousy. One box from HP had 15 fans for the 2 processors, in a 6 or 7U box. I think it would take off if you aligned it properly before turning it on. I can't imagine a rack full of these, much less a whole machine room (we had 2, and wouldn't allow them both on at the same time, but we had these in office space).

    The EFI BIOS is truly an amazing piece of work. It's hard to work with on the console if you're a PC user expecting normal menu traversal with arrow keys (left and right arrow keys worked, but to move up or down you needed to use 'u' or 'd'). But we were building clusters, and expected to do things with the machine via serial interfaces. But the UI was even worse over a serial line. What happened to nice, easy to program command line firmware? (Note to HP Fort Collins: you're supposed to take the BEST of both worlds when you try to merge paradigms).

    Yes, there was also a network interface which would take the place of the serial connection. But this wouldn't use DHCP, but rather manual network configuration, which required this funky hydra cable to connect to some other machine in order to set up properly. And each person connecting to this system would get write access to the console. There are decent ways to share a console across multiple logged in users (c.f. http://conserver.com/ for one example).

    For a set of machines designed for cluster computing, they were about as unfriendly as you can get for us infrastructure people.

    (Note, these hardware obvservations are only based on about 6 classes of HP machines that I've put my fingers onto; I have no knowledge of any non-HP IA64 machines).

    Once up and running, they're not bad systems. But they're not so much better than x86 systems to win over most people. There's always a class of user who is willing to pay for the highest performance. But the larger part of the market pays attention to flops/dollar, and building a thousand node x86 system is still cheaper than 500 nodes of IA64.

    (Disclaimer: I haven't had to price out IA64 systems for a year and change now; I don't believe my claims are invalid, but if someone can show me I'm wrong, I'd love to know it).

    I have no interest in working on IA64 systems anymore, unless you're paying me to do it.

  83. The only good thing from Intel. by Tilmitt · · Score: 1

    The Itanium is one of the few good things to come out of Intel. x86 is inelegant and Intel knows it. Massive amounts of engineering effort goes into keeping x86 performing the best, and a more elegant RISCish CPU architecture such as the Itanium would require alot less to go alot further. Personally i hate AMD for extending x86 with AMD64, now the bilnd masses will be clinging onto x86 for many more years. Shame on AMD for their inelegant choice. Yeah yeah i know they're a company so it's socially acceptable for them to be brutally pratical to make money and not do nice things but it is unfair to reap the benefits of their raw praticality (teh monies!) and still be "allowed" to be immune to criticism of their lack of elegance. Intels marketing revolts me but i despise x86 and I'd like to have an Itanium but definately not an Athlon 64. And i wouldn't be seen dead with a Pentium 4. I won't get started on Netburst, suffice to say that even x86 looks elegant compared to it.

    --
    This guy are sick.
    1. Re:The only good thing from Intel. by tomstdenis · · Score: 1

      Yeah the ISA is a bit of a pain but compared to 4 to 8 byte opcodes of the typical risc the x86 isn't that far off...

      add rax,rbx --- 3 bytes [x86_64]
      lea rax,[rbx+rcx] --- ~4 bytes [x86_64]

      add r0,r1,r1 --- 4 bytes [ARM, MIPS, PPC]

      Sure some RISC ISAs are a bit nicer but they're not that much better.

      Than you look at the fact that the IPC of the AMD64 is "a shit load higher" than that of the MIPS or ARM...

      Then you look into the fact that the AMD64 takes less power than a P4/Xeon...

      The AMD64 is well placed in desktop computers. It's not the lowest power consumption core but it's at least the fastest as far as IPC is concerned.

      It's MIPS/watts ratio beats Intel designs and it's simple MIPS rating is higher than anything MIPS/ARM offer.

      So if you need a lot of MIPS in a desktop, it doesn't make sense to use anything but an AMD64...

      If you need elegance, small and lower MIPS/power then use an ARM.

      If you want to create a second sun use an Intel.

      Tom

      --
      Someday, I'll have a real sig.
  84. Anticipation by Britz · · Score: 1

    The whole industry was preparing for the arrival of Intel on the 64 bit server processor market. Intel was so huge in the 90's (and if even bigger now) that everyone thought: "This is it!" HP, Compaq, Novell, ... everyone. They thought it would have such a good price perfomance issue that they threw out all their own stuff and only sell Itaniums a couple years later.

    Wasn't that part of the reason why they stopped developement on the Alpha? Could someone please comment?

    Also Tru64, Unix for 64bit by a consortium of industry giants was to be developed only for the Itanium.

    So the anticipation was huge. And compared to the anticipation it was such a huge failure. And it still is on many applications, because nothing got ported when it came out because of the failure to meet anticipation.

    The Itanium now rocks on some supercomputing tasks, but everyone and their dog is currently switching to the x86 Unix called Linux, not because it is free (they tend to buy expensive service contracts) but because the cost/performance ratio is so good mainly because of competition. If there would be a really good, stable and fast port of some Unix variant to the Itanium and some big company would support it the Itanium could still come around.

    But at the moment it is chicken and egg. No cheap Itanium means no port and no port means no mass sale that leads to expensive Itaniums.

  85. No one buys any! by Anonymous Coward · · Score: 0

    Why do we see so many disparaging opinions of the Itanium processor (all those 'Itanic' jokes, etc.)?"

    Because there are about 1,000 Itanium servers that have been sold in total. I remember reading one HP quarterly report that said they sold less than a dozen in that quarter.

    Even if Itanic was the best thing since sliced bread, it has no market share (probably because it's so expensive and so incompatible with x86), therefore almost nobody will waste their time developing for that platform.

    It isn't just performance that matters, it's performance per dollar.

  86. Intel bashing by edxwelch · · Score: 1

    No, Intel bashing is perfectly justified. Here is a comprehensive list of reasons why you should hate Intel:
    http://www.amd.com/us-en/assets/content_type/Downl oadableAssets/AMD-Intel_Full_Complaint.pdf

    contains some amazing revelations

  87. The simplest answer by Anonymous Coward · · Score: 0

    People don't buy Itanium's powered computers just because they don't need it.

    You know, a computer is made out of hardware AND software.
    Ok, you provide me a faster hardware, but put me in the need to find/try/buy/learn new software or, even worse, wait for the monopolist in charge to recompile and distribuite his.
    Who needs so?

  88. Top500 measures LINPACK performance only by poszi · · Score: 1
    I tested an Itanium2 machine against an Opteron box for scientific applications and the LINPACK score ratio (which is measured for the top500) was the absolute limit of what you could get from Itanium. Only for highly optimized code with simple repeated floating point calculations (like matrix multiplications which are the main task in LINPACK) 1.5GHz Itanium was much better (more than 70%) than Opteron 2.2GHz. Any branches in the code or integer calculations resulted in a relative slowdown of Itanium and for some of the codes it was slower than the Opteron.

    For LINPACK type calculations Itanium2 is probably the best what you can get and is price competitive. For a lot of other tasks it is not.

    --

    Save the bandwidth. Don't use sigs!

  89. Give me a couple of them. by elgee · · Score: 1

    I will give it rave reviews.

  90. A perhaps useful analogy by Anonymous Coward · · Score: 0

    When I first moved to the SF Peninsula in the early '90s, a friend of mine took me by a shopping center called Fashion Island. This was a classic enclosed megamall, built maybe a decade before and located at the junction of two major freeways; what made it noteworthy was that it was almost completely empty. At that point there was an operating movie theater and an ice rink; the rest was an enormous dark, abandoned hulk. Practically new shopping center, decent location in a densely populated, well-heeled area -- no tenants, and thus no customers.

    What had happened to cause this? A few years into the life of the mall, in a stroke of unfortunate timing a couple of the anchor department stores simultaneously merged or went out of business. Without those stores in place, the smaller stores in the mall saw reduced traffic, and many left. This in turn made it hard to attract replacement anchor stores, and inevitably more and more of the small shops faded away. This continued until there was no way to pull out of the death spiral. The ultimate solution? They bulldozed the entire thing and replaced it with a new mall with a new name, "Bridgepointe," which appears to be doing just fine.

    Maybe it's not a perfect analogy, but the point here is you had a perfectly fine mall, with maybe one or two minor problems -- and the stench of failure all over it. Once that stench settles in to stay, you often have no choice but to call in the bulldozers, or finally add 64-bit extensions to your existing processor line as the case may be.

  91. Motherboard sources by SeanDuggan · · Score: 2, Interesting

    Oh, and it would help if Intel could make decent motherboards for its own chip.
    It could be my information is out of date, but I don't believe Intel has made their own motherboards for years. It's just not cost-effective. Rather, they give specifications for boards and 3rd-party manufaturers then fabtricate their own varieties. Or at least that was the way it was when I co-oped with them. *wry grin* I always wondered how much they saved after the costs of bad publicity due to bad implementations. Amazingly often, a company would ignore corrections to their motherboard diagrams and of course Intel would get blamed when the motherboards would malfunction...

    --
    This sig has absolutely no significance and serves only to take up screen space and waste the time of the reader.
    1. Re:Motherboard sources by sflory · · Score: 2, Insightful

      Intel's still making mother boards. Their EPSD division is still a big player in the x86 server market.

      http://intel.com/support/motherboards/server/

      --
      IANALBIPOOGL (I am not a Lawyer, but I play one on GrokLaw.)
    2. Re:Motherboard sources by antirename · · Score: 1

      No, they still make them. And they still suck. I bought one for cheap Windows box because it was, well, cheap and I still regret it. No way to tweak anything, and six months after I got it it wouldn't boot off a CD or let me into the BIOS. POS.

    3. Re:Motherboard sources by irf · · Score: 1

      Intel still make motherboards, they are the most reliable, and these days, I must say reasonably priced, considering that ASUS & CO, do charge an arm and a leg for their MB's, just for the "added value??" of overclocking.
      If one has to take care of a lot of boxes, then one should stear away from any third party MB's and stick with the intel ones. Let me add that they are lot cheaper too.
      HTH

  92. A little History ... by Herschel+Cohen · · Score: 1

    Forgive me if this has been commented previously.

    Intel's problems with the Itanium began with its first iteration: they expected Google to be a prime customer. However, the latter was unimpressed with the excessive power consumption. That is, compared to simpler chips and custom mother board boxes they already had the Itanium was much more costly. There are two costs: purchase and maintenance; the Itanium was more expense in each.

  93. crappy apps, crappy performance, just plain crappy by mwhahaha · · Score: 1

    We've got 6 of them at work. And I've had many a sleepless night trying to get them up to par. We're running oracle and bea weblogic on them and it's been a nightmare. Coupled with the poor EMC support for them and the random init_tty lockups, I rue the day some idiot up high said go with the itaniums. We don't get the performace we see on the regular old xeons and now with the new x86_64 xeons, there's no need for them. The only reason we even have these is because of the high ram capibilities. Each machine has 16 gigs of ram, but since you can do that with xeons now, I'd love to replace them with more reliable machines. I call our itaniums our little space heaters...$30000 space heaters. *sigh*

  94. $2000 - maybe for just the CPU by awkScooby · · Score: 1
    I took a look on Dell's website, at the PowerEdge servers (at the Higher Education institutions site, since I work at an .edu). A single CPU Itanium2 (1.5 GHz) without an OS costs $15,789.00. A comparable PowerEdge 2850 costs $4,855.90. Or, if I take advantage of a special they are having right now, I can get up to 5 2850's for $2,425.50 each.

    Is the Itanium2 system over 3 times faster than the 2850? The servers my group runs are web servers, file servers, print servers, database servers, etc. I would have to be smoking crack to decide to move from Xeons to the Itanium2.

    Now, having said that, our Computer Science department just recently purchased some Itaniums for a small cluster (I think about 30 nodes). They chose the Itanium because of its floating point performance.

    Itanium has its place, but that place isn't in my server room...

  95. Itanium problems. by stnuke · · Score: 3, Interesting

    Well, there are many reasons the Itanic failed. It was a great architecture, a neat idea. Shift all of the intelligence in the chip up to the compiler, execute in-order, optimised code, get rid of deep bypassing, etc. Generally, get rid of the extra 50% of the chip that's dedicated to turning an instruction stream into a series of vectors.

    Note, it *was* a neat architecture.

    Then, everybody got involved. Imagine a roomfull of architecture, compiler, and systems PhD's, each with their own pet idea. And this chip had them ALL in it. Anybody remember the i432? In a way, this was the i433.

    BUT. This meant a complete break with the current codebase, and in the final analysis intel didn't have the guts for it. Especially once their hopes for compilers weren't being borne out (once, Intel was a HUGE player in the market for compilers PhD's). So the guys at Intel decided to add x86 hardware compatilbility to this. Then, since their compiler plans weren't working out, they added out-of-order execution.

    Now, all of these things had crazy interactions. Suddenly, who knew what it was doing? Then the power... all those units, executing all those dead instructions - it ran HOT. Then the fact that x86 compat and o-o-o were a gigantic boat anchor in terms of chip real estate, driving the cost through the roof pretty much sealed its fate. It became a "server processor". And if you get 7 or 8 P4's for the price of one Itanium... well, your cluster is better served with those 7 or 8 P4's.

    Pride goeth.

  96. Itanium is far more expensive than x86 by Anonymous Coward · · Score: 0

    Just about the very very cheapest Itanium system you can get is $2K before you add processors or RAM.
    http://froogle.google.com/froogle?q=SuperServer%20 6123L-iR&hl=en&lr=&safe=off&sa=N&tab=wf

    Come July 13th when Intel ships its x86 dual-core server support, a dual core x86 machine will be less than $1000, including CPU and base RAM.

    There are few tasks where 1 Itanium system > 3+ x86 systems.

    And thus Itanium has no real market other than very specialized tasks where cost is no object. For beyond the basic system cost, you need training in VLIW, special compilers, and highly specialized performance optimization technology to get any real performance from Itanium.

    All in all, there are many good reasons why Itanium = Itanic. The cost/benefit scenarios are dismal at best. I would not expect Itanium to ever be successful in the mainstream.

  97. Poor performance for general-purpose computing by RobKow · · Score: 2, Insightful

    The decision to move instruction-level parallelization from runtime (in the CPU, hardware, expensive) to compile-time (software, cheap on a marginal cost basis) ended up being a poor one for general-purpose computing. You save silicon not having all the fancy instruction scheduling, reordering, etc., but you lose the knowledge of the runtime environment the hardware has when you move it into the compiler.

    Sure, there's a lot more processing you can do off-line in the compiler, but you also have a lot less information about how the code is actually going to be executed at compile time.

    Theoretically, JIT compilers (Java and .NET bytecode to native code and Transmeta x86 to native VLIW) can do a better job because they can profile the running code and get a better handle on likely execution paths. These would be a good match to the VLIW Itaniums to compensate for them lacking that "complex" hardware to keep the execution units supplied.

    The Itanium2 makes a good supercomputer chip because you can optimize your code very carefully and you've got a good idea what the data looks like and what branches will be taken, etc. at compile time.

  98. Removal of heatsinks and serial numbers by SeanDuggan · · Score: 3, Interesting

    Most amusing to me was that the early versions had the chip serial numbers on the area covered with the heatsink. Removing the heatsink voided your warranty. You needed that serial number to get warranty work done on the processor.

    --
    This sig has absolutely no significance and serves only to take up screen space and waste the time of the reader.
    1. Re:Removal of heatsinks and serial numbers by Dun+Malg · · Score: 1
      Most amusing to me was that the early versions had the chip serial numbers on the area covered with the heatsink. Removing the heatsink voided your warranty. You needed that serial number to get warranty work done on the processor.

      Sheesh, all that's missing a sticker saying "Beware of the Leopard"

      --
      If a job's not worth doing, it's not worth doing right.
  99. That's funny by Junior+J.+Junior+III · · Score: 1

    I thought the official name WAS Itanic. I figured they just liked the movie, but were missing the obvious bad omen. Oh well.

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
  100. Detailed commentary on realworldtech by coats · · Score: 1

    The computer-architecture blog "realworldtech" has been slogging this one out in extreme detail (particularly as regards integer performance, where the Itanium has seemed to lag); see http://www.realworldtech.com/forums/index.cfm?acti on=detail&PostNum=3510&Thread=1&entryID=52549&room ID=11

    --
    "My opinions are my own, and I've got *lots* of them!"
  101. Re:Interoperability by sillybilly · · Score: 1

    Maybe this is a topic where the pathetic dotnet would make sense - as a transition platform from the dinosaur x86 architecture to something new, better, where you only have to execute fast the IL language code, and not the native x86 instructions. Then PPC and x86 and ia64 could all really go at it. Unfortunately, while everything is x86, dotnet sucks because it's slow, bloated, and adds yet another layer or black magic between you and your hard earned cpu cycles. In any case, more power is not what we need anymore, but less power - I'm glad to see the other news about Transmeta. I'd love to see a chip that uses 5Watts and gives me 1.5 GHz P4/Athlon performance. I'd be content.

  102. History Provides the Answer by Zobeid · · Score: 1

    The Itanium isn't making any headway in the marketplace for the same reason the PowerPC didn't. It doesn't run X86 code, not natively at full speed.

    In the early years of PowerPC, the plan was for it to replace both the 680x0 (in Macs) and the 80x86 (in PC), thus bringing the platforms together on common hardware. The lure was better performance.

    The PowerPC processors in that era cranked out roughly 80% better performance than X86. Apple went for it, but PC makers weren't interested. "What, you expect us to break compatibility for a measly 80% increase in performance? It is to laugh! HAHAHA!!"

    Now they are laughing at Itanium for the same reason. I suspect if you could get Itanium to run 300% faster than X86 at the same price, then the PC makers would sit up and take notice. But they simply aren't going to be bothered with it unless the gain is really huge and dramatic.

  103. Itanium is an astounding success by Jhan · · Score: 5, Insightful

    Let me tell y'all a little story.

    Back in '94-'95 i was doing the third grade of the Computer Science course at the Royal Institute of Technology, which meant I had to choose a specialization. I chose "Computer Systems", ie. processors, busses, caches and what-not.

    This was a very exiting time to be studying processors since (for a fleeting moment) Intel processors where the absolutely worst processors among the serious combatants.

    Yes, you read that right. The Alpha was (of course) and unstoppable juggernaut, but through a freak act of development schedules the new MIPS had managed to outstrip the latest Alpha.

    After MIPS and Alpha we had PA-RISC, SPARC, PPC and then finally the pathetic, lowly Intel x86.

    Alpha had strong plans of totatlly replacing the x86 by offering Alpha based x86 emulations that were faster than the fastest x86 in running x86 code.

    But now, Intel announced the Itanium.

    • It will be 64 bit (all the above architectures were, of course already 64 bit).
    • It will be multi-processor (all the above architectures had cache coherency logic to allow 8+ processors).
    • But, most of all, it will have THIS!, and I mean <blink>THIS!!!!</blink> much preformance! (Intel pulls wildly insane numbers out of an orifice of your choice).
    ...and the monster thing will ship in 1998.

    Apparently, all the CPU makers sat down and discussed this, and agreed that "They may be last right now, but they have piles of cash. They could do this. They really could."

    So, what did the competiton do?

    • Alpha tried to stay agressive, but didn't sell enough, so they tanked. Bought by Compaq, then HP then sweet nothingness (see HP).
    • SGI and MIPS didn't know what to do. They made some noises about shifting to the Itanium... Maybe. While still developing the MIPS... Just a little. A very little. Now, as Netcraft confirms, SGI is dying. :-)
    • HP promptly shat their pants, threw their PA-RISC processor platform (which was third fastest in the world at the time) out the window and partnered with Intel, making plans to replace all HP/UX PA-RISC machines with Itaniums. ...which is what they have been doing for some time now, and loosing customers by the droves for it.
      Because of aquisitions, they also happened to be saddled with the best processor ever made, the Alpha.
      Stick with dying Intel... Develop best processor. Hmm...
      Well, you all know where HP is going.
    • Sun, I'm sad to say, didn't ruin the Sparc platform because of Itanium, but just by being their usual ineffectual self.
    • The PPC concertium tried to press on, and did quite good. Motorola was to obsessed with embedded chips, but even now, I personally think IBM's "G5"s are very good, and believe they have it in them to produce several new generations of kick-ass chips.

    And then what happend?

    Intel didn't deliver... and didn't deliver... and didn't deliver some more.

    Year after year passes...

    When the Itanium was finally delivered, it was obvious that every other platform could have kept up, if they would just have kept developing their processors!

    But they didn't and now they sleep with the fishes.

    Conclusion: By making their Itanium announcement, Intel slew four out five serious competitor. It doesn't relly matter if the Itanium sucks. In fact, the Itanium would be Intels greatest success even if they had never delivered it.

    --

    I choose to remain celibate, like my father and his father before him.

    1. Re:Itanium is an astounding success by jafac · · Score: 1

      Conclusion: By making their Itanium announcement, Intel slew four out five serious competitor. It doesn't relly matter if the Itanium sucks. In fact, the Itanium would be Intels greatest success even if they had never delivered it.

      The ironic bit is, back when the Itanium was announced, even a retarded 5 year old was smart enough to know Intel's posturing was 100% BS. Yet everyone fell for it. TO this day, I still can't figure out what the hell happened to HP. I guess the $4 Billion increase in HP's market cap the day after Carly Fiorina resigned says something. . .

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    2. Re:Itanium is an astounding success by bill_mcgonigle · · Score: 1
      even a retarded 5 year old was smart enough to know Intel's posturing was 100% BS. Yet everyone fell for it.

      It's an interesting scale you lay out. We have:
      • Engineers
      • MBA's
      • Retarted 5 year olds
      It's left as an exercise for the reader to place those groups on the scale and answer the question you ask.
      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    3. Re:Itanium is an astounding success by bill_mcgonigle · · Score: 1

      Great post.

      The Alpha FX32 emulator was getting really good. Then Microsoft killed NT for Alpha.

      OK, they didn't kill it, they just told DEC they had to subsidize 100% of the cost of its development (same as PPC, MIPS). Vanilla, Vanella.

      So I guess you're right from that perspective - DEC wasn't selling enough of them to take on that cost.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    4. Re:Itanium is an astounding success by demachina · · Score: 1

      You left out the crucial element of the story. Intel signed a technology agreement with DEC, under the pretense that they would license the Alpha architecture. DEC gave them ALL the Alpha design docs. Intel read them all, and probably xeroxed them all, then said they weren't interested and sent them back.

      They then proceeded to incorporate most of what they learned from the Alpha design in to Pentium Pro, Pentium II, without paying DEC anything, and they quickly erased the performance gap between IA32 and RISC, and then with their vast resource left most of them in the dust. DEC won a court decision years later over it and got some chump change for it but DEC is dead and Intel owns the lion's share of the CPU market.

      Yet another example of how NOT having core values in your company is more likely to make you successful than having them. Successful business is brutual, ugly and largely devoid of ethics or values other than "Greed is King".

      --
      @de_machina
    5. Re:Itanium is an astounding success by Anonymous Coward · · Score: 0

      >HP promptly shat their pants

      AFAIK, the story is a little different:

      HP has this vision of the future and how you need to design CPUs to go faster than what you do today (we're talking ~1992 here) and will when just expanding on current ideas.

      Since they are PA-RISC people they put in a few ideas from that one along the way (to make sw/OS changes easier).

      Bigwigs at HP bring out their beancounters and look at the costs of manufacturing a new chip. Mucho $$$ they find. How can money be saved? Suggest a partnership with someone big who would want to get in on the Big Systems side. Intel sees a chance to muscle in and kill a few competitors and HP lets them do the talking.

      Intel does a Design By Committee and makes sure they get in a few of their x86-alike things they can't live without.

      End result: Big hodgepodge of (good) ideas that weigh down the chip and makes it hard to design on time and perform what was promised.

      The unintentionally funny thing is that the massive parallell resources that VLIW (and even more EPIC) was supposed to let you throw at your code wasn't there! The most recent (or is it the next) version has added more shift units and similar that should up performance and possible ILP. In the meantime the other architectures have 3/4/5 simultanous units in use of which there are typically two integer, load/store, float, and branch.

      Poor Itanium found out that "Moore happens".

    6. Re:Itanium is an astounding success by Mistah+Blue · · Score: 1

      Engineers = people who make stuff work

      MBA's = people who manage Engineers

      Retarded 5 year olds = executive management (i.e. CEO's) who manage MBA's

      Pay increases as you lose your brain too.

    7. Re:Itanium is an astounding success by Anonymous Coward · · Score: 0


      busses

      You worked with kisses? What, Hershey Kisses? Nice work if you can get it.

      Oh, you meant computers buses! Why didn't you say so?

    8. Re:Itanium is an astounding success by Anonymous Coward · · Score: 0

      Right. There's also the interesting part where Microsoft (a long time partner of Intel's) suddenly decides to drop Alpha support from NT. This was widely regarded as the first fatal blow on Alpha. Someone should dig deeply into why that happened... I have a small personal suspicion that there might be a monopolist just as bad as Microsoft out there.

  104. Itanium got too much respect... by dtjohnson · · Score: 1

    Itanium was expensive, had very poor backwards compatibility, had poor performance on existing software, required a complex compiler and intricate coding, and was notoriously finicky to get up and running. Even now, the only advantage that the article offers for Itanium is its gigaflops performance running a heavily-optimized floating point benchmark on a 4,096-processor system. I doubt if a line if forming to buy one, based on that.

    Based on what it offered to the IT industry, the Itanium got way more respect than it really deserved. If anyone other than Intel had tried to sell the world on the Itanium, they would have been laughed at for decades.

  105. Because it's for supercomputers only. by Anonymous Coward · · Score: 0

    It's heavily targeted towards highly hand-optimised, floating-point code. Ideal for scientific applications.

    But it runs hot, it can't be ramped up very much higher, and its average-case performance with the best compilers for its platforms are MUCH worse than best-case, and much closer to worst-case.

    The EPIC architecture positively demanded a much smarter compiler, and no-one outside a lab has been able to deliver on that.

    Couple in poor integer and branch performance, memory bandwidth that is outclassed by the Opteron in practice, and what is still a stupidly high price reflecting a niche processor for specialised scientific computing, and you realise that the Itanium2 is a good chip for a supercomputer which is running a hand-optimised scientfic application -- but absolutely bloody awful for anything else.

    Even Intel realised that for conventional servers and desktops, Itanium was an awful choice, which is why they begrudgingly adopted AMD's x86-64 as EM64T. Microsoft has abandoned future ia64 support in the Windows branch, leaving Linux as the only viable platform (which makes sense because that's what the supercomputers these days run anyway). Itanium has no general-purpose computing future, and never really had a general-purpose computing past.

    Intel were heavily over-optimistic, and overspecialised the processor without a compiler two-generations ahead that it needed to back it up. Since it's a bona-fide failure in everything but a highly-specialised niche (at which it is now only as good as the competitor POWER5, but more expensive), but Intel marketed it as an unsinkable powerhouse, the future of computing; the "Itanic" label is rather well deserved. Let it die; use an Opteron or POWER5 instead.

  106. it doesn't deserve any respect by Geekboy(Wizard) · · Score: 1

    sounds like the original poster hasn't actually used an itanic. they suck balls. big hairy moose balls.

    One of the biggest problems: You have to re-write your code to get decent speeds. People have code that is quite speedy on i386, macppc, sparc, mips, etc, but is dog slow on the itanic (both the itanic, and the itanic2).

    another problem: they have fast giggleboops, but they aren't really fast. a friend of mine works for an animation movie studio, and intel gave them a 32-machine cluster to try out for the render farm. so my friend put the itanic cluster against a 32-machine cluster of what they were currently using: 3 year old alphas. The alphas were 1.7 times faster. Even after an intel engineer came in to tune their machines, and massage the code.

  107. Re:Intel a victim of their own Intel Inside market by coats · · Score: 1
    Or has everyone forgotten Alpha? A totally kick ass CPU design killed by lack of native apps?
    ...and incompetent marketing and terrible management.

    Consider that Apple wanted to go with the Alpha for their Macs, and Digital wouldn't return their phone calls. The PowerPC was definitely a "second choice" for them. If there had been a major market for Alpha, and if DEC^H^H^HCompaq^H^H^H^H^H^HHP had had competent management, the computing world would be a very different place today.

    --
    "My opinions are my own, and I've got *lots* of them!"
  108. Its the software stupid. by Spazmania · · Score: 1

    Itanium was dead at the starting gate for the same reason PowerPC and Sparc are dying: Not x86 compatible; doesn't run x86 software.

    Sure, you can get the poorly tested Itanium versions of Linux, suffer through all the bugs that only express themselves on that architecture, recompile your apps, argue with the commercial vendors to get them to recompile their apps, etc. But why would you do that? At the end of the day the manpower costs far more than buying some extra servers.

    If Intel (or anyone else for that matter) wants to create a commodity non-x86 chip, they'll have to solve the chicken-and-egg problem with the software. Since that problem is nearly insoluble with the direct approach, they'll have to find another way around it.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    1. Re:Its the software stupid. by corngrower · · Score: 1
      Itanium was dead at the starting gate for the same reason PowerPC and Sparc are dying: Not x86 compatible; doesn't run x86 software.

      I don't think it is necessary to be x86 compatible to have a successful processor. It certainly will initially have a tougher go of it, but with open source software, it shouldn't be too hard to recompile and link to the new architecture. You do have to have good compiler support for the processor, however. From what I've been reading here, this is one area where Intel seems to have failed. What I read is that, although it is possible to write/generate code that executes efficiently on the Itanium, the current compilers do not do a good job of optomizing the code. And this is a decade after the architecture was announced.

      Another thorn in the side of this processor was that it was two years late, which is nearly an eternity when it comes to brining a chip to market. So although the specs for the chip were impressive when it was first announced, two years changes things a lot. Ask Steve Jobs about the NeXT computer.

      Finally, the first chips to come out ran hot. Not a good sign for reliability.

      Given all these things, the sales number prospects for the chip did not look good and software developers were reluctant to develop or port software to the chip. This leads to that chicken-and-egg situation where customers are reluctant to buy the chip because of all the aforementioned problems, and software developers continuing to push off expending software effort to support it because of poor sales prospects.

      The IA-64 architecture, or some other yet-to-be-developed chip using some of the same technologies still could be a success, but it would take a big push to get over the x86 momentum, and they'd have to execute the rollout of this chip in a much better fashon than what happened with the Itanium. That is, on time with a chip that does not test the limits of technology, and with a compiler that can produce very good optimized code. And the compiler would have to be free (as in beer) for any developers.

      Another thing - according to a different poster who actually uses and suppports a Itanium based systems, Linux runs magnificently on the Itanium.

      Personally, I wouldn't give a hairy rodent's rear about the architecture of the chip as long as there is enough software for it. And with lots of open source software out there, and the ability to compile and build it for the architecture (I'm not afraid of doing the mods necessary for porting some of it), with Linux and an excellent compiler, I'ld be a happy camper.

    2. Re:Its the software stupid. by Spazmania · · Score: 1

      according to a different poster who actually uses and suppports a Itanium based systems, Linux runs magnificently on the Itanium.

      Linux runs great on the AMD Opteron too. MySQL, on the other hand, currupts and truncates tables which it generally doesn't do on on 32-bit x86 machines. Probably something to do with 32 bit ints suddenly being 64 bit ints though it could just as easily be a one-off error buried in the libraries that doesn't express on a 32-bit architecture.

      On the AMD you can just run the 32-bit version on top of 64-bit Linux until the mysql bug is found. No such luck on Itanium -- you're stuck with it, warts and all.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  109. Funny by martin_b1sh0p · · Score: 1

    I just read a whole write up in the Sunday paper this weekend about a local (Colorado) company that is writing some new and cool stuff specifically for the Itanium processor. Matter of fact they used to work for HP / Intel I believe and set off to start this company. So they seem to think it's still got tons of potential and will still be the next big thing.

  110. Re:Easy Answer: It started as a flop by Anonymous Coward · · Score: 0

    Exactly, take a look at SCO for example. Despite their insane ramblings in public, the main point of their argument with IBM is as follows:

    1. They made an agreement with IBM for Project Monterey. SCO brought their UnixWare to the table, both sides brought engineering resources, and IBM promised $1mil in marketing.

    2. Around the time Monterey was done, IBM said that there was no market for 64-bit Unix and didn't do any of the promised marketing.

    3. SCO is so cash strapped, they have to sell out to Caldera, who renames itself "The SCO Group" and proceeds to go insane.

    If Santa Cruz Operation and IBM weren't so concerned about the Itanium, SCO (or maybe The SCO Group) would be in much better shape right now.

  111. Actually, it's still expensive by RelliK · · Score: 4, Informative

    Out of curiosity, I just checked itanic prices at dell. The cheapest configuration for a single (dual capable) 1.5GHz itanic with 2GB RAM and 36GB SCSI HD is over $17K. For comparison, a similarly configured 3.6GHz Xeon (also dual capable, 2GB RAM) is just over 5K.

    The article poster is simply trolling. Where the fuck can you get an itanic for $2000? The cpu *alone* costs that much! The article that the moron linked to confirms this: "The 1.4GHz Itanium 2 comes out Monday for $1,172 in 1,000-unit quantities. A 1.6GHz version comes out in May for $2,408 in similar quantities." (last paragraph)

    Need I give any more reasons for why it's not popular?

    --
    ___
    If you think big enough, you'll never have to do it.
    1. Re:Actually, it's still expensive by Predius · · Score: 1

      Hit up ION at http://itanium.ioncomputer.com/

      A comperable 2U box comes out at just under over 5k,
      1.5ghz I2
      36GB SCSI HD
      2GB RAM
      DVD ROM/CDRW
      Dual Gigabit

    2. Re:Actually, it's still expensive by Cheeko · · Score: 1

      HP's offering them for under $3,300 here. This is their Small/Medium business direct site too. Its very likely that if you dealt with someone directly and purchased an order it would be even less. So while $2000 isn't neccesarily correct, its far closer to the real price than 12k is.

    3. Re:Actually, it's still expensive by Anonymous Coward · · Score: 0

      fucking moron, that $17k is for dell's 4-way box.

      you can't get an itanium 2 system for $2k but you can get one for $3k:

      HP rx1620

      HP part # (HP rx1620 1.3GHz 3MB Bundle Solution Server) is $3,250. That's a nice 2-way (upgradeable to 4-core) capable 1RU box, probably the cheapest reliable system you can get for running HP-UX or VMS.

      If you really need a 64-bit server odds are you're going to spend so much on RAM that the price of the CPUs is going to be roughly equal (or maybe even less)

      anyway, you can go eat shit now :)

  112. Re:Easy Answer: It started as a flop by Anonymous Coward · · Score: 0

    real easy: change the name. It's not "itanium 2". It's "iridium" or whatever their newest name will be.

  113. WHY??? BUGS...BUGS...BUGS... by Anonymous Coward · · Score: 0

    In my corp it's not due any respect. Despite assurances of a stable state the processors led to numerous core dumps and app/os level crashes of various sorts. The vendor support for them sucks too. In short for serious prime time use when millions ride on uptime, these chips SUCK. I'm generally pro-Intel but in the 64 bit world AMD is currently alot better (assuming we're talking a Windows based OS...I don't have any *nix Itanium experience)

  114. The usual fallacy by mihalis · · Score: 1
    Given this, consider what a 2 or 3 Ghz Itanium could do.

    This is not the point. Chips that perform very well per MHz normally have longer (that is, more complex) pipeline stages that can't be clocked as high as chips that clock higher with more, shorter pipeline stages.

    It is only fair to compare chips delivered performance on the day you take your measurement, and then perhaps adjust for cost. You can't adjust for MHz or you'll get completely misleading results.

  115. Compiler tech by jesup · · Score: 1

    This sort of compiler technology goes back to the early days of RISC (MIPS, etc). The compiler has to schedule instructions, manage speculative execution directly, etc.

    If you think Itanium is complex, you should see some modern DSPs. 8 functional units/8 instructions per cycle, all sorts of dependencies on cross data paths, etc. Not to mention huge numbers of specialized instructions for working on multiple data (like "add 4 8-bit values to 4 others and saturate the results"). The compilers will not equal a good human, but they do a pretty darn good job.

    1. Re:Compiler tech by myrick · · Score: 2, Insightful

      The whole point of Itanium is that it doesn't deal with dependencies at all in hardware, thus making its scheduling very easy to implement (move these bits over here). It makes the compiler to all the hard work so it can just burn through instructions. Modern DSPs are pretty sweet, but 8 instructions per cycle is a luxury realized only because DSP is by nature a very repetitive exercise, so tons of resources can be poured into very sophisticated operations such as what you mention above. The pipelines aren't where Itanium's complexity lies. Instead, it is very feature rich elsewhere (supports both Endians, x86 emulation, etc.).

      --
      I'd rather be cycling.
    2. Re:Compiler tech by bani · · Score: 1

      the problem is that for itanium to be efficient, compilers have to be incredibly sophisticated. they have to get branch prediction near perfect (prediction miss is _expensive_ on itanium). they have to be excellent with huge register files. they have to be good with reordering, and they have to be good with VLIW packing.

      no compiler today is good at virtually any of this, even intel's own compilers. :-)

      in the end, VLIW turned out to be a very, very hard nut to crack. intel made a huge gamble on it and lost.

    3. Re:Compiler tech by Anonymous Coward · · Score: 0
      the problem is that for itanium to be efficient, compilers have to be incredibly sophisticated. they have to get branch prediction near perfect (prediction miss is _expensive_ on itanium).
      You do realize that Intel already solved the scheduling, prediction, and speculation problem in hardware. Doing it in software was just a matter of learning different mechanisms for accomplishing the same ends, which was done, which is why newer compilers get excellent results. (At least on the benchmarks I've seen.)

      Itanic's real problem is power consumption. The x86 instruction set encoding essentially serves as a form of data compression, as does running counters on the fly for branch prediction. Itanic expands those data paths to the full width using dedicated hardware, all of which runs in parallel all the time. The performance is incredible, but at a high cost in power consumption.

    4. Re:Compiler tech by antrik · · Score: 1

      > You do realize that Intel already solved the scheduling, prediction, and speculation problem in hardware. Doing it in software was just a matter of learning different mechanisms for accomplishing the same ends

      That's not quite true. The big difference is that the hardware implementation can do *dynamic* reordering, i.e. look at what's actually happening and cater to that. The software implementation needs to guess *beforehand*. This is quite a different problem. (And a much harder one at that.)

      > Itanic's real problem is power consumption. The x86 instruction set encoding essentially serves as a form of data compression, as does running counters on the fly for branch prediction. Itanic expands those data paths to the full width using dedicated hardware, all of which runs in parallel all the time. The performance is incredible, but at a high cost in power consumption.

      True. I wonder if Intel plans to introduce some kind of code compression, and how this could be done without forsaking the advantages of EPIC...

      --
      All my comments get moderated +-0, spotless.
    5. Re:Compiler tech by tjb · · Score: 1

      Yeah, the TI C6xxx compiler does a good job if you use the intrinsics and the correct #pragmas (generally to promise the compiler you aren't doing any pointer aliasing), but otherwise, you're just as hosed as the poor Itanium developer.

      This is fine for embedded DSP applications, where a large project is maybe 100KLOC and one guy can appropriately #pragma-bomb the entire codebase in two weeks; much less fine if you're writing a 30MLOC database application or galaxy simulator...

      Tim

  116. Why isn't it considered a "desktop" processor by snStarter · · Score: 1

    I see it reported as a server processor but not for the desktop.

    Why is this?

    Thanks

    1. Re:Why isn't it considered a "desktop" processor by Cro+Magnon · · Score: 1

      1. It costs waaaay to much for the desktop.
      2. It runs 32-bit desktop OS's like cold molasses.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  117. Re:Interoperability by Anonymous Coward · · Score: 0

    Your nick is quite appropriate for your post content.

  118. Alpha alpha alpha alpha... by argent · · Score: 1

    Couldn't (alpha) have (alpha) something (alpha) to (alpha) do (alpha) with (alpha) HP (alpha) stabbing (alpha) another (alpha) processor (alpha) in (alpha) the (alpha) back... one that didn't need heroic measures to get top of the line performance...

    Beating x86 is like kissing your sister.

  119. Wrong question by redelm · · Score: 3, Interesting
    Itanium gets _exactly_ the respect it is due. People pay as much attention as they want. Your question really should be phrased: "Why doesn't Itamium get the respect I think it's due?"

    That question answers itself: You think differently from most people. Highly specialized, hand optimized massively parallel predictable crunching seems to matter to you. It doesn't to most people. You're in a minority. Get used to it.

    BTW, i860 and Alpha suffered from basically the same problem.

    1. Re:Wrong question by argent · · Score: 1

      Alpha suffered from basically the same problem.

      If the problem is "no consumer software", OK, but then anything but x86 (and Power PC, at least for the next year or three) suffers from that.

      If the problem is something else, let us in on it. There's pretty much no comparison between Alpha and Itanium otherwise.

    2. Re:Wrong question by redelm · · Score: 1
      Dependancy on compiler instruction level multi-threading compiler technology. Later Alphas are 4-issue RISC. It's hard to keep the threads from stalling. Itanium is EPIC, very much the same thing (6/8 issue?).

    3. Re:Wrong question by argent · · Score: 1

      Later Alphas are 4-issue RISC. It's hard to keep the threads from stalling.

      Any modern processor has the same problem... I don't think any new core in the past five years hasn't been multi-issue, and most of them have bigger problems because they have longer pipelines and take a bigger hit when they have to stall the pipeline because of inter-instruction dependencies.

      The Alpha instruction set gives the CPU a lot of leeway in reordering instructions: the instruction set itself is very regular; it has bunches of registers to give the compiler maximum ability to avoid dependency problems; and the compiler can explicitly place barriers to give the CPU even more clues. It's really a lot like the Power PC, except with more and wider registers and less legacy cruft in the instruction set, and it got out-of-order instruction issue (like the G5) back when the "G3" was pretty spiffy.

      Now if you don't have OOO issue, the compiler has to work harder. We see that with the multi-core Power PC on the XBox, which is kind of an in-order version of the G5 core and the early comments from developers are that it's a big pain to write good code for.

      So, Alpha isn't exceptionally hard to deal with, it's actually pretty normal for 2005... and was already a typical 2005 design back in 1997 or so.

      It's a lot easier to generate good code for the Alpha than for something like the Pentium 4 where you have the same kind of scheduling issues and only 8 registers to work with and the relatively stupid "compiler" running in the CPU itself has to shuffle hidden registers around and guess at what it's really going to need.

      Itanium is EPIC, very much the same thing

      Not really. On the Itanium the way you express potential concurrency is to put the potentially concurrent instructions in a bundle, and the bundle size is implementation dependent with a slot for each functional unit. There's no leeway at all, here, the only way to get good speed on a new version of the architecture is to recompile for the larger bundles. For some people that's not that big a deal, like the control systems market where if you have relatively few customers and you upgrade the CPU at the same time as you upgrade the software you can keep them all in sync. But for commodity software it's a killer.

      Meanwhile, code that's good on a single-threaded Alpha is still going to run pretty well on a multi-issue one. You don't need to recompile the code to get all your bundles lined up with the functional units again.

  120. Don't do it Apple! by frostilicus2 · · Score: 1

    Wow that G4's fast! It is if you code in altivec. How many do? Very few. Wow that Itanium's fast! It is if you code for IA-64. How many do? Very few. Hey guys, Lets build an Itanium PowerMac!

    --
    Nothing sucks like a Vax, nothing blows like a PowerMac G4
  121. its the instruction set by Anonymous Coward · · Score: 1, Interesting
    VLIW as an archetecture is FUNKY. not the good kind of funky, either; nono, this is that slimy shit that cant be forgotten once you've been exposed...

    Itanic has its reputation because its a more fundamentally broken design than the i432 was...

    1. Re:its the instruction set by codeguy007 · · Score: 1

      Man did you ever butcher that Wilfred Brimley quote from the Firm.

  122. x86! by ShortBeard · · Score: 1

    It's the instruction set. It originally didn't use x86 (I have not kept up to know otherwise).

    It is actually a VLIW (Very Long Instruction Word) chip instead of CISC. Yup, it's a RISC chip but don't say that to Intel! It takes RISC instructions and strings them together to make a VLIW.

    That's why when vendors wanted to go 64bit they went with AMD chips, no porting. It can run 32bit and 64bit and it does it in x86 chip talk.

    So if you go with Itanium;
    1: replace x86 boxen with Itanium boxen.
    2: rewrite all your stuff for Itanium
    3: your boxen do nothing until step 2 is complete.
    4: ???
    5:Profit!!

    or you go with AMD Opterons;
    1: replace/upgrade boxen with Opterons
    2: keep running what you have while all your SW is updated to 64bits.
    3:Profit!!

  123. Hey, I work with Itaniums. by dlapine · · Score: 4, Interesting
    I have a nice cluster with ~1800 Itanium II's. It's fast, the CPU's stable, and it runs on Linux. I have a lot of hands-on experience with it.

    A couple of points that seem to have been missed when looking at why the itanium less widespread:

    • each CPU is quite large, having a square surface area for the unit about 2" x 5" and it's about 2" high
    • That area includes a voltage regulater and the passive cooling fans
    • It doesn't include any of the necessary active cooling
    If you add these physical factors to the points already made about heat, power and EFI bios, it's obvious to say that Itanium won't run in your mini-ATX destop or laptop. This isn't a slam on the design, as it was never designed to run in those form factors, but it's hard to see how any cpu today is going to have a wide use if it isn't available for dual use for destop and servers. Once you eliminate the desktop market, (and I'm going to lump the workstation market in with the servers) the number of places you can sell these processors drops considerably.

    Once you start adding in the lack of Windows support for itanium, the strides that the 86_64 architechture has made in capability, and the low numbers of current adopters, it's not looking like Itanium will ever gain widespread acceptance.

    --
    The Internet has no garbage collection
    1. Re:Hey, I work with Itaniums. by Will+Sargent · · Score: 1

      Okay, I know logically there must be a reason why Itaniums exist (someone buys them), but the mind really boggles at the idea of ~1800 Itaniums on a cluster. At what point is it more cost effective to buy an Itanium than a gaggle of Celerons for CPU power? Is there really that much of a compelling advantage to buying a $2000 chip?

    2. Re:Hey, I work with Itaniums. by Anonymous Coward · · Score: 0

      Because not all of those nodes are in a cluster - 1024 of the Itanium 2's are in NCSA's Altix supercomputer. The NCSA's Altix is a shared-memory machine with a few terabytes of RAM, so all those itaniums can work together on the same (very large) problem. (Actually, it's split up into 2 512 processor systems, one with 1T RAM, and the other with 2T)

      That might sound excessive, but there really are some scientific computational problems which can not be easily split up so as to work efficiently on a cluster (many machines with relatively small physical memory). For those kinds of problems, you need a shared-memory machine. I may be wrong, but I don't believe that it is possible to wire together that many Celerons or Xeons or what have you, so cost-effectiveness doesn't apply.

      The other 887 Itanium 2's are part of NCSA's TeraGrid cluster. I'm not sure why they were chosen for that - I'd assume it was for there floating-point speed and memory bandwidth.

    3. Re:Hey, I work with Itaniums. by dlapine · · Score: 1
      Um, we actually have 937 total nodes, each of which is at least a dual cpu node. We have 8 login nodes that are quad cpu. (slightly older 1.3 Itanic II's)

      The 887 nodes break down into 256 dual 1.3 and 631 dual 1.5's. The other nodes function as support, storage or mgmt.

      If you do the math (931 * 2 + 8 * 4) we get 1894 Itaniums in a cluster.

      More impressive is the fact that we had gige and myrinet for everynode in the cluster waaay back in 2003. :) Plus the 1024 Itaniums in the Altix.

      I'm not going to talk about why we bought Itanic, my boss is looking at me. :) Suffice it to say that we had good reasons to look at Itanic, did our research on all available options and put the cluster up for open bid.

      --
      The Internet has no garbage collection
  124. Bullseye! by Darth+Daver · · Score: 1

    Most comments are from teenagers who parrot crap spouted by bitter, old fans of Alpha.

  125. It's expensive by Sloppy · · Score: 1
    The reason no one takes it seriously, is that it is ridiculously expensive. You can get more computer for less money by buying something else.

    Even the link to the article about how much cheaper it has become, says this:

    The 1.4GHz Itanium 2 comes out Monday for $1,172 in 1,000-unit quantities. A 1.6GHz version comes out in May for $2,408 in similar quantities.
    That price is less outrageous than past prices, but it's still not competitive in the real world.
    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  126. Re:Easy Answer: It started as a flop by QuickFox · · Score: 2, Funny

    Hundreds and hundreds of products have been killed or permanently crippled because their first versions were terrible.

    There's the answer! Now it's clear what has to be done to make this processor a success!

    The first version was terrible, you say? Well, then simply apply the one and only strategy that always guarantees that an absolutely horrible first version becomes a great market success.

    Put a sticker on it with the name "Microsoft".

    --

    --
    Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
  127. Three words... by Anonymous Coward · · Score: 0

    Price, heat, and power.

    The Itanium is a very good performing 64-bit processor, BUT it's expensive (mostly because of the outrageous cache sizes), it's hot (mostly because of the outrageous cache sizes), and it draws a lot of juice (mostly beca...well you get the picture).

    It's also a bear to write apps for. Intel did a lot of work on the compilers, and they are very nice, but there are a limited number of OS options for it and they are randomly stable depending on from whom you bought the hardware. I guess if you're going to setup a small server that's not going to do much that would really require a 64-bit processor you can make statements about OS options, but if you're going to use the machine for scientific/engineering work there aren't a whole lot of options (SUSE and RHAS).

    I do agree, it's a great processor IF you can afford it (and I don't mean the initial sticker price). Let's also not forget the small production volumes and the near decade of R&D to get a working chip.

  128. Why It's Not For Me... by Nom+du+Keyboard · · Score: 4, Interesting
    Having an affordable chip one step above a Xeon or Opteron in floating-point performance would not be such a bad thing for gaming enthusiasts (or 3D artists).

    Why this chip is not for me are two reasons:

    1: I'm not buying one before the software is ported to it -- and at a comparable price to its PC equivalent!
    2: It may be a step above an Opteron for floating point, but is it still that step about a dual processor Opteron that I can buy today for less money than a mono-processor Itantium?

    As for the "Itanic" jokes (all of which are way off-base, since heat output of any H.M.S. Itanic would melt any iceberg long before it could do any damage), blame The Register. I saw them use the term long before anyone else.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  129. my experiance by Anonymous Coward · · Score: 0

    well, from my experiences with this chip...

    The first versions were so terrible that it soured alot of people on the whole line.

    The Itanium2 is a big improvement over the first generation, and if you are willing to hand tune all your code in assembler you can get some very respectable performance. The reality is that if you compile your code with any current compiler and test the Itanium against the opteron the opteron will win. There are exceptions but this is what I have seen.

  130. Itanic Iceberg: Memory Access Speed by m0ntar3 · · Score: 1

    Namaste,

    Here's a reason: P4's are like DDR667, Itanic's are like DDR266.

    Incidently, an IT guy might find a performance increase for some applications when migrated from 64-bit big-iron HP/IBM to big-aluminum like x86 w/ the memory extensions---due to faster memory speeds. FP perfs aren't so import when you got WSL sloshing around in 32G of RAM. What might be more import is how fast can you read that 100M java object.

    The big deal with Itanium is that it's a change in ISA (Instruction Set Architecture). The 32-bit to 64-bit jump on Intel/AMD isn't a fundamental shift in ISA like the Itanic, hence migration is less complicated.

    It's like moving from the United States to Canada. There are cultural differences that make for some adjustments, but there are enough folks speaking English to get along. Unlike, moving from India to the United States, where hardly anybody can speak Sanskrit :)

    AUM, Shanti

  131. Simple by bored · · Score: 4, Informative

    Your quoting FP performance. The "integer" (aka general purpose) performance isn't nearly as competitive. This is because its a static VLIW machine, and its hard to write a good VLIW compiler. Writing fast FP code is simpler. Then there is the fact that the Itanic is 3x the hardware of the machines your comparing it to. Bigger caches, and all that. Your misunderstanding of clock rate is also simplistic. In order to get the Itanic faster they would have to create a longer pipeline, this would more than likely decrease the IPC and keep the processor from scaling lineraly.

    Basically it was pointless. we don't need yet another processor targeted into the same market the POWER64/SPARC64/PARISC and now the X86-64 etc are in.
    The whole arch is a mess in my opinion its accually probably worse than the x86, this is evident in how long it took to get the thing out the door. For a processor based on the idea that superscaler wasn't easy and wouldn't perform its beginning to look like the itanic is accually in that boat. Its a dead arch, there are orders of magnitude more x86-64 machines out there even though the itanic had a two year lead. Why should I use itanic when there is a larger software base for PPC/POWER and its multivendor?
    POWER is cheaper,faster and more mature and it can barely compete with x86 in the desktop area. ARM has pretty much taken over the smaller chores (cellphones, PDA's MP3 players etc..) and smaller chips like the 8051 clones sit below that.

    Give it up, it was stupid, Intel was wrong. My opionion is that itanic was a marking plan to lock up the processor market. If we were all forced to run itaniums back in 96-98 then we would all be buying intel chips for everything. Instead intel had to release the P-Pro to keep ahead of Cyrix/AMD, only they never got far enough ahead to kill AMD to release the pressure and transition everyone to Itanic, where theyhold all kinds of patents and copyrights on the instruction set. Plus they couldn't make the thing work and it slipped for 5 years.

  132. Yes, do consider... by Nom+du+Keyboard · · Score: 1
    Given this, consider what a 2 or 3 Ghz Itanium could do.

    Melt?

    (Aiming for the PITHY +1 Moderation)

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  133. Performance etc. unrelated to popularity by Anonymous Coward · · Score: 0

    It should be obvious that the quality of an architecture is now totally unrelated to its popularity: the x86 heap-of-shit is now so popular that it's being used by people like Sun and Apple in place of superior architectures. "Compatibility" and "low risk" are seen, rightly or wrongly, as more important than the technical attributes of the processor. Other processor vendors have found this out in turn over the last decade. Somehow, Intel were the only ones who hadn't noticed.

  134. BINGO by e40 · · Score: 1

    To drive this point home even more: we were told by Intel that to do our own code generation was not recommended. They recommended that we use their C compiler backend. For us, this was not an option, and we never did the port.

  135. gamerz want ghz by Anonymous Coward · · Score: 0

    No gamer is going to buy a 1.4ghz chip over a 2.4 regardless of the actual speed.
    What are the fast chips? DX20-133mhz now? They would prefer a dx50-60mhz chip if intel could make it.

  136. It doesn't deserve much respect by turgid · · Score: 3, Informative
    For about the millionth time:

    itanium (itanic) is a poor design for anything other than numbercrunching. It is a relic of theoretical supercomputer designs that were popular in the late 1970s. itanic shines on floating-point benchmarks, and is mediocre at best on everything else.

    Since the late 1970s, we have had RISC and then superscalar RISC, some now with elements of VLIW. This provides better real-world (general-purpose) performance using substantially less power and fewer transistors than itanic.

    Modern RISC processors (including x86 which are RISC internally) can reschedule execution of instructions dynamically (i.e. at run time). itanic can not. It relies on the compiler to schdule the code. It is only possible to schedule code well at compile time for very well-defined problem sets i.e. floating-point maths intensive programs like numerical simulations. NASA currently owns 5% of the world's itanic processors (in a single machine).

    itanic was intel's attempt to kill the 64-bit RISC market, putting all of its competitors out of business. Like all great megalomaniacal plans, it has failed. It was a marketing-driven processor, and a failure.

    It can't compete with clunky old UltraSPARC IV on server-oriented workloads. Even that market, which isn't big enough to sustain Sun and its processors, is orders of magnitude bigger than the market in which itanic has any relevance.

    For big servers nowadays, you have a choice between Opteron and POWER.

    In science and engineering, you're often better with something like Opteron, POWER or something fancy from Cray, NEC or Fujitsu. itanic runs hot and consumes too much electricity.

    Has anyone ever seen one? I haven't. There was one at a show once on the Red Hat stand, but they wouldn't let me performance test it... and they wouldn't even let me see it because it had over-heated.

    itanic is about the most expensive turkey in computing history.

    1. Re:It doesn't deserve much respect by damicha · · Score: 3, Interesting
      just a little detail from a purist assembler coder:
      in real supercomputing you do not want your processor to 'auto-schedule' or rearrange your code.


      in the end, real special code is still hand oprimized, since no compiler nor any built-in rescheduling algorithms can actually know what I really want to achieve.


      Maybe I just want to accept the half ready value because I don't care for part of it.


      Maybe I want to put one instruction way ahead to prime a set of registers for what is coming.



      A processor which is always auto-scheduling can achieve only performance within the foresight that the rescheduling design put into it. But not for my very special algorithm for just this one dumb equation I want to solve.


      It is not a 'fail' criterion for a processor to strictly adhere to what I tell it, and thus provide an exactly reproduceable solution path each time.


      The result of this automatic rescheduling is that execution times in the end become non deterministic. In some cases you just want to avoid that.


      The scope is for sure not gaming, but hand optimized supercomputer grade code: check the compiler's result over and manually squeeze clock cycles out by doing things that seem to put cycles in, but reward in the end because one 'senseless' instruction may just have served to prime a cache o, register file, or vector set with new content for the next run, just in time when the pipe runs empty.

      Curious why the DecAlpha does not appear in these posts....

  137. Re:because it's a failure by pete-classic · · Score: 1

    Thanks for answering. Double thanks for not being snarky!

    It's like a whole new slashdot.

    -Peter

  138. Fashion. by Timbo · · Score: 1

    Pure and simple.

  139. This was somehow a worthy article???!?!!?!? by What+me+a+Coward · · Score: 1

    I mean really what idiot thought we were stupid enough to buy this garbage let alone eat it????

    I guess Cliff does.

    Tell you what cliff why don't you go jump off a cl....

    No sorry it's to easy and you're not worth it.

    But i mean God seriously itanium? just what were you smoking anyway.

    --
    Coward? Coward! Thems fighten words!!
  140. Re:the problem is those are well optimized benchma by Surt · · Score: 1

    Well, from what I've seen, in #1, itanium is rarely the faster solution. Particularly in, say, desktop productivity suites. But even if it is close or marginally faster, it still has to contend with #2, which may well improve with motherboards that support xeon/itanium, but my guess is that pentium optimized motherboards will continue to rule the desktop. You certainly may start to see more itaniums in servers if the price is more competitive. As to #3, AMD64 retains the enormous advantage that even if you can't get 64-bit drivers, you can sit in 32-bit mode and still get a great price/performance deal.

    --
    "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  141. I had an Itanium in my office once... by Anonymous Coward · · Score: 0

    ... it kept me warm in the winter.

  142. Pentium Pro was not a flop by Anonymous Coward · · Score: 1, Informative

    The Pentium Pro was not really a flop. The PPro was faster and better then the Pentium. Operating systems such as Linux, FreeBSD, OS/2 and WindowsNT all worked very well on the PPro. The problem was that the PPro was optomized for 32bit opperations. Software that used 16bit opperations took a performance hit (25% slower IIRC). This was a big problem for Microsoft as Windows 95 still used a lot of 16bit code (as did 98 and ME). At the time Microsoft had no plans for a consumer based 32bit operating system. Intel was basically forced to redesign the PPro for better 16bit performance and the Pentium 2 was born. In the process some of the more server oriented features of the PPro were stripped such as SMP and 36bit addressing.

    1. Re:Pentium Pro was not a flop by petermgreen · · Score: 1

      i heared that the big problem with the PPRO was that manufacturing wasn't really ready for on die level 2 cache with the result that yields were low and therefore prices high.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  143. slow chip?!? by SolusSD · · Score: 1

    Was your company database software compiled for the Itanium.. or were you guys using the x86 emulation mode? (i sure it was the latter... otherwise your results would be quite different). the parent (by jarich) needs a psuedo-mod of uninformed

    1. Re:slow chip?!? by jarich · · Score: 1
      Was your company database software compiled for the Itanium..

      Yup. The database was MySql compiled natively for the platform.

      or were you guys using the x86 emulation mode? (i sure it was the latter... otherwise your results would be quite different).

      yeah, a lot of people are really sure... but that don't make it true. I always opt for experience over expert opinions and press releases.

      the parent (by jarich) needs a psuedo-mod of uninformed

      Well, one of us does anyway. ;)

  144. Re:the problem is those are well optimized benchma by Anonymous Coward · · Score: 0

    1) compare the performance of itanium with xeon/opteron in running native IA64 code.

    2) and 3) don't match, since "real end-user systems" won't run Winblows XP. Windows Datacenter 2003, maybe - but not XP.

  145. Excellent point, but as a processor... by Anonymous Coward · · Score: 0
    It was massively over-hyped, and then underwhelmed.

    Compatibility may be an issue with volume sales, but the Alpha was definitely respected in a way the Itanium is not.

    And the reason is that just keeping up with x86 is not good enough. What Intel was saying was exactly what had to be true to make it worthwhile to introduce a new processor: we will leapfrog the x86 and enter a whole new world of gigaflop goodness.

    If they had managed to deliver the performance - meaning performance far in excess of x86 processors - then there would have been respect, and they could have worked on the price. But just keeping up with the x86 is uninspiring.

    Add that to the initial wild promises, and you get even more cynicism.

  146. maybe it'll change by halfelven · · Score: 1

    Currently, Itanium is pretty much exclusively used in really high-end machinery such as SGI supercomputers, which are not really within the reach of the ordinary computer enthusiast. So, since there are more urban legends about the chip than actual knowledge, it's easy for such myths to spread.
    But there are some trends that seem to push this chip outside the exclusive markets - e.g. the aforementioned SGI is working hard to translate its knowledge in the field of supercomputers into things more accessible, such as high-performance enterprise servers. If Intel makes concessions to the price, those high-performance servers might actually use Itanium.
    Of course, if Intel keeps the price high, then those "small supercomputers" will just use some other CPU, to keep the total price down.

    Bottom line: it's a perception thing. It's easier to ridicule what is not known, hence the "Itanic" myth.

  147. Why the Itanium failed by Targon · · Score: 2, Interesting

    First off, remember that the current Itanium is the Itanium 2. The original Itanium was a failure in almost every way.

    A reason why the DEC Alpha and other processors died wasn't because of a bad design, it was because the software support wasn't there. Think about it, if you could run all your Windows apps under Linux, more people would run it. The difference in what software is available is a big issue. Sure you can recompile many things to run on a given piece of hardware, but for endusers and even when it comes to servers, if a company needs to spend a lot of time making a program run well on a new architecture, and it doesn't sell well, it's a waste of resources to do it.

    So, look at the current market. The Itanium 2 is horrible when it comes to performance under Windows 2003 or Windows XP. If you have native support, then the performance comes up to speed a bit better, but compare that to the performance of an Athlon 64/Opteron and the P4/Xeon chips.

    Then you have the issue of how fast does it do in the real world. Theoretical performance in benchmarks is one thing, but how well does it work in a real-world environment? Can you say that the Xeon can hold it's own against an Opteron with a multi-processor system? In some applications it can, but as time goes on, AMD has tweaked the Opteron and Athlon 64 design so even in areas where Intel has dominated in the past, AMD is getting much closer in terms of performance.

    Why go to a new architecture, which means all new software when you can stick to a tested architecture that runs all your current applications faster?

    The Itanium 1 is like the Pentium Pro. In theory it was better because it dropped the legacy support that plagues the x86 world, but since it failed to be better at running the current/older software for the x86 world, it didn't do well. Eventually the Pentium Pro design was used in the Pentium 2, and as a result it did well, but the original implementation was horrible.

    The Itanium 2 design may eventually make it's way into the current x86 world(compatability and such), but very few would be willing to switch to it.

    The Opteron/Athlon 64 design is up to 2.8GHz, and is expected to eventually make it up to the 3.8GHz mark which is where the highest end Pentium 4 processor is. All things considered, I'd stick with the Opteron for multi-processor systems, or Athlon 64 FX 57 for single-processor. You get the best of all worlds without the drawbacks.

  148. If the best argument... by Hymer · · Score: 0

    Intel & HP could give for a upgrade from Alpha to Itanium was/is: "Easy migration to MS Windows Server and MS SQL server", what bloody respect do they deserve ??

    The whole Itanic story is based on this Windows compatibility and migration to Windows. The power Itanic deliver is not better than what the target market allready have... and the Windows aspect is not a argument in the UNIX world.

    They don't deserve our respect... they do everything they can to insult us...

  149. Quacks like a Duck by Nom+du+Keyboard · · Score: 1
    On giving this a calm reading some things jump out:

    I am not affiliated with the Itanium or the top500 list in any way.

    Sounds like PR Bilge to me. And if only FP performance mattered, then the Cell processor would Rule Them All.

    As in recent years the Itanium does well, easily beating x86 processors even at its low clockspeed (1.4Ghz).

    See note above about FP performance not being the be and end all of what many of us use our processors for.

    We'll be paying for x86 compatibility indefinitely.

    Don't know about you, but I think we'll pretty much all be running under the quite-a-bit-nicer AMD64 a lot sooner than indefinitely. Even holdout Apple has now blessed the Intel ISA future roadmap.

    So it's statements like the above leading me to call it Bilge.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  150. Re:because it's a failure by Anonymous Coward · · Score: 0

    Java, and most other byte compiled languages, perform quite poorly on processors with heavy branch prediction penalities. If Intel thought Java was going to be the key to Itanic's success, then Intel's left hand and right hand were having a serious failure to communicate.

  151. Code sparse by regjoe · · Score: 1

    No code for the chip has really been written to take advantage of its security features. Therefore it acts just like an avaerage chip. Take a look at this article from The Denver Post on the subject http://denverpost.com/business/ci_2848039

    --
    Indecision may, or may not be my problem! -- Jimmy Buffett
  152. Second Processor is a Killer by Nom+du+Keyboard · · Score: 1
    Price drops have already had some effect. In 2002, a two-processor Itanium server cost about $18,000 (£9,859). With the new chips, a similarly configured system can sell for less than $8,000, while basic one-processor Itanium servers will go for just more than $2,000.

    Boy, that second processor for only $6000 over the single-processor system is a real killer. Definitely a Beowolf cluster of single-processor boxes is the way to go.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  153. 99% of the replies are not relevent by Anonymous Coward · · Score: 0

    The pc-centrix /. crowd who thinks a 2x is big have no clue what an itanium is for.

    1. Re:99% of the replies are not relevent by Anonymous Coward · · Score: 0

      Referring to your subject: you been reading /. long?

  154. Re:The overclocking by Anonymous Coward · · Score: 0

    In Soviet Russia, the Itanium...sells!

  155. Intel == Engineers vs. Marketing by tdsanchez · · Score: 1

    Intel has the same problem as Microsoft... Product development over the last decade has been driven by marketing, not by developing good technology.... They've spent millions adding features and bloat to their respective products for the purpose of marketing, and the results are Itanium, Pentium 4, and (for Microsoft) Windows XP. Both companies' 'product segmentation' also is to blame... Itanium -could- be a mass market chip -if- Intel didn't need to keep it's prices high in order to prop it's gross margins.

    And why are AMD and Apple technically 'better' than Intel and Microsoft respectively yet have low(er) market share? Because their focus has been on technology. To compete, they HAVE TO be better than Intel and Microsoft, so their money is better spent on true R & D, not marketing. Since Microsoft and Intel still enjoy the benefits of economies of scale IBM handed them in the early 80's.

  156. Itanium is the new P6 by cyanics · · Score: 1

    Might turns some heads at that remark, but think about it like this.

    The Pentium Pro, the True P6 chip, that was developed during the early 90's was nothing to anyone, except in business / mainframe environments. The P6, with its true cores and integrated memory, was hands down the champ, when compared to the P5. Amazingly enough, every incarnation of the Intel X86 processor is STILL based on the P6. Yes, there have been improvements (MMC, SSI, HT, DC, etc) but the core design principles themselves have remained unchanged.

    The Itanium (which sucked ass when I was developing on it) was a new start, at a new core. Itanium2 (which is what became available shortly after Intel realized how bad the I1 was) was a push to market.

    Now, a few years have passed, and AMD got the great idea of releasing the x86_64, to act as a bridge between 32bit and 64bit. Intel IA64 requires wholly new programs to really take advantage of the 64bit, whereas Opteron/64 don't.

    Intel then realized its mistake, in not creating a 64bit bridge. Tadaa! EMT64 comes out.

    But what is happening on the back side? Itanium going away? No. The ia64 will continue, just at the p6 did. Give it a few years, and you will find that x86ia64 chips are starting to be developed. That being, a single chip with a front side x86_64 implementation, and a backside ia64 implementation. These chips will act as a branch point between the two architectures.

    Intel will continue to develop, until the market has reached the necessary 51% saturation, and then start phasing out x86.

    Processor development is near linear. If clock speeds can't be increased, you increase the core count. When core counts can't be increased, you increase to bus width. Lather, Rinse, Repeat.

  157. Intel Taking Lessons From Microsoft by Nom+du+Keyboard · · Score: 1
    Intel is clearly taking lessons from Microsoft. A couple modest examples:

    1: Both are monopolies (Intel case is being proven now).
    2: Both want to continue acting as if they not monopolies.
    3: Both are taking until Version 3 to get it mostly right.

    Case closed.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  158. Why doesn't ppc970 get respect? by Colonel+Panic · · Score: 2

    Given your little performance comparison chart:
    rank processor ghz (gflops / #procs) speed
    #5 ppc970 2.2 (27910 / 4800) 5.81
    #7 itanium2 1.4 (19940 / 4096) 4.86
    #10 opteron 2.0 (15250 / 5000) 3.05
    #20 xeon 3.06 (9819 / 2500) 3.92


    Maybe the question should be, why doesn't the ppc970 get the respect it deserves? I suspect that the ppc970 has a much smaller die than the itanic. Sure the clock speed of the ppc is 0.8 GHz higher, but who cares if the ppc costs 1/2 to 1/4 as much? Also, it would be interesting to know how much power each of them uses.

  159. Re:The overclocking by drakaan · · Score: 1
    Speaking of overclocking...if you adjust the "speed" calculation to allow for clock speed, you end up with (numbers in parentheses are (gflops/processors)/procspeed):
    • #5 ppc970 2.2 (27910 / 4800) 5.81 (2.64)
    • #7 itanium2 1.4 (19940 / 4096) 4.86 (3.48)
    • #10 opteron 2.0 (15250 / 5000) 3.05 (1.53)
    • #20 xeon 3.06 (9819 / 2500) 3.92 (1.28)

    I'll admit, I've fallen for the "Itaniums suck" line, but clock-for-clock they appear to be speedy, based on the numbers given. Now if only I had a beowulf cluster of 3.06 GHz Itaniums...

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  160. Operations per kilowatt-hour by volts · · Score: 1

    Itanium is (or used to be) very power hungry. When Itanium released, someone from Google remarked that they had no interest in Itanium because electricity was a very large operational cost.

  161. Ummm, that's what the Itanium is for by Sycraft-fu · · Score: 1

    You might have guess form the price that it's not a desktop chip. It's designed for high performance FP calcualtions almost exclusively. There's a market for that, we have an Itanium cluster here for just that reason.

    I think that's part of the reason people hate on it on Slashdot, is they think it could and should be deisgned for their app, which seems to be webserving and scrolling text for the large majority. It's not, for that, Intel's solution is the P3 and P4. The Iatanium is if you need to crunch massive amounts of FP data for research or modeling or whatever.

    I think it would be like hating on ARM (Xscale in Intel lingo) chips because they don't run at 1ghz+ speeds and have no FP unit. Well the reason for that is they are designed to be low power embedded chips, and they do so brilliantly. That they don't complete performance wise with a P4 isn't relivant, they aren't designed to.

    In the market that it was designed, the Itanium seems to compete fairly well. Like I said, a research group here got a cluster of them. Reason was they calculated it to give them the most bang for their buck for the kind of work they do. Now their desktops are all P4s, wouldn't want to waste money on an Itainum there, but that doesn't mean it's worthless.

    1. Re:Ummm, that's what the Itanium is for by timster · · Score: 1

      Sure, you're completely right. Like I said, great for science or whatever. The question, though, refers to it as a potential mass market chip.

      Of course, Itanium has always been referred to by Intel as a high-end chip, and never really as a mass-market one. Slashdotters, I suppose, are inherently the kind of people who think Space Shuttle main engines are useless because they can't have them in their cars.

      I do think that Intel hoped Itanium would work out a little better than it did, though.

      --
      I have seen the future, and it is inconvenient.
    2. Re:Ummm, that's what the Itanium is for by Sycraft-fu · · Score: 1

      Oh with out a doubt, Intel hoped that the Itanium would be The Next Big Thing(tm) and that all computers would go IA-64. That would have effectively shut AMD out of the market. Well they realised that wasn't going to work and finally threw in the towel and are now making x86-64 chips. However the Itainum remains great for high end FP work, and Intel will continue to sell it for that.

      At this point it means they have basically a total lineup. They have Xscale/StrongARM for low end embedded apps, the P4 for desktops/worksations/servers, the PM for laptops, and the Itainum for high-end computations. They bascially can compete at any level.

    3. Re:Ummm, that's what the Itanium is for by antrik · · Score: 1

      > Oh with out a doubt, Intel hoped that the Itanium would be The Next Big Thing(tm) and that all computers would go IA-64.

      I remember Intel announcing somewhere around 1998 that IA64 won't be for the mass market at least until somewhere around 2008 or so.

      Sure they hoped some day all computers will go IA64, and most likely they still do. But they never expected it to happen very soon.

      --
      All my comments get moderated +-0, spotless.
  162. clustering by Exter-C · · Score: 1

    I was recently involved in a build up of a clustered system. We evaluated several dell based Itanium 2 servers. At the end of the day we had issues with stability when we started to MOSIX the itaniums, It seemed as though there may have been less development in resolving bugs. That maybe because of the cost being so dam expensive originally. In the end we got better performance / £ to use an Opteron based system. In the next few weeks we will be taking the nodes down to upgrade to dual core processors and they are STILL cheaper than the Itanium processors from Dell. Total cost of ownership made it better to NOT use the itanium and buy an extra nodes and get better redundancy etc.

  163. anyone remember the i-986? by peter303 · · Score: 1

    I recall the time Intel tried to introduce a non-X86 compatible CPU in the 1980s, it flopped because it didnt have good compilers and applications. It was called the i986(?). I recall it had special CISC intrustion to optimize object-oriented computing. I cant find it on Google, probably because this was pre-web and people dont write much about failures.

    1. Re:anyone remember the i-986? by Hymer · · Score: 0

      I think you are reffering to the I860... it is now known mainly in the microcontroller version called I960.
      The I960 has been, and still is, used in many RAID-controllers. AFAIK it was a RISC CPU but I'm not sure...

    2. Re:anyone remember the i-986? by Anonymous Coward · · Score: 0

      The i860 and the i960 were two entirely different CPUs. The 860 has died completely I believe, while the 960 does live on.

    3. Re:anyone remember the i-986? by Anonymous Coward · · Score: 0

      Google for Intel 432. Special support for Ada; instructions were variable-length, up to several hundred bits.

    4. Re:anyone remember the i-986? by thebagel · · Score: 1
    5. Re:anyone remember the i-986? by demon · · Score: 1

      Or maybe the i432 (aka iAPX 432). See http://en.wikipedia.org/wiki/Intel_i432 for information.

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
    6. Re:anyone remember the i-986? by the_greywolf · · Score: 1

      i have one such controller. any tips or information on how i could test it and possibly use it? it's just sitting in a box right now.

      --
      grey wolf
      LET FORTRAN DIE!
  164. 3 GHz chip by AvitarX · · Score: 1

    I imagine the 3GHz Itanium does a great job power Santa's Desktop.

    It makes as much sense as imagine what a 6GHz G5 would do or an 8GHz Pentium IV.

    They all do nothing because they don't exist. I don't really know much on the subject, but my understanding is designs can be made to clock real high but do less per a clock (P4) or clock real low and do more (Itanium) or somewhere inbetween (G5 Athlon).

    I know there is more to it then that, but part of the reason the P4 is so inneficient is it was designed that way. The reason the P4 clocks so high is that it needs too, the reason it needs to is it was designed that way, and the reason it was designed that way was so it could clock high.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  165. Did you ask SGI? by haeger · · Score: 1
    According to them, a single image, large memory machine is what they're experts at. From what I've heard from them at different seminars they do what you ask quite successfully for quite a few companies.

    Actually I think they chose the Itanium specifically for its ability to handle large memorysets.

    The Altix is the machine you're looking for I think.

    .haeger

    --
    You are not entitled to your opinion. You are entitled to your informed opinion. -- Harlan Ellison
  166. Looks like... by sallgeud · · Score: 1


    You'd need approximately 7967 2GHz opteron processors to perform as well as 4096 Itaniums.

    Opteron 846 (2.0GHz) which was used in this system.... $675 OEM or $775 Retail.

    Itanium 2 (1.4GHz) used in the compared system is approximately $2050.

    $8.4 MEEELION for Itanium 2 system

    $6.2 MEEELION for Opteron 846 system

    Opteron runs standard 32 bit x86 stuff (read: compatability)... is easier to support (read: very common architecture).. and is cheaper...

    Here's a $12M budget for the next few years to buy new hardware.... do you want 1 Itanium 2 system or 2 Opteron systems (twice the power, and all the other stuff).

  167. Another Reason the Itanium (Intel) Sucks by gear-falcon · · Score: 1

    Here is someone elses great explanation for why Itanium/Intel suck...

    "Itanium however, is completely based on the future. It has no real history. Only 2-3 processor releases, and all the big server sellers are getting behind it. And if you were to judge Itanium by Intel's history, you know that when Intel pushes something, it happens. I know they too have had failures, but seeing the big server oems get behind this should be a good clue to where this is going. Alpha engineers were acquired in 2001. Merger took place a year later. Not sure if Intel knew about the merger when they were making the deal. I think they were just trying to buy Alpha IP, but I could be wrong about that.

    Intel pushed Rambus in a huge way and was flatly rejected by most consumers as being too expensive at the time. This lead to AMD picking up a few crucial market share points as i recall from history. So much for Intel's strong arming there. Itanium's history is what, 10 years or so at this point? Over 10 billion dollars invested in R&D. It is the love child of Intel desperately wanting a big chunk of the big iron market and HPQ's dying PA-RISC. As it stands right now Intel has almost ZERO market share of the big iron market, that is still ruled by SGI, IBM and SUN. Yes, lets discuss why Intel was buying Alpha IP shall we? Could it have anything to do with them blatently ripping off DEC Alpha tech and getting caught and rather than facing an incredible lawsuit they decided it would be much more cost effective to just buy the company?

    You like to clamor about how Itanium adoption is a given for all of these leaders of big iron technology. Lets look a little closer as to why this is. SGI is on the ropes and arm chair quarter backs such as myself wonder how much longer they will be withering on the vine before they are bought out or file for Chapter 11 protection. MIPS for high end computing is quickly becoming passe and has been that way for years. The only reason SGI can still use the chip is because of their NUMA architecture and they leverage massive amounts of cpus to work in tandem with one another.

    HPQ as already mentioned is in the love nest with Chipzilla. Some consider the Itanium to be the greatest quo ever pulled off in corporate history. Basically Intel has footed a 10 billion dollar bill for HPQ to redesign a brand new architecture that no one really knows or is comfortable with from a software writing point of view. Adoption at this point in time has been abysmal at best. It certainly doesn't help the Intel cause when a bug is discovered with this supposed "enterprise" level chip and the only solution to it is to scale back significantly on its clock speed so that it doesn't rear is ugly head."

  168. Itanium gets all the respect it is due. by ameline · · Score: 1

    Silly question -- I believe that Itanium is getting all the respect it is due. It's just not due as much as you seem to think.

    --
    Ian Ameline
  169. Benchmarks do not mean real code will work by Anonymous Coward · · Score: 0

    I have to laugh at this statement.

    "The supercomputer people are serious about benchmarking (no easily tricked microbenchmarks or reliance on closed-source commercial apps)"

    What pray tell do you base that assertion on? I work in the so called super computing field and I can tell you that statement would be false, if it had any meaning whatsoever. Benchmarking is good for one thing, advertising for funding through press releases. When it comes down to it what you want is to actually get work done. The itanium makes a big noise but comparitively little actually gets done on it. First because it never lives up to its performance hype running real code, and two because writing code for it (or porting code) is far to costly and time consuming. For all that extra effort all I need to do is go buy more x86 and still save a bundle. Unless you want to argue that the itanium helps to employ more programmers and thus stimulate the IT industry I just do not see the attraction.

    Check out some of the newest Terra Grid members. I will give you a hint, they are not running itanium. You know the terra grid, one of the biggest Itanium booster projects?

    When it comes to actual science it is far better to have an app that is actually running, analyzing or producing data than some theoretical ability to do what you are doing today 15% faster. Oh and of course you will only get that performance if you spend 200% or more on software development than you already do.

    Also not all science is done with floating point. Floating point is all nice and good for generating things, but there is a massive amount of computing work that is all integer. FLOPS is not everything and x86 and x86_64 is perfectly good for that work, if not the best solution, certainly price performance and installed software base.

    Oh and that $2000 number? I can buy a dual processor Xeon or Opteron node at the close to highest Core frequency and fasted FSB in addition to disk, motherboard, ram and 1U case for less than $2000. Why would I pay $2000 for a single CPU machine? That is easily twice as much for less performance when you factor in that I get to have twice the processors or more.

    3.92 * 2 vs 4.86

    Is there even a contest? That and your numbers use obsolete processors, my newest xeons are 3.2Ghz with 800Mhz FSB, both features very valuable for my application. Compare that $2000 Itanium against a dual socket dual core x86. never stacks up.

    Itaniums are not popular because the numbers just never add up when you look at practical deployments. That is even before you factor in the massive redesign of every application you run to even get close to that theoretical capacity of the itanium.

    Anyway I have no idea why this was even posted, the itanium ship has come and gone. Dual and multi core X86_64 is the future for the next few years in the computing I am involved in. Beyond that, unfortunately my crystal ball is out of batteries so I will have to get back to you.

  170. Maybe the "C" students agree with you ... by AHumbleOpinion · · Score: 1

    Well, after you take the "Compilers" course maybe your love for IA-64 will have, uh, dimished a bit.

    Maybe the "C" student think so, those just taking the class because they are required to do so. The "A" students and those with an interest in compilers often think the opposite. Here is a challenge, here is an open area for research, parallelization is the future and here is a CPU that fits in with that concept.

    1. Re:Maybe the "C" students agree with you ... by Anonymous Coward · · Score: 0

      Yes, and when I'm in my consumer/product development hat I run screaming from any architecture that is "interesting" for reasearch.

    2. Re:Maybe the "C" students agree with you ... by AHumbleOpinion · · Score: 1

      Yes, and when I'm in my consumer/product development hat I run screaming from any architecture that is "interesting" for reasearch.

      Agreed, but the GP said "Well, after you take the Compilers course ..." not "Well, after you get that promotion and lead a product development team ...". We have different casts of characters here.

  171. Why give links anyway? by Anonymous Coward · · Score: 0

    Maybe it's not a new idea but since virtually all articles have the ICOS post, does it make any sense to give links to the original site?

    IMHO we could just as easily CTRL+C CTRL+V whole articles here. Slashdotting would be an yesterday's nightmare.

    (Yes, I know, in the Free World we could highlight the text with the mouse and press the middle button just as easily)

  172. That wacky IA-64 instruction set by pestilence669 · · Score: 2

    The Itanium, had it been an x86, would have been the next logical step from the Pentium. Microsoft's weak support and developer reluctance to switch instruction sets, have killed all hopes of application support. Only a select few are adventurous enough to support Itanium running on esoteric UNIX distributions.

    I've been *HOPING* that Apple would use Itanium on their high-end Power Macintosh. This would have given a second wind to the chip's lack luster success. Apple really is the only company that can give Itanium application support. If they decided to support IA64 *AND* x86, they could offer a high performance option along with their budget Macs.

    I'm saddened by the end of the G5 line, but I'd shut up entirely if it were replaced by the Itanium. That chip is just fast... and elegantly redesigned. As I see it, it's the best chip out there.

    Apple is great at supporting odd architectures. Their O/S already supports multi-platform binaries... c'mon... somebody petition Apple to add an Itanium build option in X-Code... PPC, IA64, and x86 all at once. I'd be so happy.

  173. single ia64 system $2k, single x86_64 system $600 by Anonymous Coward · · Score: 0

    even if the ia64 system is faster then the x86_64 system it's not nearly enough faster to account for it's higher price.

    especially since most of the target users that the poster talked about are going to be useing a lot of systems in a cluster anyway the single unit performance is far less important then the price/performance ratio.

  174. Supercomputer Performance by Rhys · · Score: 1

    Chips aren't really the limiting factor in supercomputer performance overall. You could custom design a chip to get crazy performance for the linpack benchmark that the top500 list is based on, but that doesn't mean it'd be worth squat outside of that.

    The interconnect is probably at least as important to getting good performance (with today's software at least) as the processor is. Disk subsystems are probably about half that important. (and at least here got neglected in the initial setup)

    How many itanium2s are in the top list? Are they making waves with their performance/price ratio? What about their heat when you're talking trying to build ultra-dense supercomputers? (Hint: spreading out is very bad for your fast interconnect) What does all that heat equate to in terms of cooling and then total power required?

    --
    Slashdot Patriotism: We Support our Dupes!
  175. Which Intel Processor for Apple? by parvenu74 · · Score: 1

    This is a very good point. While the WWDC demo was done on a Macintel with a 3.6Ghz P4 (x86), the developer machines from Apple are also x86 boxes, and the first wave of machines next year are supposed to be Pentium M devices (x86), it's curious that the compiler options in XCode are PPC/Intel and not PPC/x86.

    What caught my eye in the article linked at the top of this post is that the price premium for Itanium is supposed to disappear sometime in 2007, about the same time that Intel processors will be appearing in PowerMacs and XServers in lieu of PPC970's. Maybe it's just a coincidence and the PowerMacs and XServes will have 64bit x86 processors. Or maybe they will run Itanium?

    And then there's the expectation that iPods will be getting XScale processors which will be more than fast enough to decode and play video... which means that if the iPod at that point would play audio and video, show pictures, and include a cell phone, you've basically got a handheld computer in your hand, similar to Compaq's iPaq or Dell's Axim. Perhaps we'll see "OS X Embedded" and the requisite SDK's before long???

    Maybe not, but in lieu of real announcements from Apple I will GUARANTEE that we'll see millions of "maybe if" scenarios all over the web...

  176. I wonder how... by master_p · · Score: 1

    the mighty Alpha would fair against current CPUs, provided that it used modern technology (i.e. 90 nm silicon fabrication, 3 MB SDRAM for cache, a 333 MHz and beyond bus...)

    1. Re:I wonder how... by Rod+Beauvex · · Score: 1

      With SDRAM for cache, I imagine not very well. With SRAM, yes.

  177. Re:EU HAS REJECTED PATENT LAW by Anonymous Coward · · Score: 0

    Where have YOU been? This patent law has been big news, and covered here before. The entire EU was out to enforce software patents, and basically hurt open source software from being developed freely in Europe. I guess blogs/opinions and random screenshots are now 'News for Nerds. Stuff that matters' as the /. editors sure accept them as news. Slashdot used to be a place for good news a long time ago.

  178. Er... that was a troll, right? by MrPower · · Score: 2, Informative

    If not I think you better go watch The Life of Brian and come back to remove the egg off your face.



    My particular love for this joke is irony of looking into a room of Monty Python fans and they are all sitting there chuckling and repeating that very same line.



    Yes, yes we are all individuals!

    Classic!


  179. Re:The overclocking by Anonymous Coward · · Score: 0

    What sound does an Itanium make when dropped?

    DUD!

  180. Offtopic, but... by Vorondil28 · · Score: 1

    ...we do the same thing with the Catalyst 4000 in our Cisco lab.
    :p

    --
    This sig rocks the casbah.
  181. Micro Channel failed due to licensing issues. by MtViewGuy · · Score: 2, Informative

    I think the biggest thing that doomed the Micro Channel Architecture (MCA) was the fact that IBM did not bother to license the technology at very low cost.

    If IBM had done a proper job of licensing MCA at a low cost then not only would MCA have replaced the old ISA bus, but alternative bus connection architectures like EISA, VL-Bus, PCI, AGP and PCI Express would have never happened! This is because we know now that MCA could be easily expanded all the way to 64-bit bus connections and support very fast bus speeds. Indeed, if you look at PCI and PCI Express connectors they strongly resemble the old MCA connectors in physical design.

    1. Re:Micro Channel failed due to licensing issues. by entrigant · · Score: 1

      Indeed, if you look at PCI and PCI Express connectors they strongly resemble the old MCA connectors in physical design.

      Therefore they are equal. I can make a ps/2 port and make it look like a firewire port. I can also put Type R stickers on Hondas.

    2. Re:Micro Channel failed due to licensing issues. by Dun+Malg · · Score: 1
      Indeed, if you look at PCI and PCI Express connectors they strongly resemble the old MCA connectors in physical design.

      Yah, OK, but my gigbit ethernet connector (8P8C USOC modular jack derivative) is the same as used for the old 4800bps serial lines feeding VT52 terminals! Furthermore, MCA was a double/staggered contact design (like the AGP slot) with up to 55 pins (x2) whereas PCI and PCI express are single row, up to 82 pins. When you check out the pinouts for PCI Express compared to MCA, you'd have to have a pretty far-out imagination tosay one was derived from the other in any way.

      --
      If a job's not worth doing, it's not worth doing right.
  182. I just love circular logic by Anonymous Coward · · Score: 0

    "The reason the P4 clocks so high is that it needs too, the reason it needs to is it was designed that way, and the reason it was designed that way was so it could clock high."

    Oh sweet vertigo!

  183. My dislike is somewhat personal. by AtariDatacenter · · Score: 1

    HP came into our large site and told us all that RISC is dead. It has gone as far as it can go, but no more. Their own PA-RISC will be phased out, but its okay, because nobody would want it in a few years. SPARC is completely worthless because it is an old fashioned RISC processor. Embrace the new Itanic CPU like our (then, before she was fired) CEO has! (Followed by the parade of 100 slides.)

    We thought it was silly that HP was throwing away a perfectly good platform and throwing all their customers over to the Itanic commodity CPU. Which, of course, wasn't a straightforward transition because there was no binary compatibility. But there were a lot of vendor promises. (KEYWORD ALERT! "vendor promises" is a tip-off that something is wrong.) And frankly, we really didn't believe them. It sounded more like marketing / sales / VPs were driving the change and the technical crew were taking a back seat, but being called to duty to try to come up with justifications that their customers could buy into.

    That was about five years ago. Fast forward to today. The skeptical audience was right, and the sales droids and their vendor promises were wrong. And the sales numbers go to show that you still can't sell a technical audience with just marketing propaganda.

    I think my summary (epitath?) for Itanium would be, "A processor platform designed for computer company VPs but (un)sold to a technical world."

  184. MOD PARENT UP!!! by Anonymous Coward · · Score: 0

    OH FOR MOD POINTS

    Thats interesting take on the market.

  185. Few answers, for other way... by JollyFinn · · Score: 1

    Single processor itaniums for under 3000$
    http://www.siliconmechanics.com/i2190/itanium-serv er.php?cat=352

    Montecito, coming in 6 months. Running 2 cores >2Ghz frequency, AND adds multithreading to micture at sametime, takes the itaniums worst performance hurdle in those integer apps that itanium cares about by making a dedicated 1MB L2 instruction cache for each cores.

    Now I'm doing some code generation stuff. Itanium is great for code generation target it has lots of facilities to get great performance out of it. However, there exists a LOT of ugly spagetti code that is given to compiler and say compile this and give us performance. The ugly spagetti is slower that properly designed code on *ALL* platforms however it hurts itanium most by not being able to guess and do out of order execution, and lower clockspeed. And based on what I've seen on university students coding I can say that the problem is growing all the time...

    Now I've found that Itanium is great target for the stuff that I make a code generator for.

    --
    Emacs is good operating system, but it has one flaw: Its text editor could be better.
  186. Re: Complaint about CPU Price by dakirw · · Score: 1

    few people like paying $1000+ for a cpu alone, for example.

    No one WANTS to spend that much on a CPU, except for those who want bragging rights. I think the point that the parent poster makes is valid. Very few people would complain about getting the top of the line AMD64 FX-57 chips - there would be more "oohs" and "aahs" amongst the /. crowd. In fact, those chips go for over $1100 each at Amazon or New Egg

    FYI, the Athlon 64 X2 4800+ is also going for over $100 as well at New Egg

    For anyone with the need or desire to have a fast top-end CPU (or plenty of cash to burn), $1000 isn't a big deal.

  187. my answer by Trogre · · Score: 1

    Why Doesn't the Itanium Get the Respect It's Due?

    It does

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  188. Intel Marketing! by burnttoy · · Score: 1

    When Itanium was up and coming it was expensive. This in itself is _not_ a problem for Intel as up till then they'd been making a bucket of cash on every x86 CPU they sold. I imagine they thought they could do the same with Itanium.

    However, AMD began to challenge in their cash cow (x86) and the clock rate race started. Itanium would never be able to compete on clock speed but the battle lines were drawn. Ever since Intel has pumped oodles of cash into getting the P4 as fast as possible. Unfortuantely the P4 really isn't that great as a CPU, but it keeps up (with a bit of kicking) and I guess that will do.

    Also AMD realised there was no immediate reason to push the 64bit desktop (no software!) and so just didn't bother to compete on that ground at all, this probably saved them a fortune and gave them a few years break to re-equip x86 with 64bit addressing. Which TBH isn't that hard as there are so many operation modes on x86 anyway! 1 more isn't gonna kill it! They did do it very elegantly though. AMD have built the worlds first truely defacto 64bit CPU... well... for the next 10 years anyway.

    Intel already have the Pentium M but don't seem to be sure on how to sell it. It has very good IPC stats but a low clock rate. Oh well. Everyone's gone to some sort of PR value... even Intel... kinda... dual and quad core are going to help confuse the PR ratings considerably.

    --
    Time flies like an arrow. Fruit flies like a banana.
  189. Not moving to Itanium Tandem by Anonymous Coward · · Score: 0

    We chose *never* to move to an Itanium-powered Tandem. We're now an AIX shop instead. IBM's HACMP is just as rock-solid reliable as Tandem/Himalaya/NonStop/Whatever...

  190. Top 3 reasons to use Opteron over Itanic by Anonymous Coward · · Score: 1, Interesting

    1. Power consumption,
    2. Power consumption, and of course,
    3. Power consumption.

    Replying anonymously because I already modded in this story. Glad you brought up points 1 and 3, because I work for a company that builds custom Linux clusters for Los Alamos National Laboratories and other government agenCIes who shAll remain nameless. They use Opterons exclusively, for reasons 1 and 3. When you figure out how much it takes to power and cool 100+ node clusters and how many more compute nodes you could buy for that money, the reasons are obvious. We had our Intel rep come to us a few months back, asking what they could do to get us back to selling more Intel chips like we used to, and we said, "Cut power consumption." Number one concern, not FLOPS or anything else. Cut power consumption. Cheaper would be nice, too.

  191. No. by Ayanami+Rei · · Score: 1

    The P2 and P3 (and even the Pentium M) are largely unchanged from the original PPro.

    P2 = PPro + MMX
    P3 = P2 + SSE

    There are other differences (cache structure and speed, bus signaling, addt. transistors for branch prediction, die shrinks) but it's all the same block diagrams and stuff.

    P4 was different... the whole netburst thing. Wow did that suck.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  192. Oh that's real apples to apples comparison. by codeguy007 · · Score: 1


    rank processor ghz (gflops / #procs) speed
    #5 ppc970 2.2 (27910 / 4800) 5.81
    #7 itanium2 1.4 (19940 / 4096) 4.86
    #10 opteron 2.0 (15250 / 5000) 3.05
    #20 xeon 3.06 (9819 / 2500) 3.92

    Given this, consider what a 2 or 3 Ghz Itanium could do.


    Your comparison doesn't show the whole picture. You are listing clusters with 3 different interconnects. If you want a true comparison you need to compare clusters with all the same interconnects configured the same way. Also you are listing different architecture styles. The Opteron solution is a Cray with their own interconnect and specialized motherboard hardware.

    Maybe the XT3 (or whatever it is called) sucks in comparison to myrinet or quadrics. (I wouldn't know)

    Also with Xeon and newer Opteron processors proper cooling is an issue. If you aren't cooling the cpu properly it will slow itself down limiting performance.

  193. Re: Complaint about CPU Price by bani · · Score: 1

    that $1000 is the _bottom_ of the itanium line. $1000 barely gets your foot in the door with itanium. $1000 is _top_ of the amd64 line.

    the difference is like night and day.

  194. because it's slow. by yergi · · Score: 1

    Just speaking from experience. I ran 4 dual itanium 2's with 16 gigs of ram each. It took my group months to optimize the code, and in the end they were slower than a 2.5G pentium IV, and the only advantage was the extra memory addressing ability. We trashed the itaniums in the end, and purchased 2 quad opterons with twice the memory for half the price. THE OPTERONS RUN ORDERS OF MAGNITUDE FATSER. I have benchmarks that prove it. My group was doing all floating point operations. This is all done in 'c' code compiled directly on the platform that it's used on. This was using the same version compilers and redhat linux. The itanium looks good on paper. That's about it. The only people that I know personally that speak highly of the itaniums are the people that have never wrestled with them.

  195. You answered yourself by arodland · · Score: 1

    I could get a single-processor Itanium system for "around $2000". Or I could get a system with dualie 2GHz G5s for $2000 (less, if I'm a student).

    According to your stats from the "top 500", a single G5 2.2GHz has a bit more power than a single Itanium 1.4GHz. So the 2.0 G5 x2 should be almost twice the processor, for the same price. Yeah, the Powermac is a desktop machine -- but it's a kicking one -- and the article you linked said that a "basic" 1x itanium machine "will go for just over $2000".

    Other advantages: while the future of the PPC is not entirely certain right now, I'd venture to say that Itanium's future is even shakier. Dualie 2.7GHz G5 systems are already available (at a $3,000 pricepoint from Apple). I see the power/price ratio continuing to look better for PPC than Itanium for a while.

    Also, there's considerably more software out there for PPC than Itanium, and probably more developers familiar with the platform.

    If you want more reasons why Itanium deserves almost every slam it's ever gotten, ring me back -- or read some of the other posts here :)

  196. Re:EU HAS REJECTED PATENT LAW by Anonymous Coward · · Score: 0
  197. Please followup on this! Why AMD64 == good IO? by Anonymous Coward · · Score: 0

    This is exactly what I'm investigating at the moment. I'm trying to find out how to get the best performance for an I/O bound database. We have tables with 10s of millions of rows that must be joined with other 10s of millions of row tables. The datbases vary between 50GB and 150GB.

  198. It's an integer task... by Ayanami+Rei · · Score: 1

    ...it's just that your system lacks the bandwidth.
    I'm guessing you have a 754-pin A64... you've got a crippled bus from your cache to memory.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  199. DOA by dtfinch · · Score: 1

    It was way too expensive when it shipped, and is still too expensive. Even if I wanted to buy one, how do I know it'll work well and reliably for our needs? Most people have never seen an Itanium. Commodity processors get a lot more public use, run cooler, and are better supported by most software. After reading some other comments, I'd sleep easier with Celerons powering our servers. Besides, most performance problems can't be fixed by throwing a faster cpu at them.

  200. Power by waveman · · Score: 1

    I remember the first Itanium demo I went to. It was in conjunction with a software vendor deminstrating their SQL server software for the chip.

    You could not hear the presenter because of the noise the CPU fan was making. He had to move closer to the audience so we could hear him!

    And that is a big part of the problem. Coming out with a power hungry CPU just when power became a huge issue was not a clever thing to do. AMD decided not to follow itanium for precisely that reason and said so at the time. AMD64 was their choice and the rest was history.

    Tim Josling

  201. Can't follow the herd! by DavidRawling · · Score: 2, Interesting

    Furthermore, having just tried to order a pair of Itanium 2 servers for a SQL cluster:

    • We can't get the 1.6GHz 6MB cache chips (we wanted 2 quad-proc servers)
    • The 1.6GHz 9MB cache chip ups the price of the entire server by 25% for 3% extra performance
    • The only other Itanium available to us was the 1.5GHz 4MB cache, for which we waited an extra 2 weeks.

    These supply issues quickly gathered the chip a new moniker - Unobtanium.

  202. Re: Complaint about CPU Price by dakirw · · Score: 1

    that $1000 is the _bottom_ of the itanium line. $1000 barely gets your foot in the door with itanium. $1000 is _top_ of the amd64 line.

    True, but the Itanium is pretty much stuck as a server/workstation chip these days. It's still pretty pricey, but compared to the price of a decently laid out workstation or server, it's expensive, but not TOO bad.

    I'm not too surprised that the chips cost that much, considering how much the projected market has shrunk.

    Personally, I don't disagree with you - I wouldn't want to spend more than $500 for ANY chip. It's just that for certain specialized fields, that $1000 chip might be worth it.

  203. All about the arch by Barny · · Score: 1

    Main reason the opteron is getting so much press? its x86 compatable, end of story.

    People would love faster proccessors but don't want to have to pay a pack of patroniseing programmers to convert all their code to it (or in most cases beg and plead to their closed source developer to please make it for the new design)

    --
    ...
    /me sighs
  204. and in 1996 it was Alpha by AHumbleOpinion · · Score: 1

    If it was anything like my EE class (1998 era) they were also handing out Itanium architecture manuals, Itanium platform reference guides, a book about Processor Architecture written by a guy from Intel, taught by a professor who drank out of an "intel" mug, and the cute female grad student had an "intel inside" t-shirt on with an arrow pointing down. Yeah, I had that class.

    If you substitute 1996 for 1998, Alpha for Itanium, DEC for Intel, and change the T-Shirt on the cute female grad student it sounds like my graduate architecture class. Are you suggesting there is something odd here? Well, other than the girls.

  205. Re:Actually, it's still exp READ FINE PRINT by iggymanz · · Score: 1

    look at the "available" date, those systems don't ship yet! hahaha, vaporhardware! I have two 1.5GHz Itanium2 boxes at work, they run RedHat Enterprise Linux & Oracle about 15% slower than my home 1.5GHz Xeon box. Why someone would pay 2.5 times the money for same performance in most business/serving apps is beyond me.

  206. the cell processor by john_uy · · Score: 1

    isn't the cell processor similar to the itanium2 (please make corrections)? just find it weird that everybody seems to think that cell next generation of processors for everyone but suffers things that are the same itanium 2 which is criticized by the same people. anyway, just a thought.

    --
    Live your life each day as if it was your last.
  207. patented ISA = no competition by Anonymous Coward · · Score: 0

    ...and businesses don't like to get locked into a single vendor. Intel got too greedy and anti-competitive, and that's a big reason why businesses aren't embracing the Itanium.

    I've read a fair bit about the architecture, and I've done a decent amount of programming & optimization for a VLIW CPU. So, let me correct something: THE ITANIUM IS NOT VLIW. It is VLIW-like, in that dependencies between instructions are explicitly encoded. However, the scheduling of the instructions is not static, so it doesn't place as much a burden on the compiler as a traditional VLIW.

    Other benefits include that code doesn't have to be recompiled from one generation to the next, yet it can take advantage of different amounts of parallelism, across the family. Also, it allows you to do branch prediction & speculative execution, or interleave instructions from different threads (i.e. hyperthreading).

    On the down side, dynamic scheduling forces the chip to contain scheduling logic. The ever-increasing size of this logic, for wider & more deeply-pipelined superscalar CPUs is one of the main points in favor of VLIW.

    So, Intel's EPIC (Explicitly Parallel Instruction Computer... or something like that) is really closer to CISC/RISC than VLIW.

  208. it's by Anonymous Coward · · Score: 0

    It's or its? I think it's its. Duh.

  209. The Unreasonable Expectations Itanium Lives with by Glasswire · · Score: 1

    1) "It's an Intel processor, so it has to have great x86 compatibility and performance. If it doesn't run that well, it's a failure."
    Why doesn't anybody rap an IBM Power processor (or a HP PA or Sun SPARC or...) for having NO (not just slow) x86 compatibility? Itanium is the only non-x86 processor (one with a different native instruction set) that does ANY native emulation of x86 -so does this win praise from people who like Power but wish it supported x86 as well as it's native instruction set? STRANGELY, NO.
    2) "It uses an instruction set (EPIC) that only Intel makes so no competing processors can use it. This is very bad from a company with as big a market share as Intel."
    Well, Itanium is not (not yet anyway) a big market share leader in the big enterprise space that it's targeted at...like IBM Power. Of course IBM would sue your ass off if you tried to independently build and market a Power-compatible processor. The truth is that in the high end of the enterprise computing market, proprietary is the norm and Intel is no worse or better than any of the other players in this space. If you don't think Intel SHOULD NOT be trying to make processors that compete at the high end, fine, but that's what IS where Intel aims this processor at. (Anybody think that AMD WOULDN'T do their OWN exclusive high end processor and unique instruction set if they thought they could sell enough of it to make it work?).
    3) "Itanium is hard to work with, being so different with the VLIW instructions, so dependent on compilers and so darned parallel the compilers excrete binaries in structures called 'bundles'. Why didn't Intel just build a better x86 instruction set processor?"
    It always facinates me that you can sometimes hear this comment voiced in the same conversation that somebody else claims there are no major innovations happening in computer architecture. For better for worse, Intel stuck it's neck out and did a very elegant highly parallel processor design that is not CISC or RISC. And does Intel get credit for spending a ton of money to bring to market something that ISN'T just a tarted up decendent of the 4004 cpu from the 70s? You answer.
    (There's lot's more to say here, but I'm out of time...)

  210. They should have called it the "Dangerfield". by falconwolf · · Score: 1

    It gets no respect hey?

    "Back to school!

    Falcon
  211. itanic? by Anonymous Coward · · Score: 0

    A better question is why doesn't the Alpha processor get the respect it deserves. Yes, HP is trying to kill it, but it still trounces the Itanium 2 even today. Alpha is the fastest, flat out. Ever wonder why you can't find Alpha vs. Itanium 2 benchmarks on hp.com? Because Alpha is faster and hp is trying to bury it, so it doesn't publish the numbers. I would know, I used to work in the High Performance Technical Computing division at HP.

    1. Re:itanic? by msbsod · · Score: 1

      Hey, if HP would pursue the Alpha path, then they would have to sell their own software instead of Microsoft shit. Scary, you know!

  212. Server-only platform by msbsod · · Score: 1

    HP is currently "giving" away an Itanium server for attendees of a $2000 HP and Intel Developer Workshop - of course only in the USA (always the same pattern, do not call it fascism). http://www.theinquirer.net/?article=24502 The regular price for such a server is more than $3000. What you get is a low-end server without the extras for a workstation. Oh, and HP recommends Microsoft Windows XP. Do you recommend Microsoft Windows? We have seen such deals before. A few months later, let's say one VMS revision later, and the free server is no longer supported. The quotes at pricewatch show why a regular low-end Itanium system costs more than $3000. Did I mention that not all of these Itanium systems run all operating systems? Do not expect that all Itanium systems are compatible. And which operating system would be most affected? VMS, of course. But the biggest problem is the lack of CHEAP low-end systems. Who is seriously going to spend money on a $3000, or maybe $2000 Itanium PC? Nobody. A PC costs $500, no more. Why would anybody want to invest into two different platforms for workstations and servers? Performance? Just tripple the number of low-cost x86 servers and you still end up with lower costs than for any Itanium system. The bottom line is that without cheap workstations and notebooks there will be no growing Itanium market. Intel made it pretty clear that this will not happen. Look for the AMD64 series instead!

  213. Cost. by Nelson · · Score: 1

    I think the only thing that really mattered was/is cost. Until you're making IA-64 desktop workstations for $700, it's just not that interesting to the masses. Compilers aren't as strong as they could be because compiler writers aren't working on IA-64 compilers because they aren't selling because of cost. 32bit IA-32 support is nice, but when it's all said and done, you want IA64 code. Because it's expensive and nobody buys them, MS doesn't spend the several hundred million dollars to keep Windows running well on it and get the Office Apps ported.


    It's kind of interesting, Intel timed it really well to kill off sparc, alpha, PA-RISC, Mips and potentially even POWER. They essentially did kill off most of them, Sparc is kind of limping along for now and IBM's still in the ring. On the other hand, they also made kind of a big blunder and they hurt themselves by hurting a lot of that competition. Why would I spend $100k on an IA64 solution that hasn't be proven in the field rather than a Sparc or POWER solution? Or even better, spend $30 on Xeons and Linux.


    Really to make it happen, HP is going to have to move a lot and start to hurt IBM with them and the cost will have to drop substantially. As is the x86-64 market is building up, being 64bit alone isn't a selling feature, people don't care about RISC vs. CISC vs EPIC and there is simply no way that small and midsized companies are going to pay for the relatively small performance improvement.

  214. Re:It is true for processors as it is for people.. by Anonymous Coward · · Score: 0

    As an avid necrophiliac, I concur.

  215. call me old fashioned... by Philodoxx · · Score: 1

    I have a hard time taking the Itanium serious for two reasons:

    1. I have heard there are thirty-six megs of cache on one version of the chip

    2. When the original Itanium was released all those years ago, its hardware x86 emulation was so terrible that Intel wrote a software emulator that was faster than the hardware solution.


    Don't get me wrong, the first isn't a bad thing(I just find it a tad rediculous), and the second no longer applies. More seriously I think that its completely incompatible instruction set combined with high cost keep it from more widespread adoption. Even if the supercoputer people are getting all hot and bothered about it, that still leaves a few fractions of a precent below one hundred of the world's population that the chip has to do something for.

    --
    Oh, a lesson in history from Mr. I'm my own grandpa.
  216. marketing compatibility by quarkscat · · Score: 1

    Intel initially did a superb job of marketing the ia64 processor -- they scared the bejeezes out of DEC, HP, and SGI. So much hype from Intel, in fact, that each of these companies which already had 64-bit processors and a market for them, has abandoned their processor in favor of Intel's marketing muscle.

    Intel then pulled the plug on much of their ia64 development "roadmap", apparently having created the desired disarray amongst their 64-bit competitors. To top this off, Intel's own marketing bullshit over processor clock speed meaning more than system thoughput shot themselves in the foot.

    With no backward compatability to their ia32 architecture, little regard for seeding low cost development platforms to gain market share, and their own internal battle over "processor clock speed rules all", it is really no wonder that the ia64 has not gained widespread acceptance.

    Reuse of code from previous generation processors is important -- IBM's PowerPC processor, SGI's MIPS processor, and SUN's UltraSPARC processor all offered backward compatability.

    Intel's ia64 processor doesn't even garner respect from Intel. Why would any other computer OEM offer more respect than that?

  217. Swing and a miss by infonography · · Score: 1

    should have been "mid to upper end small business market" Numbers wise Intel/Microsoft still dominates. If SUN can take a bigger bite out of M$'s SQL Server market then they will be set. Now, Linux/Mysql is starting to show big there. Why not, do it on Ultrasparc?

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    1. Re:Swing and a miss by beezly · · Score: 1

      And why not do Solaris/MySQL? That's Sun's point of view.

      Besides, I doubt Sun care that much about small business. Sun doesn't make much money from shifting boxes, it does it through professional services (like IBM, just check their financials and you'll see).

      Small businesses tend to not spend very much on professional services.

  218. Been there, got the t-shirt, wore it out by ellbee · · Score: 1

    Ten years ago you could buy an Alpha that had the same bragging rights - 64-bit registers & addressing, wider bus, better atomic primitives, etc. *YAWN* It solves a serious problem that confronts maybe .05% of the world, and runs about the same amount of sw compatibly. A technological masterpiece/kludge in the tradition of IPv6.

    --

    You can't fight in here - this is the war room!

  219. Re:Still true to this day. by Anonymous Coward · · Score: 0

    Sad part is x86 is still cheap, and MS still can't handle 1bit of competition. Can't we just have Alpha back plz?

  220. Nitpick by XanC · · Score: 1

    The 286 was the last 16-bit processor; 386 and 486 were both 32-bit. The crippled 386SX had a 16-bit interface, though it was internally 32-bit.

  221. Why? Let me tell you why. by rew · · Score: 1

    Somewhere in the late seventies, a company had a bright idea. Instead of asking the developers to recompile their source code for the new processor, they would give the new processor at least a mode wherein it would simply execute the binary code of the old processor.

    This idea made them big. This idea made them the biggest. And they are still called Intel.

  222. Because it was a failed technical launch by AceJohnny · · Score: 1

    We were part of a pilot program at our school on the Itanium. I think the Itanium tanked because Intel didn't plan the release correctly.

    Remember the Itanium is a brand new architecture. It's NOT x86. It's like jumping from x86 to PPC if you will... That means you have to recompile everything. Of course, I'm not talking about compatibility mode.

    Of course, introducing a new architecture is a *huge* endeavor. Intel wanted to fast-hand it and their marketing department went nuts over it. Problem is, the Itanium *wasn't ready*. You can't introduce a new architecture and expect the market to gulp it in. They were trying to push x86 out with the new chip. That couldn't happen. How long has x86 been around? How many *billions* of cash rest on that chip?

    Anyhow, the first Itanium was only a technical preview, in a way. It was the first public diffusion of the chip, to try to get developpers used to it, slowly.

    However, there came another problem: Itanium is an EPIC (Explicitly Parallel Instruction Computing) architecture. Not RISC or CISC. Do *not* listen to their marketing BS about EPIC. Technically, it kicks ass. In practice, you need a good compiler to take advantage of that instruction set.

    That was the core of their problem. The compiler. Compiler gurus will tell you it's devilishly difficult to optimize parallel processing correctly. The cool thing about PPC chips is that it manages some parallelization on its pipelines internally. The compiler just doesn't have to care. It's much more difficult on EPIC, because of the E: the compiler has to manage the parallelization itself.

    The chip arrived, but the compiler wasn't there. Intel relied on universities to develop powerful compilers. Universities are great for research. This is fine, if you have the time. Intel did not have the time.

    At one point, I think, they tried to push the GCC guys to work a bit on optimisation for the Itanium. The answer was no. They had spent too much effort on optimisations for the x86 platform. x86 has been out for so long, and they're *still* optimizing. If someone wanted to do some Itanium optimisations in GCC, go ahead, but not them.

    One important problem with the compilers, as another poster has pointed out his experience, was memory access. The Itanium is supposed to have a *killer* memory subsystem. It just wasn't used correctly.

    So in the end, it boils down to this: the Itanium arrived before its time. Its time will be when good optimizing compilers will exist. I believe the NCSA is working on one that could fit: OpenMP, though its applications are primarly supercomputing.

    Intel tried to push the processor too hard too quickly. It tanked in trying to replace the x86 market. It is now releguated to niche applications, like supercomputing. Maybe its descendants will come back to the front of the scene when the compilers will be good enough: when GCC will have optimisations for it.

    Just my .03$, from hanging around the Itanium team at school.

    --
    Misleading titles? Inflammatory blurbs? Keep in mind that Slashdot is a tabloid.
  223. Why? by Bert64 · · Score: 1

    Itanium gets no respect mostly because of the attitude of HP...
    Forcing their customers to drop Alpha or PA-RISC for itanium, which can be a costly transition... And expecting Alpha users to migrate to HP-UX which lacks many of the features Tru64 had..
    Had HP put money in to developing the Alpha instead of itanium, then the alpha would be at 2-3 ghz nowadays, and would still be beating the power chips from ibm in raw performance..

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  224. HP is still heavy into Itanium by Stu+Charlton · · Score: 1

    HP has no where to go *but* Itanium for its small-SMP, Superdome and NonStop lines. That article noted they're investing $3 billion in using that chip over the next few years.

    And Microsoft does support Windows Server 2003 on Itanium, that article was referring to client XP (which makes sense -- there is little/no need for an Itanium workstation at this point.)

    I can get HP-UX, Linux, or Windows Server 2003 on HP's Itanium2 machines (I've had several running HP-UX and Windows in a corporate lab).

    --
    -Stu
  225. Itanium2 is decent by Stu+Charlton · · Score: 1

    I've built designed databases and/or application server farms for coporations in telecom and finance.

    If you need 64-bit addressing (i.e. large shared memory sizes, or individual process heap sizes over 2GB), you basically have 4 choices: Opteron, SPARC, POWER5, and Itanium2.

    If you take a quick look at the SPECcpu2000, SPARC is a condenter if you need throughput, but not if you need raw CPU power. POWER5, Opteron and Itanium2 are about on-par, with minor (~10%) differentials between each other, in both power and throughput.

    So really, it comes down to what hardware vendor do you want to do business with, and what software support is on each chip/OS, and that determines the chip you'll buy. Most corps deal with the big 3 (IBM, HP, Sun). HP chose Itanium2, Sun chose SPARC or Opteron, and IBM chose POWER5. Some systems are only tier-2 support on AIX POWER5, for example, but are tier-1 on Itanium2 HP-UX. Some are the other way around. Go figure...

    --
    -Stu
  226. Re:Actually, it's still exp READ FINE PRINT by Cheeko · · Score: 1

    Are you saying that those applications specifically are running slower, or that YOUR application that uses Oracle and runs on REL is 15% slower. If it is your application, did you build it with the Intel ICC compiler, or did you use GCC? If GCC, then there's your performance hit right there, and then some.

  227. Re:Interoperability by sillybilly · · Score: 1

    Actually, I did some research, and I realize I wasn't completely on the mark with my comments. I think the big two chip companies are moving somewhat in the right direction, with dual-core chips, though there is certainly a need for low power Transmeta chips for reading Slashdot, or at least the big players should drop the clockspeed to 1 Mhz when the CPU is idle, and only crank it to 5GHz when needed.

    As far as off the mark goes, did you know that the human brain consumes humongous amounts of power? More exactly 20 Watts out of a 100 Watts resting pace, so even though it makes up only 2% of the body's weight, it consumes 20% of total energy/oxygen needs? So even this ever-perfected life runs the cpu "hot" relative to the rest of the system.

    Also, by 2020-2050 we can expect real artificial intelligence if things keep up they way they do. We better start thinking about the consequences of what happens when machines are smarter, more intelligent, can hold wittier conversations, and make better supreme court judges than human beings. Is that something we can deal with, or trust?

  228. Itanium 2's for $699 by anarchynow · · Score: 1

    For anybody in the need, I source my Itanium 2 1.3's from a guy (packageshop@hotmail.com) for only $699! Where else can you get 3mb on chip cache for that kind of money at that price...! I've only noticed a marginal speed bump with the 1.4 and 1.5's which are priced astronomically much more, so for price/performance tricking out a box with the 1.3's are the way to go, and their price is now very affordable. Now you can get them for a steal and these little babies are screamers. I run a bunch of tricked out servers maxed out with four 1.3's each and the main cool deal with the Itanium 2's, was you can blow right on past the 4gb barrier and it executes code in big chunks. Working with any computer with less than 4gb and 4 processors and you don't know what you are missing. These badboys have 28 dimm slots or 64 dimm slots and go up to 56gb and 64gb respectablly, node scalable up to 224 gb. Show me that motherboard of yours again with 2 dimm slots that goes up to 2gb??? Um, yeah, where's the trash can. You want one of these... its all about memory. Itanium 2's running stuff in solid state memory with 3 caches between it and the memory totally obliterates everything else out there short of maybe Power5's, which are actually 4 processors on a chip and will cost you a small south american country. You do have to flash upgrade your EFI bios with the lastest to enable EPIC, and the machines work best with lots of RAM because they execute code in chunks. The issue of running 32bit code has never mattered to me, as the entire OS was recompiled for 64bit anyway, and if you're using linux everything is in the distro you need as a 64bit native app ready to go. I run Centos Linux which is free, but have also used Redhat ia64, Suse Enterprise ia64, and the latest 64 bit Windows on them. The 32bit enabler was installed by default but I never used it, except under Windows. Most people gave the Itaniums a bad rap, because the EFI didn't enable EPIC by default, and all that capability just was left bridaled and brimming there under the surface. So be sure to flash your EFI bios to enable EPIC. Also, I always get a better video card by default for my server, most servers ship with the bare minimum for video. I won't even touch the Opterons or Xeons, they are kludges by comparison. Once you figure out the little tricks on how to make the ia64 chips sing you can do some serious number crunching. Wikipedia still lists the Itanium 2 as Intels top dog processor.

  229. Because we did *NOT* want processor monopoly by snolan · · Score: 1
    Itanium announcements by the UNIX vendors where I worked scared me because we deliberately used architecture diversity to isolate our production facilities from architecture problems.

    Having half our mail servers run on Sun (SPARC) and half on HP-UX (PA-RISC) meant that a problem with any one of the components could only take out half the complex, and we hoped we'd fix that problem before a different problem took out the other half.

    It worked, but with most of our vendors jumping on the Itanium vaporware wagon, and the remaining non-jumper screwing us on service we got very nervous about being able to continue.

    Turns out we were lucky. The scaleability and reliability of Linux on several processor types has made our tradition of two OS vendors for any major subsystem moot, and we can still split architectures between i86, Opteron, PowerPC, and even re-use the PA-RISC and SPARC gear that we have not lease returned or sold off.

  230. Re:Actually, it's still exp READ FINE PRINT by iggymanz · · Score: 1

    not my apps, standard Oracle diskless TPS benchmark is slower. I should be fair and say that the floating point and linear algebra benchmarks are smoking on Itanium2, but that's just not what usual business apps do, it's all bcd/integer, memory shuffle, and such which show no benefit

  231. Transmeta code morphing by Per+Cederberg · · Score: 1

    Hmm... Didn't Transmeta go with VLIW too? Maybe Intel should just buy them and implement their on-the-fly instruction translation software (code morphing) for the Itanium?

    But it's probably too late to save it now, anyway...

  232. Cray Opteron systems by mparaz · · Score: 1

    Cray uses Opterons. Such as in this product.

  233. where's the cache? by vlad_petric · · Score: 1

    If I understand correctly, you're referring to the off-chip L3 cache (which is considerably slower than the on-chip Itanium one)

    --

    The Raven

  234. But marketing also helped to sink it by UnapprovedThought · · Score: 1

    Everything you said, plus:

    • They went out of their way to convince a whole crop of companies to drop their own 64-bit products and gear up to support the Itanic
    • Everyone stopped buying the existing big iron and waited for this phenomenal thing... and waited, and waited...
    • Rather than lower expectations, they drummed up EPIC further as the future of computing, in no uncertain terms. "Step aside RISC, EPIC is here."
    • Someone insisted on backward compatibility to x86, which ate up valuable real estate on the chip and made the first version even slower (tell me that wasn't a marketing decision!)
    • Rather than brag as early as possible about the amazing performance, they guarded initial performance figures with tight secrecy, which seemed a bit odd and only made people more curious.
    • Of course, when they finally released it, it was nowhere near the expectations that had been set for it, and in fact was slower than even non-server processors.

    The overall effect was a loss of credibility, and that a number of hardware companies were either weakened or went under. So don't be surprised if the Itanic gets some derision.

  235. please, enough of the bullshit by Anonymous Coward · · Score: 0

    The BIOS replacement they use is not functional. It's very difficult to set up disks for use, and if you lose the disk that the BIOS data is kept on, you're screwed.

    Your EFI configuration lives in flash memory you stupid fuck. You are certainly brainless if you don't know how to set up an EFI partition (if you even need one that is: you don't have to have one) - Linux (Debian, Ubuntu, RedHat, SuSE) and HP-UX will all set these up automatically, don't know about windows or VMS.

    The HP systems are riddled with hardware problems

    I've been using an rx2600 for about 3 years now and it has been in absolutely perfect working order? We got an rx4640 a few months ago and it too has been just fine. Sure, two systems is hardly a representative sample, but would you care to give an example of what you mean by "hardware problem"?

    I think you're just making up total and utter bullshit. You've never actually used one of these systems, have you. (Easy test: what's the logo next to the flashing green led on the baseboard of all HP Itanium systems? This is easy to see (even in the dark) and you don't need to open the system (just look through the grille at the back))

  236. How to win with a non-existent product by zbalai · · Score: 1

    I've created an article from this comment on http://www.zbalai.com/_ideas/index.html I've quoted Jhan, please check, if the quote is OK.

  237. followup by happycorp · · Score: 1
    (This is the person who submitted the original post. I was travelling the day the discussion came out and did not see it until later.)

    In my opinion many of the comments explain why the Itanium is not widely adopted, but they mostly do not explain the admitted community attitude about the Itanium.

    Specifically, yes the processor has a chicken-and-egg problem-- if it were popular, software would be ported and the cost would come down (or at least this is conceivable). So one would think our attitude would be,

    "It's too bad the Itanium doesn't catch on, it sounds like an interesting alternative processor choice".
    Instead of the current,
    "Itanic - why hasn't it died yet".

    The post that (IMHO) maybe does explain the situation was this:

    The winner is not always the best or even close to the best, the winner is often the one that people feel good about.

    So maybe problem is that people want to feel good that their 3.4ghz processor is THE FASTEST thing out there, and the Itanium is there in the background denying this claim.

    Some repeated themes that (though true) do not explain the attitude are:

    • Integer versus Floating point performance.
      Your quoting FP performance. The "integer" (aka general purpose) performance isn't nearly as competitive.
      ...
      For about the millionth time: itanium (itanic) is a poor design for anything other than numbercrunching.

      The problem here is that, when purchasing a computer for personal use, floating-point (games) is in most cases the only issue. You are't upgrading to a 3.4Ghz processor to run Office faster.

      Certainly running xyz.com's website and database are a different story (integer performance needed), but this by itself wouldn't prevent anyone from craving the itanium for personal use, any more that it would distract us from wanting a PS3.

    • Compatibility
      Sure, an Itanium will run all your existing 32-bit stuff...in compatibility mode, which means you get performance akin to a 300MHz Pentium-II on your $2000 CPU. Remind me again why I'm supposed to buy Itanium?
      This is the chicken-egg issue.

    • heat/size I don't know - could this be a checken/egg issue too? In other words, if the chip were more popular, would intel spend more resources trying to address this, or is it intrinsically large and hot?
    The most frustrating part of the discussion to me was the conflicting statements about whether the architecture is potentially a good one. I don't have the background to judge, though I'm more inclined to give it a chance than some.