News for hackers. Stuff that matters.
Re:Oracle Ceases Development For Intel’s Itanium Chip by whatusername on Wednesday March 23, 2011 @12:38PM (#2360119)
Is there anyone on HN who can speak in Itanium's defense? Anyone used it and been impressed? We've all heard the Itanic jokes -- but surely there was some gold buried in there?
Re:Oracle Ceases Development For Intel’s Itanium Chip by azim on Wednesday March 23, 2011 @01:55PM (#2360469)
I did software development for NonStop Kernel on Itanium for a few years. 5 years ago, Itanium was FAST. Our software was twice as fast as competitors who used twice as many processing cores. Problem was that, unlike x86, Intel's Itanium roadmap moves slow and continually plagued by problems. About 2-3 years ago, with cost reduction in mind, we began porting software over to Linux on x86. Initially we needed 2.5x as many x86 cores to reach the performance of the 1.6Ghz Itanium 2. By the time Intel began shipping Westmere-EP processors early in 2010, each core was nearly 1:1 with Itanium, and at half the cost and 3x the density.
Re:Oracle Ceases Development For Intel’s Itanium Chip by whatusername on Wednesday March 23, 2011 @05:00PM (#2361437)
Interesting. The NonStop has always intrigued me as a platform. Thanks.
Re:Oracle Ceases Development For Intel’s Itanium Chip by sp332 on Wednesday March 23, 2011 @12:59PM (#2360218)
I've never worked with it, but the idea is that it's unbelievably fast if you have a smart enough compiler. Intel's x86 chips have a lot of logic onboard that will optimize code as it's running, in real-time. Itanium uses all of its silicon to do whatever it's told really, really fast and just trusts that the compiler has figured out all the optimizations ahead of time. Also, it has mountains of cache memory, so that helps too :)
Re:Oracle Ceases Development For Intel’s Itanium Chip by jacques_chester on Wednesday March 23, 2011 @06:59PM (#2361871)
The problem was coming up with the Sufficiently Smart Compiler to turn branchy code into explicitly parallel instructions. It never really turned up for C/C++ and Fortran code.

It would probably fly for languages like Haskell or Erlang.