Though no benchmarks have been done.. is the base 2009 8 core 2.26 as fast as the 2008 8 core 2.8?
Um...benchmarks have "been done". Search Google for "Nehalem benchmarks"...
Where did you find them for the 2.26? I found them for the 2.9?
Though no benchmarks have been done.. is the base 2009 8 core 2.26 as fast as the 2008 8 core 2.8?
Someone who works at Apple (the company itself - not the store) told told me that the base 2.66GHz Quad-Core Intel Xeon "Nehalem" model is 2x faster than the 2008 Dual-Xeon (8-core) Mac Pro.
Unfortunately, the 8GB ram limit kills the deal for me, as I am looking for 16GB+ of ram.
Someone who works at Apple (the company itself - not the store) told told me that the base 2.66GHz Quad-Core Intel Xeon "Nehalem" model is 2x faster than the 2008 Dual-Xeon (8-core) Mac Pro.
Unfortunately, the 8GB ram limit kills the deal for me, as I am looking for 16GB+ of ram.
is the base 2009 8 core 2.26 as fast as the 2008 8 core 2.8?
Someone who works at Apple (the company itself - not the store) told told me that the base 2.66GHz Quad-Core Intel Xeon "Nehalem" model is 2x faster than the 2008 Dual-Xeon (8-core) Mac Pro.
Unfortunately, the 8GB ram limit kills the deal for me, as I am looking for 16GB+ of ram.
The bottom line, no matter how you look at it, is:
2.8GHz - faster in most apps that can use LESS than 8 cores
2.26GHz - faster in apps that can use MORE than 8 cores, because it has 16 threads.
but how can you predict that because you don't know how the architecture advantages of the new chips effect performance in single-threaded apps.
AND don't forget Turbo Boost which OC's the processor on single-threaded apps when the other cores aren't being used. So with the proc OC'ing to 2.5-2.6ghz should be as fast/faster than the 2.8 even on single threads.
The bottom line, no matter how you look at it, is:
2.8GHz - faster in most apps that can use LESS than 8 cores
2.26GHz - faster in apps that can use MORE than 8 cores, because it has 16 threads.
Not really, if Nehalem detects an application that is idling the other cores it will automatically overclock the used cores a few hundred Mhz while lowering clocks on the other cores.
The 2.26GHz Nehalems are not faster then the 2.8GHz. Not the same, not even close. Lower.
Why is this so? - Because the architecture although different (Integrated memory controller and such) is actually very similar. They are built in the same way with the same base architecture. A bit like two children from the same parents. Both come from the same base design but arrive in different conclusions.
Nehalem is not a complete re-design it is a roll back of the Front Side Bus and a roll out of an integrated memory controller among other additions and a scalable Multi-Core die. Now it is important to recognise that the integrated memory controller makes the avalible memory bandwidth go through the roof but with DDR3 memory the Core 2 Quads of yesteryear were never starved for bandwidth and often in benchmarks increasing the RAM from DDR3-1333 to DDR3-1600 or even DDR3-2000+ would yield but 1-2% difference. This is relevent as the design and total memory requirements of the old chip and the new one are very similar. Latency has improved and there is your main performance increase with regards to Memory access.
But this all means nothing when you actually look at benchmarks. Core i7 (Consumer Nehalems) have been available on the market for several months now and even I upgraded from a 2.66GHz Core 2 Quad (First Quad Core ever available the QX6700) to a 2.93GHz Core i7 - What sort of performance enhancements have I seen? .... well not many it is faster no doubt about that but clock for clock I would say its around 20-25% faster. That is Clock for Clock. Now compare that to the 2.26GHz vs the 2.8 and this is a 45nm 2.8Ghz I had the original 65nm 2.66 with 8MB L2 Cache (The 2.8's had 12MB L2 Cache and much faster Buses 1600FSB, mine 1066FSB) And I just have to say no.
Ok so what have we learned? - The new 2.26GHz is not faster. The 2.66GHz however is faster then the old 2.8GHz. I notice people talking about threads (16 Threads on the new vs 8 on the old) and although it has more threads there are not many applications today that can manage 8 threads well let alone 16. Most are optimised for 1 of course. The ones that quote SMP to begin with are 2 to 4 and 8 to 16 .... really looking at a handful of apps that can do that well. When you add in to that the 16 threads are only running over 8 physical cores ... well you cant get blood out of a stone if the 8 cores are already taxed adding another 8 threads in to the mix wont get you much.