[Beowulf] itanium vs. x86-64
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Toon Knapen toon.knapen at gmail.comMon Feb 9 23:59:11 PST 2009
- Previous message: [Beowulf] itanium vs. x86-64
- Next message: [Beowulf] itanium vs. x86-64
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > SGI altix3000 series is basically 280ns (random 8 byte reads from big > buffer) shared memory until 4 sockets. itanium needs 8 clock-cycles to fetch a double from L2 cache (floats are not stored in L1) and 110 clock-cycles from L3 IIRC, how is that with x86-64? > f) itanium2 total focussed upon floating point, yet that is about the > least interesting thing for such hardware to do; there always have been > cheaper floating point solutions than itanium2. Let's forget about the > disaster called itanium-1. A wrong focus. Integer speed simply matters > for such expensive cpu's. This is why IBM could sell power6. same goes for x86-64, no?
- Previous message: [Beowulf] itanium vs. x86-64
- Next message: [Beowulf] itanium vs. x86-64
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
