Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Dell Technologies Inc. -- Ignore unavailable to you. Want to Upgrade?

To: D.J.Smyth who wrote (165610)	5/29/2001 4:44:25 PM
From: rudedog	Read Replies (2) \| Respond to of 176387

John, Darrell - this discussion misses the point. Itanium runs existing X86 code about half as fast as a 32 bit processor at the same clock speed. No ifs, ands or buts. It is way slower at running X86 code in every respect. So no matter how cool it will eventually be on code optimized for the EPIC architecture and 64 bit operations, on the code most people will be running today, it will be way slower than a XEON. There is no simple recompile or other automated approach. A program has to be completely re-written to take advantage of EPIC. The notion that a 64 bit system can in general accomplish twice the work of a 32 bit system is silly too. 64 bit systems have an advantage when large flat address space memory is needed - databases are the most obvious example. They have some advantage when working with floating point data. They have almost no advantage in working with 32 bit data, which happens to be the bulk of data out there. An Itanium running a standard file and print server - or almost any other program written for the current server base - will be slower than a Xeon running the same jobs. A lot slower.