I am guessing C2,3 maybe even in a D series. This is a pretty aggressive lurch for Intel.Quote:
Originally Posted by terrace215
Printable View
I am guessing C2,3 maybe even in a D series. This is a pretty aggressive lurch for Intel.Quote:
Originally Posted by terrace215
Why start with 2 or 3, when you can with 0 ? ;)
Quote:
Originally Posted by JumpingJack
...btw, how is nehalem pronounced correctly? ne-ha-lem? ne-hale-em? am just wondering all the time :p:
http://de.youtube.com/watch?v=fet-Tr...eature=relatedQuote:
Originally Posted by RaZz!
7 secs in to the vid.
Some preliminary typo for ref ... :shrug:
http://i245.photobucket.com/albums/g...lem/Type_B.jpg
...
i wonder how much performance impact the faster QPI has.
Nothing I say. Or close to nothing. Maybe if you have 4 GPUs and 12 disks and 12 USB devices :p:Quote:
Originally Posted by Hornet331
For uniprocessor platforms probably none. HyperTransport clocks doesn't make much of a difference for AMD at least. Besides, either one of those are on an entirely different scale than the FSB.. If it turns out to make a difference, just overclock. It's not stocksystems.org is it? ;)
Now JC is just making me wonder what he's blanked out above 'Turbo' there... :cool:
Also, does this mean 'Turbo Mode' is confirmed in some way on the desktop or are they still deciding whether or not to include it (TBD)? It seems like it'd fit their 'dynamic, scalable' thing quite well.
Shintai?Quote:
Originally Posted by Movieman
^
lol way to go, start your posting career here. :rofl:
lol. wrong :p:Quote:
Originally Posted by Shintai
NO WAY MAN!!! Wrong, just how some people called it fe-num, while i stand by Pheee-nom. :p:Quote:
Originally Posted by Hornet331
Pronounce phenomenal and leave off the enalQuote:
Originally Posted by Kingcarcas
fe - nom (short e)...
Pheeeenom sounds like a urinary disorder.
Call the city chamber of commerce:Quote:
Originally Posted by RaZz!
http://en.wikipedia.org/wiki/Nehalem,_Oregon
ask them how they pronounce their own town. It is near the Nehalem river, which Intel will often (not always) use river names geographically located near one of their sites as code names.
Sorry, that blanked part is SMT :p:, My mistake to cover it wrong ... :ROTF:Quote:
Originally Posted by bowman
TURBO is still TBD for 1S, but 2s is already fixed ...
Nah, I got 5 sec 920ms with a dual harpertown at 3603mhzQuote:
Originally Posted by Monstru
That Nehalem score is impressive as all hell at 2ghz
Probably i'm wrong :p:,but wasn't it actually a 2S geinstown@3Ghz that scored 6s in wprime?I'm looking at page 30 i think.Quote:
Originally Posted by Movieman
They are 24-32GB per link, 12-16GB/sec per direction.Quote:
Originally Posted by Cooper
So something like 2 cards wont do squat for sure. We dont even have much problem today with some 8-12GB/Sec link with memory on top (FSB).
'Turbo' is this thing I read about where it will clock down other cores and increase the clock on one or two cores to boost performance in less threaded apps while staying within the TDP? Or something different?Quote:
Originally Posted by JCornell
jup.Quote:
Originally Posted by bowman
Exactly.Quote:
Originally Posted by bowman
The NHM is the 1st CPU that is aware of its own TDP. This is a very interesting feature, but that also limits the "external" control on it. Whatever clock and voltage setting you apply, the CPU keeps having the last word.
In HWMonitor I tried to show the CPU TDP as it sees it, but I'm not completely sure how accurate this is.
http://www.cpuid.com/pics/nhm_03.png
Sounds like a candidate for BIOS makers to me.
If the greatest achievement of Nehalem is less control for the user I'll have to wait until they figure out something clever before I jump on it.
I remember reading this:
http://www.bit-tech.net/news/2008/06...t-on-nehalem/1
Brrrr. :(Quote:
Intel's EIST and C1E states for clock changing to save power will now work 56 percent faster in Nehalem and the chip frequency will also adapt to power supply voltage changes and vDroop - this should make a system ever more stable, but we think it might push enthusiasts into looking for the best motherboards and PSU combinations that completely minimise this clock down effect, especially if it affects performance figures.
Intel even dropped an interesting titbit that it was thinking about completely decoupling itself from rated frequencies because of the constant clock changes, however it found customers and retailers were very much against this move. Despite the fact that, internally, the CPU is constantly adjusting its clock speed, from the outside it appears like a fixed frequency due to overall averaging. No doubt this continual variation will surely make our job testing hardware reliably that much more difficult though - it depends on the level of clock changes and the quality of motherboard and power supply.
Finally, Intel also mentions in its documents that the Duty Cycle adapts to transistor variation and lifetime stress - does this mean that even if your CPU isn't made as well as the next guy's, instead of dying outright it will reduce the time that part is working. Does this translate into reducing the core frequency over time?
Dual Barcelona @2156MHz for comparison
hmm so single socket nehalem beats dual socket phenom in cpu/mmx and loses in fpu... this benchmark sure acts strange. :p
Yep strange benchmark,but it ends quickly, at least :).Quote:
Originally Posted by Hornet331
Anyone care to comment what system scored 6s in wprime?I see you people are talking about 2Ghz 2P Geinstown but all i see is 2x3.07Ghz system in that screenie (page 30) with power saving on...