Slashdot Mirror

← Back to Stories (view on slashdot.org)

Intel Details Eight-Core Poulson Itanium Processor

Posted by Soulskill on from the here's-a-thing-that-exists dept.

MojoKid writes "Intel has unveiled details of their new Itanium 9500 family, codenamed Poulson, and the new CPU appears to be the most significant refresh Intel has ever done to the Itanium architecture. Moving from 65nm to 32nm technology substantially reduces power consumption and increases clock speeds, but Intel has also overhauled virtually every aspect of the CPU. Poulson can issue 11 instructions per cycle compared to the previous generation Itanium's six. It adds execution units and re-balances those units to favor server workloads over HPC and workstation capabilities. Its multi-threading capabilities have been overhauled and it uses faster QPI links between CPU cores. The L3 cache design has also changed. Previous Itanium 9300 processors had a dedicated L3 cache for each core. Poulson, in contrast, has a unified L3 that's attached to all its cores by a common ring bus. All told, the new architecture is claimed to offer more than twice the performance of the previous generation Itanium."

77 of 102 comments (clear)

  1. Why? by PCK · · Score: 3, Interesting

    I was under the impression that Itanium was all but dead. I'm guessing Intel must be contract bound to bring out new versions.

    1. Re:Why? by Anonymous Coward · · Score: 1

      If that was the case, why bother making performance improvements inside the core? Why not just move it to 32nm and double/triple the number of cores / socket?

      Though I agree, this was likely a significant loss on intel's books.

    2. Re:Why? by Guignol · · Score: 4, Funny

      I understand
      In death, an agent of project Itanium has a name
      His name is Robert Poulson

    3. Re:Why? by ewanm89 · · Score: 2

      Yeah, I'm sure there was a big argument with oracle threatening to sue when Intel said they were dropping Itanium architecture several months ago.

    4. Re:Why? by Anonymous Coward · · Score: 1

      I came for this joke. /. does not disappoint.

    5. Re:Why? by hairyfeet · · Score: 1

      This is what I don't get, you look up the numbers and the chip is all but a corpse, my guess is they already had these designs done before itanic lost any chance of gaining real share and now they are hoping to simply carve a niche out with it, something like how POWER and SPARC have their niches.

      But according to the Wikipedia they sell than 200k Itanium chips a year which while that makes it not a money loser for a giant like Intel you have to wonder if its worth keeping the lights on for such a small market share. All I can figure is they can keep this a step or two behind on the die shrinks and use them to fill capacity. After all in TFA they say its 32nm and isn't Intel about to release 20nm X86 chips? or did they get them out the door already?

      Who knows, maybe there is some niche contractor that Intel wants to keep happy, look how they kept cranking the 486 chips out until just a couple of years ago, they get enough sales from the US military and defense contractors for the 486 (because its easy to harden against radiation) that even with such a tiny niche it was worth keeping it running just to keep them happy. last i heard they had a warehouse full of 386 and 486 where they had that last run cranked to the max so they'd have plenty of spares to keep the contractors happy for several more years.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    6. Re:Why? by unixisc · · Score: 2

      The recommended ASP is ~$4000/tray. Anyone know how many itaniums are there in a tray? Multiply the unit price by 200k, and you'll get the cash that Intel would be making on those.

      But honestly, there are some markets Intel should attack w/ this CPU. For starters, supercomputers. The platform from Cray discussed yesterday - that one looks just perfect for a whole bunch of these. There are quite a few supercomputer projects in a number of countries, and Intel should target the Itanium at all of them. That alone would have a bunch of them flying off the shelves.

      One thing I believe - by tossing more cores at the problem, just like w/ the i-Cores and others, Intel has possibly eliminated a major drawback that Itanium, as a VLIW based CPU had - namely a complete break in compatibility b/w generations. This was something that would have threatened to sink the platform, but since Itanium I & II didn't take off, there ain't a whole bunch of legacy software for Itanium III to support. But Itanium is the wrong platform for legacy OSs such as NonStop or OpenVMS - it's probably perfect for supercomputers, but not much more.

    7. Re:Why? by rot26 · · Score: 1

      Yep.

      It's GOOD to be an important supplier to a black project with a black budget. *cough* NSA *cough*

      There will be trainloads sent to Bluffdale, Utah, in boxes labeled as containing Donnie and Marie CD's. I imagine much if not most of the development was done by SAIC contractors with TS clearances. There will no doubt be a few thousand crippled versions marketed though the normal channels.

      --



      To ensure perfect aim, shoot first and call whatever you hit the target
    8. Re:Why? by g00ey · · Score: 1

      Who is to judge whether developing and marketing the Itanium is worthwhile other than Intel themselves? Perhaps the development and marketing of these chips will give them valuable information that is useful for the development of future generation processors.

      The EPIC architecture (which is looked upon as a continuation of the development of the WLIV architecture) is significantly different from other more wide-spread architectures and perhaps the performance issues are there because people have not yet figured out how to fully utilize such an architecture in an efficient manner. So maybe one day when the compiler tools get more mature we might see EPIC CPUs with a competitive price/performance in the market. But that's my two cents.

      Btw, damn to the depths whatever muttonhead thought up 'all butt'!

    9. Re:Why? by unixisc · · Score: 1

      RISC was actually the optimal CPU architecture. CISC had a lot of things, such as variable instruction lengths, different modes of addressing and so on that complicated the hardware. RISC simplified some of that by reducing the number of instructions that were needed since all the programming was done in higher level languages like C, but still kept techniques like branch prediction, speculative execution and register renaming in the CPU itself. As a result, RISC never had problems maintaining compatibility b/w different generations of CPUs. The simplified hardware allowed them to either accelarate clock speeds, or have improved performance/watt.

      VLIW went a step further than RISC and moved everything to the compiler. The idea being that once very little work was left to the hardware, it could be simplified and overclocked to speeds above the fastest superpipelined RISC CPUs, such as the Alpha. It was a good theory, except for 2 things:

      • The compilers for such a platform that would do all the dynamic analysis was near impossible to write
      • Compatibility b/w generations of CPUs was automatically broken every time they would add a few register or even a few pipelines or pipeline stages - the compiler would have to take care of that to makes sure that all the pipes were utilized

      Also, the amount of circuitry in RISC that does that dynamic analysis was already quite small, so the percentage of real estate saved by going to VLIW was not very much. So not much cost savings there, while in the meantime, the compilers didn't get much better. In the meantime, on the RISC side, both Alpha and POWER incorporated a lot of the other MIMD techniques inherent in VLIW, making that difference even more theoretical.

      Ultimately, it was tragic that Itanium brought about the premature deaths of several far better RISC CPUs such as the Alpha, MIPS V and PA-RISC. It would have been good as a new platform from Intel targeted very specifically at scientific applications, such as supercomputers, where the effort could have gone into making exactly the sort of compilers that would have been needed, while in the meantime, PA-RISC could have continued to sustain HP/UX, Alpha could have continued to sustain OVMS and MIPS V could have continued to sustain both NonStop, even if SGI went under. Itanium certainly does not play in the same area as SPARC or even POWER7, and it could have been fine tuned for what it would have been best at, instead of pretending to be a successor to the x86 platform, as Intel originally planned.

    10. Re:Why? by turgid · · Score: 1

      But honestly, there are some markets Intel should attack w/ this CPU. For starters, supercomputers. The platform from Cray discussed yesterday - that one looks just perfect for a whole bunch of these. There are quite a few supercomputer projects in a number of countries, and Intel should target the Itanium at all of them. That alone would have a bunch of them flying off the shelves.

      Er, no. Itanic is just an over-grown, over-engineered DSP. The GPUs that they use as co-processors in supercomputers these days do a much better job (orders of magnitude faster, cooler, cheaper and supported by standard - and open source - software libraries).

      --
      Stick Men
    11. Re:Why? by tigersha · · Score: 1

      The rest of us jerk off to pictures of girls instead of conspiracy theories. Try it one day!

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
    12. Re:Why? by g00ey · · Score: 1

      Perhaps breaking of compatibility between CPU generations is not a weakness of the VLIW/EPIC architecture per se but rather a weakness in how people look at software and software distribution. First of all, why should software be distributed as pre-compiled binaries? A much better way would be to distribute the sources while maintaining a compiler/installation environment that automatically handles the software. This environment would then automatically optimize the software for the specific computer system and its particular hardware configuration during the installation process and migration of this software to newer generation systems would be a non-issue.

      Another approach would be to add an abstraction layer between the hardware and software very much like what is done with virtualization, Java, ZFS, LVM, DirectX, Crossbow et al. That would make the software more independent of the underlying hardware...

    13. Re:Why? by Tore+S+B · · Score: 1

      Another approach would be to add an abstraction layer between the hardware and software very much like what is done with virtualization, Java, ZFS, LVM, DirectX, Crossbow et al. That would make the software more independent of the underlying hardware...

      Isn't that basically how CISC works nowadays?

      --
      toresbe
    14. Re:Why? by g00ey · · Score: 1

      The problem many CISC CPUs (such as x86 based CPUS) are facing today is that they are encumbered by legacy instruction sets so as to maintain backwards compatibility. I understand that there is an abstraction layer in many x86 CPUs that emulates some of these legacy instructions at the hardware level. The downside with this is that the wafer space required for this circuitry logic could be used for something else that would improve performance instead of maintaining this backwards compatibility.

      As an abstraction layer between hardware and software; CISC cannot be compared to the implementations I mentioned in prior post. Assume that Intel introduces a new instruction set that would make any concurrent CPU without it pale in comparison. Let us call this instruction set SSE6. Any precompiled software will not take advantage of this new instruction set. The software has to be recompiled. In the examples I mentioned, the hardware support is determined at the driver level while the applications take advantage of whatever is available. As we all know, hardware and their drivers/compiler stick together like a horse and carriage.

      Maybe the ideal CPU is EPIC based, maybe it is a CISC that is not encumbered by legacy instructions or even a RISC. We will not know until we spend time and research to find out. Most likely, what is optimal will depend on circumstances or the quantum mechanical properties of the materials used which is likely to change as newer and more efficient materials are discovered. Maybe we will see all these CPUs in one and the same system eventually as they are all good at specific tasks. So it would mean a great deal if existing software could immediately take advantage of the new hardware features and optimizations as they reach the market.

    15. Re:Why? by hairyfeet · · Score: 1

      Oh please! While FOSS might be able to work in the server niche that is pretty much the ONLY place it works and even then not great, as the redistribution clause means you can't stop people from simply making endless copies. By distributing as a binary you make people buy the next version to get bug fixes and upgrades, which in turn pays for the bug fixes and upgrades to be written. There is a good reason why the largest FOSS company on the planet, Red hat, wouldn't make a pimple on the ass of MSFT and Apple, and that's because you can simply take all their work for free with Cent, the FOSS model simply cuts your own throat if you need to actually get paid, see Canonical putting ads into ubuntu and holding out a tin cup begging for donations as an example.

      Now as for why Itanic went nowhere? simple...VLIW. With VLIW the compiler is everything, it has to be damned near perfect to get any kind of performance and no matter how well you write it there will still be tons of corner cases that will cause it to stall, yet in the case of Itanic Intel had only a half ass compiler out the gate and by the time they came out with a halfway decent one AMD had forced them to go X64 and multicore which fricking killed any advantage Itanic had. It is obvious that VLIW is a dead end, hell even the GPUs are moving away from it, with AMD replacing VLIW for Vector, first in their GPUs followed by their APUs.

      The simple fact is you can do everything you could on Itanic with a Tesla or Firepro card and STILL enjoy the incredible amount of software and OSes for X86, no point in taking a platform with less software and compiler issues.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    16. Re:Why? by rot26 · · Score: 1

      Donnie and Marie fans are a touchy lot, are you?

      --



      To ensure perfect aim, shoot first and call whatever you hit the target
    17. Re:Why? by g00ey · · Score: 1

      Nowhere did I state that it should be free. If you remove the "F" from the FOSS you are mentioning then you are talking my language. While I'm a proponent of FOSS I don't think all open source software necessarily should be free. If people are concerned about this openness then perhaps some kind of encryption or other ways to obfuscate the source code that would make it understandable only to the compiler would be in place. However, in the end I don't think people would want to obfuscate the code before distribution. After all, even binaries can be reverse engineered and cracked so going open source shouldn't be that big of a deal.

  2. There are a hell of a lot of Itanium users by attemptedgoalie · · Score: 4, Funny

    I'll be buying a number of systems with these in a few months when they hit the street and the budget's ready. I'll be able to virtualize a lot of our old PA-RISC boxes into a smaller and more efficient set of systems.

    But you're right, they suck because you can't play Angry Birds on it.

    --
    My mom says I'm cool.
    1. Re:There are a hell of a lot of Itanium users by greg1104 · · Score: 1

      Intel provides an Itanium reference board that makes it possible for other manufacturers to release OEM Itanium based systems. As a second manufacturer example, I've used on of Bull's Novascale Bullion servers. It wasn't very cost effective, but it did include 256 cores, and continued running just fine when one socket was damaged during shipping. The sort of applications that need that many cores and heavy redundancy against hardware failures exist, and no commodity hardware will satisfy them. There's just only a few hundred thousand of such systems sold each year.

    2. Re:There are a hell of a lot of Itanium users by Anonymous Coward · · Score: 1

      With the software requiring to fill your raised floor with Itanic servers, the cost of hardware usually is the lesser of your worries.

    3. Re:There are a hell of a lot of Itanium users by Anonymous Coward · · Score: 1

      Intel would have a wet dream if a few hundred thousand titanium systems were sold each year. I'd revise that number down a few orders.
      The number of non-HP itanium vendors is very very very very narrow and getting smaller by the day. Niche products.
      The market for 256+ core single image systems is also vanishingly small.

    4. Re:There are a hell of a lot of Itanium users by unixisc · · Score: 1

      What I'm wondering is why Intel doesn't sit down w/ organizations that still support Itanium, such as Debian and FreeBSD, to optimize those OSs for the Itanium. Similarly, they could also work w/ the GCC and Clang guys to make sure that additional work gets done to finetune those compilers so that they can make the best use of these CPUs.

      But these CPUs seem more ideal for supercomputing work, not the Google or Facebook types. Their needs, aside from Xeon or Opteron, can be met even by SPARC servers - those too can run Linux or BSD, and they can then do what they do but on more failsafe hardware.

    5. Re:There are a hell of a lot of Itanium users by unixisc · · Score: 1

      In the meantime, how is POWER8 coming along?

    6. Re:There are a hell of a lot of Itanium users by unixisc · · Score: 1

      Uh, no, Itanium could only run Windows Server 2008, but that too was Itanium II. For Itanium III, software would have to be recompiled, and since Microsoft has dropped support for that CPU, you can be sure that it won't happen.

      Heck, even the Linuxes have dropped support for Itanium - the only exception being Debian. On the BSD side, only FBSD supported it initially, although looks like NBSD support might be there in version 6.0. But w/ the compatibility breakage b/w each generation, looks like it would have to be recompiled each and every time (unless they freeze a certain core, say the 9500, and then just improve performance by adding more cores). In which case, GNU HURD should be ported to this platform - sounds like the perfect OS for it.

    7. Re:There are a hell of a lot of Itanium users by Desler · · Score: 1

      What I'm wondering is why Intel doesn't sit down w/ organizations that still support Itanium, such as Debian and FreeBSD, to optimize those OSs for the Itanium.

      Because it wouldn't benefit them economically?

      Similarly, they could also work w/ the GCC and Clang guys to make sure that additional work gets done to finetune those compilers so that they can make the best use of these CPUs.

      Why would they bother? They already dropped IA-64 support in their own compilers after version 11.1.

  3. Re:Failtanium by rwa2 · · Score: 1

    I ought itanic it n ceberg nd ank nto he ea

  4. Re:Failtanium by TheLink · · Score: 4, Funny

    I think there is a world market for about 5 Itanium computers.

    --
  5. Great news for Oracle databases! by gtirloni · · Score: 2

    The next upgrade will surely make things fly!

    --
    none
  6. What's twice a small number? by davecb · · Score: 2

    My leaky/biased memory says these machines were a speed disappointment. Is this doubling going to make them faster or slower than an x86?

    --dave

    --
    davecb@spamcop.net
    1. Re:What's twice a small number? by betterunixthanunix · · Score: 2

      At least according to Wikipedia, Itanium's performance was disappointed when compared to other RISC architectures, ten years ago:

      https://en.wikipedia.org/wiki/Itanium#Itanium_.28Merced.29:_2001

      One of the traps Intel tends to fall into, at least according to someone I know who worked there during the Itanium "hype days," is that the architecture team does not communicate with the compiler team. Both Itanium and x86 fall into this trap, although x86 is far more illustrative of the problem (most compilers can only take advantage of a small fraction of the total number of x86 instructions; most instructions are too complicated, and most programming languages do not make it easy to specify when such complex instructions are advantageous). I suspect that in a few decades, compiler technology will have advanced enough that Itanium would beat the pants off x86 in typical "enterprise" applications, although by then Itanium will probably have been forgotten.

      --
      Palm trees and 8
    2. Re:What's twice a small number? by Anonymous Coward · · Score: 1

      The current Xeon E5-2670 (8 core, 2.6GHz, 2012) can do roughly 4x the performance of the previous Itanium 9350 chip (4 core, 1.73GHz, 2010), according to spec.org CPU2006 benchmark results. I think Itaniums do slightly better with FP, the Xeons win with INT.

      But that's per chip, and the Itanium systems are going up to 8 chips, so a single 8 socket Itanium system was getting roughly the same performance (in 2010) as a 2-socket E5-2670 in 2012. I don't think the Xeons go up to 8-sockets.

    3. Re:What's twice a small number? by Anonymous Coward · · Score: 3, Interesting

      Perhaps Intel fell into the trap of not communicating with the compiler team, but HP certainly did not.

      The development of the EPIC concept at HP already started in 1992 as the to-be-successor for the HP-PA architecture. Look up e.g. the many joint research papers of CPU-architecture and compiler engineers for PlayDoh (or see e.g. http://www.hpl.hp.com/techreports/93/HPL-93-80.html for an intro to PlayDoh).

      The compiler technology to do well for EPIC architectures was mostly available by the time IA64 launched. Arguably it hadn't advanced enough to be considered "ready for prime time", but things like data flow analysis of predicated code (http://www.hpl.hp.com/techreports/96/HPL-96-119.html), if-conversion (various influential papers), VLIW scheduling (e.g. selective scheduling a la Moon&Ebciolu), interprocedural analysis and various other interprocedural analyses were available and actually implemented in the HP compiler and probably also in the Intel compiler.

      (John C. Dvorak wrote "How the Itanium Killed the Computer Industry". Perhaps one day I'll write "How the Itanium Revived Compiler Scalar Optimization Research" :-)

      I think a bigger problem for Itanium was the underwhelming Merced. We used them mostly to heat the SuSE Maxtor building, they weren't good for much else. Slow, power-hungry, inefficient. And by that time, the market for things like database servers and high-end engineering workstations (where HP-PA was big) was imploding due to the advances on commodity architectures like AMD64 running Linux or even just Wintel32. Merced was a disaster, the chip wasn't ready and the compiler technology was not available widely enough, and by the time Madison came along the reputation damage was too big to be undone.

      It probably also didn't help that support for Itanium in Linux was never very good. The "typical hacker" didn't have access to IA64 and the major companies supporting IA64 didn't invest in Linux-for-IA64. Compare how IA64 funding for Cygnus/Redhat got cut before binutils was complete (to this day, binutils for ia64 is still far from complete) to how AMD funded and cooperated with SuSE to get a good x86-64 Linux ecosystem even before First Iron. Also, GCC is only since recently beginning to catch up with the proprietary compilers of HP and Intel (and also e.g. SGI's Open64), but neither HP nor Intel ever really understood how GCC is a corner stone for the whole GNU+Linux system. For example, bash compiled by ecc was much faster than bash compiler by gcc -- but no Linux distribution ever shipped an ecc based complete distribution. An official LLVM port for IA64 doesn't even exist, but a port for the long-dead Alpha *does*. What does that tell you?!

      Mis-management and lack of vision are as much a cause for Itanium's failure as the technology itself....

    4. Re:What's twice a small number? by fatphil · · Score: 1

      I understand that for "compatibility" they squeezed a little 386-compatible core in the corner of the chip. It was also my understanding that some people benchmarked the chip by feeding it x86 code, and saw a 10-year-old core struggle with the load. This was not good publicity for their enterprise flagship.

      Might all be urban legend, or misremembered, or I might be on drugs.

      --
      Also FatPhil on SoylentNews, id 863
    5. Re:What's twice a small number? by eabrek · · Score: 2

      The early processors had a functional unit for translating x86 into Itanium (it was probably area-wise bigger than a 386, but it just read x86 opcodes and produced Itanium instructions). It was later removed, and x86 support was handled in software: http://www.xbitlabs.com/news/cpu/display/20060120105942.html

    6. Re:What's twice a small number? by TemporalBeing · · Score: 1

      My leaky/biased memory says these machines were a speed disappointment. Is this doubling going to make them faster or slower than an x86?

      --dave

      The big issue, IIRC, is that Itanium was dead slow in its x86 emulation in the first few rounds. Intel's ideas as initially to emulate the x86 chips in software so that the Itanium wouldn't lose their x86 market and they could switch everyone over. They later went back and remove the software emulation and put an x86 die on to do the work in order to make it faster.

      In native mode, I've never heard a complaint about Itanium and speed - only its x86 support mode.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    7. Re:What's twice a small number? by TheRealMindChild · · Score: 1

      The "typical hacker" didn't have access to IA64 and the major companies supporting IA64 didn't invest in Linux-for-IA64

      This has nothing to do with availability, or even cost per unit factor. These machines were plagued with the same problem that Alpha servers had... they weigh in excess of 200lbs. Even as a hobby, for a free machine, I'm not paying shipping on that bastard

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    8. Re:What's twice a small number? by petermgreen · · Score: 1

      I don't think the Xeons go up to 8-sockets.

      Intel do have xeon processors that support 8-socket systems and afaict at least HP and supermicro make 8-socket xeon solutions (I think HP sell them as fully-built servers while supermicro sell them as a "barebones" system to which you add processors and drives yourself).

      However afaict the processors that support 8 socket setups are both underwhelming (high core counts but low clockspeeds and still on nahelm technology) and expensive compare to those for 2-socket systems.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    9. Re:What's twice a small number? by unixisc · · Score: 1

      HP had in the 90s acquired 2 VLIW companies - Multiflow and Cydrome - and already had a lead in VLIW compiler technology. Once they made the alliance w/ Intel, they had the grand vision of replacing both the x86 and PA-RISC lines w/ the successor Merced. As I pointed out above, leading RISC CPUs were already adapting MIMD techniques intrinsic to VLIW, while moving the dynamic analysis to the CPU to the compiler didn't do much for the CPU real estate, since they weren't using much to begin w/.

      Yeah, Intel and HP were both short sighted by not recognizing the importance of both Linux and BSD to the future success of Itanium. Initially, it was all focussed on various projects, such as HP/UX, OSF/1, Solaris and so on. Oh, and then there was that SCO led project Monterrey, which was supposed to merge Unixware, AIX and some other Unixes into a single Unix for the Itanium. It never materialized. Linux would have been pretty happy to go on the Itanium had Intel and HP pushed it that way. As it is, when SGI moved from MIPS V to Itanium, they also moved simultaneously from Irix to Linux. This was the perfect opportunity to unify several Unixes so that the only differences would be in licensing - say if they had Monterrey for proprietary software, FreeBSD and Linux for Open Source, then the CPU would have had a simple array of choices and taken off.

      On the compiler front too, I agree w/ you. Intel should have worked w/ GCC, and much later, Clang, to ensure that more active development on their compilers happened outside the company. That would have enabled both Itanium and the various OSs to work synergistically w/ each other.

      OVMS in the meantime could have continued to live on the Alpha, NonStop on MIPS, XP on x64 and Solaris on SPARC. Itanium need not have been targeted at platforms where it was ill suited.

    10. Re:What's twice a small number? by davecb · · Score: 1

      I looked at some older TPC results, and see the previous Itanium delivering 4/7 the speed of the T5440, one of Sun's oldest threads-not-clock-speed boxes. Compared to IBM Power 7, Itanium delivered 4/10, so the doubling should being it up to 80% of the IBM.

      Not to be sneezed at! Nevertheless, not competitive with Power, Fujitsu (Sun) M series or even the new Sun T4 boxes.

      --dave

      --
      davecb@spamcop.net
    11. Re:What's twice a small number? by Tore+S+B · · Score: 1

      Just as the AlphaServer had desktop equivalents, so did the Itanium, which were discontinued.

      --
      toresbe
    12. Re:What's twice a small number? by TemporalBeing · · Score: 1

      I looked at some older TPC results, and see the previous Itanium delivering 4/7 the speed of the T5440, one of Sun's oldest threads-not-clock-speed boxes. Compared to IBM Power 7, Itanium delivered 4/10, so the doubling should being it up to 80% of the IBM.

      Not to be sneezed at! Nevertheless, not competitive with Power, Fujitsu (Sun) M series or even the new Sun T4 boxes.

      One question that begs: were those TPC tests done on Itanium optimized well enough for Itanium? Or was there another bottleneck other than the processor?

      One of the early on issues with Itanium was that it was hard for the optimizers to get right. I think they solved that, but I don't know when.

      And of course it is hard to make apples-to-apples comparisons between architectures unless you have a reference system where the only thing you change is the processor, and verify that the code running on top of it is equally optimized for it and the hardware in the reference system. There are many factors - something as simple as a bad network card could throw off the results if you had to converse over the network. I'm not familiar with TPC tests, but I would assume they would be including processor, memory, network, and storage - not simply processor given that they are trying to test the transactional performance of a system, which has little to do with the processor itself and more to do with the networ, storage, and application being tested.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    13. Re:What's twice a small number? by davecb · · Score: 1

      They're TPC results, so they are from the vendors, and optimized up the gazoo (:-)) --dave

      --
      davecb@spamcop.net
  7. Why waste a product run? by Anonymous Coward · · Score: 1

    From Intel's view as an innovation company, it kind of makes sense to try out new stuff on a platform that will not matter that much.
    And since they know HP will buy them, Intel know they will be field tested.

  8. Re:The article misquotes facts by Anonymous Coward · · Score: 1

    By 'more', don't you mean 'everything'? I'm no Itanium expert, but I was under the impression that the compiler had to tell it precisely which instructions it could execute in parallel in any clock cycle.

    We learned more than a decade ago that relying on the compiler to tell the CPU how to work was insane. I have very not fond memories of early RISC CPUs which didn't have any instruction interlocks so you had to order instructions to ensure a calculation would be complete by the time you read the result.

  9. Thank you HP? by jandrese · · Score: 3, Interesting

    I guess all of that money that HP has been dumping into Itanium development is finally paying off. Everybody else assumed Intel was just going to discontinue the product for obvious reasons, but here they are releasing a major upgrade to the core architecture. It still makes me wonder what HP sees in Itanium that makes them so gung ho about it though. Is it the vendor lock in? Is this upgrade enough to finally push Itanium past x86 based processors in some performance metric?

    --

    I read the internet for the articles.
    1. Re:Thank you HP? by Desler · · Score: 2

      It's because they spent a shit ton of money porting software to it. They don't want to have to incur that cost again to port away.

    2. Re:Thank you HP? by Billly+Gates · · Score: 2

      Still who is going to buy it now?

      Remember the Alpha? Slashdot ran on Alpha's for 5 years. They had a new version out and it didn't matter. HP wanted Itanium and purposedly made sure people wouldn't buy it and crippled the product line for the inferior Itanium. Makes you wonder why they bought it?

      After Windows 2000 dropped support in RC 3, it didn't matter. Who in their right mind would invest in a dead platform?

      This new chip could be 20x faster than a xeon and use 1/10 of the power! No one wants to invest in it and be dumped later by the likes of Oracle.

      --
      http://saveie6.com/
    3. Re:Thank you HP? by Abalamahalamatandra · · Score: 2

      Hell, on the OpenVMS side, it wouldn't shock me a bit to find out that they don't even HAVE a team any more that's capable of porting it to other architectures. They likely say they do, to fulfill government contracts that specify that OpenVMS can't be orphaned, but I wonder what the reality is.

    4. Re:Thank you HP? by TheRealMindChild · · Score: 1

      It still makes me wonder what HP sees in Itanium that makes them so gung ho about it though

      The same thing Apple saw in MIPS

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    5. Re:Thank you HP? by TheRaven64 · · Score: 1

      OpenVMS and NonStop effectively only run on Alpha and a surprising number of companies have mission-critical software that works on one of these two platforms.

      --
      I am TheRaven on Soylent News
    6. Re:Thank you HP? by Billly+Gates · · Score: 1

      I wonder what management is going to do or are doing? I expect they are already underway replacing them. I doubt HP is porting them to x86 or ARM as it maybe too late for those that are retiring these with win32 or Linux equilivent of different applications that do the same tasks. It is not like you can get an emulator for these but these are systems I would not want to invest a penny into anymore as it would be a penny lost 3 years down the road when intel stops production and I can no longer even get motherboards if one server fails.

      HP has their heads up their ass if they do not have a migration plan at least so these can be run under virtual machines for decades to come.

      --
      http://saveie6.com/
    7. Re:Thank you HP? by linatux · · Score: 1

      If HP ditch Itanium, they effectively ditch HP-UX. They can (have?) ported HP-UX to x86, but why would anyone pay top $ for HP-UX on x86 - they would just use Linux instead. Without HP-UX, they don't have a tier 1 platform & will be drowned by Red Hat & SuSE.

      Meanwhile, Intel is busy building the RAS features of Itanium into x86 - as these get implemented into Linux, HP-UX will become irrelevent anyway.

      IBM & Power have a little more headroom - be interesting to see how long it lasts.

    8. Re:Thank you HP? by unixisc · · Score: 1

      NonStop on MIPS, not Alpha

    9. Re:Thank you HP? by TheRaven64 · · Score: 1

      Uh, I meant Itanium. Freud got me again - I'm still bitter about it killing a superior architecture through employing better sales drones.

      --
      I am TheRaven on Soylent News
    10. Re:Thank you HP? by unixisc · · Score: 1

      True, and then not being able to replace it. Now, that was lame!

    11. Re:Thank you HP? by tigersha · · Score: 1

      If you think some brand name beige Linux box is going to replace a nonstop system do yourself a favour and come out of mom's basement.

      Nonstop actually means what they say.

      No. Stops.
      Period.

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
  10. Re:Failtanium by Anonymous Coward · · Score: 1

    3 Words: VMS + Fortran + Mission Critical

    If it's going to cost you 250M to migrate to another platform, or 20M to buy replacment itanic hardware,
    which one are you going to do?

    Companies and large institutions with these kinds of equations exist in many places.

    They are the ones that actually needed computers when computers 1st came out.

  11. Too bad by Billly+Gates · · Score: 1

    We already switched. ... ok a former customer I worked with already switched.

    Thank you Oracle for convincing us that it is dead.

    No one will touch it with a 10 foot pole. I hope HP wins the lawsuit agaisnt them and Intel also sued Oracle for damages. When they violated that contract it gave a lot of hurt for those who have invested so much in Itanium.

    Now it doesn't matter as no one will touch it.

    --
    http://saveie6.com/
  12. The most important improvement... by eap · · Score: 4, Funny

    From TFA:

    Poulson can issue 11 instructions per cycle compared to Tukwila's six.

    These go to eleven.

  13. Re:Failtanium by Tapewolf · · Score: 1

    Balls, that was supposed to be a 'funny' mod.

  14. You can still buy Itanium?!? by vinn · · Score: 3, Funny

    You can still buy Itanium chips? Holy crap. Are they found on the same aisle of the department store as the iceboxes and cotton gins?

    --
    ----- obSig
  15. Re:Failtanium by tgd · · Score: 1

    That's funny, because I've personally worked on hundreds of them.

    *woosh*

  16. It's simple: by Type44Q · · Score: 1

    This is just Intel putting on a show of competing with themselves so that they don't get accused of monopolistic behavior... :p

  17. Re:The article misquotes facts by Dogtanian · · Score: 1

    If OOOE is out-of-order execution, itanium does oooe fine. It just expects compiler to tell more about it.

    We learned more than a decade ago that relying on the compiler to tell the CPU how to work was insane.

    Correct me if I'm wrong, but IIRC one very major problem with Itanium was that Intel, having designed it around this philosophy, never properly implemented (or were able to implement) the compilers it relied on to do this.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  18. Behind x86 in process by erice · · Score: 1

    This is an annoucment for a 32nm Itanium. Intel has been shipping 22nm x86 since spring.

    1. Re:Behind x86 in process by petermgreen · · Score: 1

      Intel has been shipping 22nm x86 since spring.

      It seems that in the Intel x86 world the higher you move up the product line the older the technology gets.

      Intels x86 processors right now are best grouped by the sockets they use. There are basically three "current" (that is not "replaced" by a newer socket) sockets.

      LGA1155 is the mainstream desktop and low end single socket server socket. This is the only socket for which 22nm parts are currently available.
      LGA1356 is intended for low end dual socket systems but I get the impression it didn't really catch on (newegg lists 10 dual lga1356 boards and 34 dual lga2011 boards under "server motherboards"). Afaict it is currently using 32nm sandy bridge based parts.
      LGA2011 is used for high end desktop parts and 1-4 socket servers. It is currently using 32nm sandy bridge based parts.
      LGA1567 is used for systems that need 8 sockets or insane ammounts of ram. It's also 32nm but is using the older westmere microarchitecture.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    2. Re:Behind x86 in process by unixisc · · Score: 1

      Probably want to fill up fab utilization.

  19. It's easy to criticize Itanium in hindsight by Larry_Dillon · · Score: 1

    If it hadn't been for AMD's 64 bit extensions, we'd all be running Itanium servers right now. AMD forced Intel to release a 64bit x86. If AMD hadn't, all of the effort that is being put into Intel's current 64bit chips would have go into Itanium and it would be a very strong platform. The alternative, PAE, sucked.

    --
    Competition Good, Monopoly Bad.
    1. Re: It's easy to criticize Itanium in hindsight by Desler · · Score: 1

      Well as long as you ignore that all the legacy x86 software that is still running today wasn't going to be ported to Itanium. People would have just stuck to x86 rather than spending billions on porting and rebuying working software.

    2. Re: It's easy to criticize Itanium in hindsight by TheRaven64 · · Score: 1

      It was easy to criticise Itanium at the time, in comparison to Alpha, or PowerPC too. If we'd somehow all been forced to rewrite all of our legacy x86 code, either of these would have been a better choice. In fact, emulating x86 on PowerPC is a lot easier than on Itanium, so it would have been a more natural path if Intel had managed to kill x86. Lucky for them, they failed...

      --
      I am TheRaven on Soylent News
  20. The Itanium is still around? by davydagger · · Score: 1

    https://www.youtube.com/watch?v=HLgQMtquS6Y

  21. Do these chips make the user's face glow blue ? by vikingpower · · Score: 1

    I remember that in the "Hyperion" space opera, there is a "Poulsen" anti-age treatment. It has only one drawback: repeated applications of it make the beneficiary's face glow ever bluer. I wonder about these ones...

    --
    Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
  22. hothardware eh? by turgid · · Score: 1

    Sounds like the itanic all right.

    They had one at LinuxExpo once, back in the day, allegedly running DeadRat, but we couldn't see it because it had overheated and they took it away.

    --
    Stick Men
  23. Re:The article misquotes facts by turgid · · Score: 1

    If OOOE is out-of-order execution, itanium does oooe fine. It just expects compiler to tell more about it.

    They have clairvoyant compilers now, do they?

    --
    Stick Men
  24. Its name was Itanic Poulson... by Nexion · · Score: 1

    its name was Itanic Poulson... its name was...

  25. Re:The article misquotes facts by wisty · · Score: 1

    It would be nice for virtual machines. Branch prediction is where VMs shine. But I can't see Sun (the Java people) having a big interest in it, and LLVM wasn't so widely used when Itanium had mindshare.