One hundred years from now It won't matter
What kind of car I drove What kind of house I lived in
How much money I had in the bank Nor what my cloths looked like.... But The world may be a little better Because, I was important In the life of a child.
-- from "Within My Power" by Forest Witcraft
...btw, how is nehalem pronounced correctly? ne-ha-lem? ne-hale-em? am just wondering all the time![]()
1. Asus P5Q-E / Intel Core 2 Quad Q9550 @~3612 MHz (8,5x425) / 2x2GB OCZ Platinum XTC (PC2-8000U, CL5) / EVGA GeForce GTX 570 / Crucial M4 128GB, WD Caviar Blue 640GB, WD Caviar SE16 320GB, WD Caviar SE 160GB / be quiet! Dark Power Pro P7 550W / Thermaltake Tsunami VA3000BWA / LG L227WT / Teufel Concept E Magnum 5.1 // SysProfile
2. Asus A8N-SLI / AMD Athlon 64 4000+ @~2640 MHz (12x220) / 1024 MB Corsair CMX TwinX 3200C2, 2.5-3-3-6 1T / Club3D GeForce 7800GT @463/1120 MHz / Crucial M4 64GB, Hitachi Deskstar 40GB / be quiet! Blackline P5 470W
http://de.youtube.com/watch?v=fet-Tr...eature=related
7 secs in to the vid.
Some preliminary typo for ref ...
...
===N/A===
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...
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.
Last edited by bowman; 07-25-2008 at 02:12 PM.
One hundred years from now It won't matter
What kind of car I drove What kind of house I lived in
How much money I had in the bank Nor what my cloths looked like.... But The world may be a little better Because, I was important In the life of a child.
-- from "Within My Power" by Forest Witcraft
Call the city chamber of commerce:
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.
One hundred years from now It won't matter
What kind of car I drove What kind of house I lived in
How much money I had in the bank Nor what my cloths looked like.... But The world may be a little better Because, I was important In the life of a child.
-- from "Within My Power" by Forest Witcraft
Crunch with us, the XS WCG team
The XS WCG team needs your support.
A good project with good goals.
Come join us,get that warm fuzzy feeling that you've done something good for mankind.
Exactly.
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.
![]()
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.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
Bookmarks