The Inquirer-Home

Intel prices up Woodcrest, Tulsa server chips

Server Roadmaps SKUs us, while we kiss the sky
Fri May 26 2006, 20:08
WEEK 21 roadmaps detected on the walls of famous London pub the Porcupine show that Intel has decided on flavours and prices of its Tulsa server processors.

Tulsa MP chips have 16MB of shared L3 cache, are dual core, and have power characteristics of 95W. That, according to Intel gives big performance gains versus Paxville MP.

The prices for Tulsa, with an estimated shipping date in Q4 of 2006, are $3160 for the 7140M and the 7140N, $1980 for the 7130M and the 7130N, $1180 for the 7120M and the 7120N, and $850 for the 7110M and the 7110N.

What's all this M and N thing about, you are probably asking? The M suffix denotes 150W chips using an 800MHz bus, and the N suffix the 95W family using a 667MHz bus. There are also clock speed differences between the Ms and the Ns which also have different cache sizes.

The 7140M is a 3.40GHz 16MB part, the 7140N is a 3.33GHz, 16MB part. The 7130M is a 3.20GHz, 8MB part, while the 7130N is a 3.16GHz 8MB part.

The 7120M and the 7120N have 4MB of cache and clock at 3GHz respectively. The 7110M and the 7110N clock at 2.60GH and 2.50GHz respectively, and have 4MB of shared cache.

All these chips use something Intel calls "Cache Safe Technology" - this was formerly codenamed Pellston - and support Intel virtualisation.

As we reported earlier, Intel Woodcrest will launch on the 26th of June and ship on that date. The TDP is now 65W on 2.66GHz SKUs and below, while the 3GHz chips have 80W TDPs.

Intel will sell the 5160 Woodcrest, a 3GHz, 1333MHz part for $850; the 5150 2.66GHz 1333MHz part for $690; the 5148T for $520 - this is a 2.33GHz part; the 5130 2GHz at $315; the 5120 1.86GHz 1066MHz bus part at $250, and the 5110 1.60GHz 1066MHz CPU at $210. Ultra dense server Woodcrests will eat 40W. µ


Share this:

blog comments powered by Disqus
Subscribe to INQ newsletters

Sign up for INQbot – a weekly roundup of the best from the INQ

INQ Poll

Heartbleed bug discovered in OpenSSL

Have you reacted to Heartbleed?