Tuesday, April 6th 2010
Microsoft to End IA64 Support
Microsoft plans to gradually end support for the Intel Itanium IA64 architecture with this generation of Windows, SQL Server, and Visual Studio software. The Windows Server 2008 R2, SQL Server 2008 R2, and Visual Studio 2010, will be the last versions to support IA64. Mainstream support for IA64, for Windows Server 2008 R2 will end end on July 9, 2013, while in accordance with Microsoft Support Lifecycle Policy, extended support will last till another five years past 2013, ending on July 10, 2018. Till that time, Microsoft hopes that the industry will adapt itself extensively to the x86_64 (x64) architecture for enterprise hardware.
This change establishes x86_64 as the de-facto 64-bit computer architecture across all segments of computing, as far as Microsoft's market is concerned. A majority of IA64 users use the HP-UX operating system, with Microsoft Windows Server having a paltry 5 percent usage share. Having a small market share with IA64, Red Hat had last year, announced that it would end support for IA64 since the tiny userbase didn't justify having continued development of RHEL for IA64. For consumer operating systems, Microsoft ended IA64 support with Windows Vista, leaving only Windows Server versions with it.
IA64's rise to popularity came with it being the first to offer 64-bit extended memory capabilities, and after the advent of x86_64 by AMD's AMD64 technology, offered higher reliability and scalability not found with x86_64. Recent releases in Intel and AMD's Xeon and Opteron lines of enterprise-grade x86_64 processors changed that, and those chips became capable of higher scalability with support for even more sockets per system. This kills IA64's selling-points. Intel's most recent IA64 processor was the Itanium 9300 series "Tukwilla" processors that makes use of QuickPath Interconnect.
Source:
Windows Server Division Blog
This change establishes x86_64 as the de-facto 64-bit computer architecture across all segments of computing, as far as Microsoft's market is concerned. A majority of IA64 users use the HP-UX operating system, with Microsoft Windows Server having a paltry 5 percent usage share. Having a small market share with IA64, Red Hat had last year, announced that it would end support for IA64 since the tiny userbase didn't justify having continued development of RHEL for IA64. For consumer operating systems, Microsoft ended IA64 support with Windows Vista, leaving only Windows Server versions with it.
IA64's rise to popularity came with it being the first to offer 64-bit extended memory capabilities, and after the advent of x86_64 by AMD's AMD64 technology, offered higher reliability and scalability not found with x86_64. Recent releases in Intel and AMD's Xeon and Opteron lines of enterprise-grade x86_64 processors changed that, and those chips became capable of higher scalability with support for even more sockets per system. This kills IA64's selling-points. Intel's most recent IA64 processor was the Itanium 9300 series "Tukwilla" processors that makes use of QuickPath Interconnect.
15 Comments on Microsoft to End IA64 Support
Luckily Itaniums + Windows is not the most logical configuration, if you want to run Windows you're better off with Xeons in most cases. So perhaps the Itanium will stay around. Though seeing how every new generation has its screwups and the Xeons offering a lot more nowadays I can see the Itanium line being dropped by Intel.
IA64 is definitely higher performance in practically every regard compared to IA32 but the sacrifice is backwards compatibility.
As mdm-adph said, AMD basically killed the future in regards to high performance instructions sets. We're stuck with a 2+ decade old standard indefinitely. IA64 was meant to be the future.
It's okay, intel has a new baby to waste billions on and never get anywhere.
But what's mind boggling is that intel just won't give it up. Let the thing die already. By the time it's affordable to produce (I assume the price jacked from RnD and their mindset) the tech will be too old to be useful.
Intel is as much to blame for this as Microsoft. Intel never pushed IA64 towards the consumer market and Microsoft most likely expected them to. Microsoft isn't making much money on Itanium without consumer products so they are giving up on waiting.
Gotta get your digs in, eh? :laugh:
If Intel had wanted us to all be using IA64 now, we'd all be using it. What they want, they get.