Nehalem-EP......BLOOMFIELD

[FlanK3r]

maybe try Nero recode DVD, crysis bench, worldbench, winmedia encoder (set simillary as herehttp://techreport.com/articles.x/14606/8 etc )

[XS Janus]

^Yes do some real life encoding tests so we see those to.

Thanks for posting all this early stuff, man.

[Donnie27]

1 stick of 2G DDR3-1066 ...

I'd bet on Single channel 1600MHz LOL! Wasn't all 3 channel capable of something like 26GB?

What speed or is that the default speed?

[[XC] NetburstXE]

Did anyone else notice the below 1 volt?

Yes. I don't understand how that works

[JCornell]

What speed or is that the default speed?

default speed of what ?
The DDR3 that I plugged is 1066 ...

[anubis]

Please do the BOINC test MM requested

[JCornell]

Yes. I don't understand how that works

Why this matter ? that's just false volt detect ...
How to judge with software that doesn't fully support(calibrate) for latest(final) hardware ?

Actually vcore for 45nm CPUs is approx nominal 1.1v ... (of course this is for default speed)

[JCornell]

Please do the BOINC test MM requested

I forgot to test after heard from Mr.MovieMan request ... I will pleased and as possible to fulfill some casual bench, nothin' more ... Hope all the bench will useful for some users ...
Afterall, this is just for references ... and it's endless to compare all of it by my own ...

[The Coolest]

Why this matter ? that's just false volt detect ...
How to judge with software that doesn't fully support(calibrate) for latest(final) hardware ?

Actually vcore for 45nm CPUs is approx nominal 1.1v ... (of course this is for default speed)

I don't think that this is accurate.
The field Core Temp assumes for VID is actually used as FID (multiplier). So don't trust the early VID readings.

[metro.cl]

Why this matter ? that's just false volt detect ...
How to judge with software that doesn't fully support(calibrate) for latest(final) hardware ?

Actually vcore for 45nm CPUs is approx nominal 1.1v ... (of course this is for default speed)

Hello JC,

Do you know which will be the last stepping? from what i see the actual mem controller is not fully working (i'm right? or is a mobo issue?).

I cant wait to see a fully working nehalem and see its overclock, also some real world gaming would be nice or some HD decoding/encoding.

[Movieman]

I forgot to test after heard from Mr.MovieMan request ... I will pleased and as possible to fulfill some casual bench, nothin' more ... Hope all the bench will useful for some users ...
Afterall, this is just for references ... and it's endless to compare all of it by my own ...

Thank you.. It should take you maybe 10 mins max to download,install and run the benchmark.
The benchmark itself is app 60-90 seconds max.
You will see this (or like it) on your BOINC manager screen and just highlight and on the left hit "Copy selected messages" and then paste into a post.
6/29/2008 4:48:30 PM||Suspending computation - running CPU benchmarks
6/29/2008 4:49:01 PM||Benchmark results:
6/29/2008 4:49:01 PM|| Number of CPUs: 4
6/29/2008 4:49:01 PM|| 3558 floating point MIPS (Whetstone) per CPU
6/29/2008 4:49:01 PM|| 8289 integer MIPS (Dhrystone) per CPU
The above was on a Q6600 at 3600mhz with some items running in the background.
I would imagine the Nehalem to be above the 4000 mark on Whetstone.
The question is how much above 4000..

Again, my thanks for doing this.
It's not a exact bench but rather will give a good idea of the Nehalems computational power.

[Donnie27]

default speed of what ?
The DDR3 that I plugged is 1066 ...

The RAM of course, thank you!

[Seraphiel]

That's correct.

The Nehalem code name is unique in that it applies to the overall microarchitecture that includes all the above products. Correct me if I'm wrong, but this is the first time in recent history where Intel has used a codename for a microarchitecture that did NOT also apply to a specific product.

Here's the comprehensive list of Nehalem product code-names...

Wait a minute

NVIDIA doesn't have a license for the QPI connection, but could make a chipset for anything that doesn't have QPI. The lack of QPI info on the lower market solutions, does that mean they use the old FSB and not QPI, and could NVIDIA possibly make SLI chipsets for these if they wish to?

And even if NVIDIA doesn't have the QPI license, couldn't they just unlock the driver and support SLI on Intel's own chipset, if they wanted to?

Just speculation and sorry for off-topic.

[Donnie27]

Wait a minute

NVIDIA doesn't have a license for the QPI connection, but could make a chipset for anything that doesn't have QPI. The lack of QPI info on the lower market solutions, does that mean they use the old FSB and not QPI, and could NVIDIA possibly make SLI chipsets for these if they wish to?

And even if NVIDIA doesn't have the QPI license, couldn't they just unlock the driver and support SLI on Intel's own chipset, if they wanted to?

Just speculation and sorry for off-topic.

QPI's main use is for Socket to Socket communication on this chart. No need to worry about it on Single socket systems. As for links between the I/O Hub and the Processor, Intel already uses a Serialized Point to Point interface called DMI. It is an offshoot of PCI-E.

nVidia also doesn't have a license for any of the new sockets and or IBEX (south bridge) as well according to at least on IBM platform guy I know. All Intel does is switch incoming I/O , to the processor instead of DMI, to Quick path and nVidia can only hope for Low end Legacy Products without an IMC

[bowman]

Wait a minute

NVIDIA doesn't have a license for the QPI connection, but could make a chipset for anything that doesn't have QPI. The lack of QPI info on the lower market solutions, does that mean they use the old FSB and not QPI, and could NVIDIA possibly make SLI chipsets for these if they wish to?

The lower markets have just what amounts to an I/O southbridge. The northbridge is entirely integrated on the CPU, and PCI-E 2.0 connects directly onto the CPU. Even less wiggle room for NVIDIA. They could pull a Skulltrail and launch boards with a couple of NF200 chips to 'enable' SLI and and claim there's special sauce in those.. But that didn't fly so well the first time, I fear they'd get publically shredded if they pulled that stunt again.

And even if NVIDIA doesn't have the QPI license, couldn't they just unlock the driver and support SLI on Intel's own chipset, if they wanted to?

Of course they could, but that's exactly what Intel wants. SLI on Intel chipsets. At the same time NVIDIA's chipset business would go out of business, at least for desktops, because the 6 and 7 series for LGA775 sure has given them a frayed reputation.. Even if their Nehalem chipsets turned out 'okay', why would anyone bother if Intel had SLI and with the cloud of data corruption, crashes, bugs and bad drivers looming over nForce?

[Seraphiel]

Thank you both for explaining this

[Donnie27]

The lower markets have just what amounts to an I/O southbridge. The northbridge is entirely integrated on the CPU, and PCI-E 2.0 connects directly onto the CPU. Even less wiggle room for NVIDIA. They could pull a Skulltrail and launch boards with a couple of NF200 chips to 'enable' SLI and and claim there's special sauce in those.. But that didn't fly so well the first time, I fear they'd get publically shredded if they pulled that stunt again.

Of course they could, but that's exactly what Intel wants. SLI on Intel chipsets. At the same time NVIDIA's chipset business would go out of business, at least for desktops, because the 6 and 7 series for LGA775 sure has given them a frayed reputation.. Even if their Nehalem chipsets turned out 'okay', why would anyone bother if Intel had SLI and with the cloud of data corruption, crashes, bugs and bad drivers looming over nForce?

You're totally under estimating the nVidia Faithful, Fanboys and Loyalists. They're afraid to even try anything but nVidia. Some even claim to have have switched from Intel chipsets and are much happier with nVidia. There's thread about Intel not giving nVidia a license and why. Amazingly nVidia Fans think Intel should Pay for SLI while nVidia should get all Intel for free! Giving more credence to the old saying, "Love Blinds". BTW, I'm very BIASed against nVidia but not without good reason.

[Donnie27]

Thank you both for explaining this

You're welcomed

[virtualrain]

If you want a bit more detail on how NVIDIA could support Nehalem with their own chipset, feel free to check this out...
http://www.nehalemnews.com/2008/05/e...halem-sli.html

It all depends on licensing of course and as you pointed out, a QPI license is only relevant on Bloomfield. The lower end parts don't use QPI.

[Movieman]

If you want a bit more detail on how NVIDIA could support Nehalem with their own chipset, feel free to check this out...
http://www.nehalemnews.com/2008/05/e...halem-sli.html

It all depends on licensing of course and as you pointed out, a QPI license is only relevant on Bloomfield. The lower end parts don't use QPI.

Hell, all I want is a dual socket gainstown board with 2 quad core Nehalems in it running at 4000mhz and I don't care whose chipset is in it as long as it works!

[Fuji]

well me too lol.

I was thinking about going Nehalem when it's cheap enough. I've also been facinated with the idea of two socket Nehalems. If Intel maintains their Xeon pricing for Nehalem (i.e lower clocked for pretty cheap) then i'll go dual socket when i get the money...or should i say if.

I still want to know how they plan on shoving all that cache on the 8 core Nehalem and still have it

a) yield
b) fit in a standard packaging.

[Anemone]

1 I'd take NF200 chips to get SLI - just didn't have a fondness for FBDIMMS really. But SLI on Nehalem is something I'd take just not on a Nvidia chipset.

Now mind you, Nvidia chipsets could get better. Nvidia takes risks and gives little long term support to chipset buyers. It's a business they don't treat well, and that's really why they are in the pickle they are in. You look at Nvidia GPU drivers and you know that Nvidia takes bugs pretty seriously. Why? Because they know it's something people look for, and without that they would lose a chunk of business. With chipsets they have a more captive audience. And they abuse that which shouldn't be. If instead they had to test, retest, and issue patches in days to support chipsets, you can bet the chipsets would be vastly better built. Intel's current chipset business is only rosy (and even then not always) because of years of experience. Nvidia could do the same.

So giving SLI (which is perfectly fair as a trade for getting socket/connection rights to Intel's cpu's) isn't going to kill the chipset business. It's just going to grow it up fast, and make it play in the field like it should. Give people a solid, safe, and fast platform, with maybe a version or two aimed at clockers and enthusiasts.

It's simple really. And it's high time.

[Blauhung]

well me too lol.

I was thinking about going Nehalem when it's cheap enough. I've also been facinated with the idea of two socket Nehalems. If Intel maintains their Xeon pricing for Nehalem (i.e lower clocked for pretty cheap) then i'll go dual socket when i get the money...or should i say if.

I still want to know how they plan on shoving all that cache on the 8 core Nehalem and still have it

a) yield
b) fit in a standard packaging.

a) It will most likely be very expensive
b) 4 socket server chips do not use "standard packaging"

[JCornell]

Thank you.. It should take you maybe 10 mins max to download,install and run the benchmark.
The benchmark itself is app 60-90 seconds max.
You will see this (or like it) on your BOINC manager screen and just highlight and on the left hit "Copy selected messages" and then paste into a post.
6/29/2008 4:48:30 PM||Suspending computation - running CPU benchmarks
6/29/2008 4:49:01 PM||Benchmark results:
6/29/2008 4:49:01 PM|| Number of CPUs: 4
6/29/2008 4:49:01 PM|| 3558 floating point MIPS (Whetstone) per CPU
6/29/2008 4:49:01 PM|| 8289 integer MIPS (Dhrystone) per CPU
The above was on a Q6600 at 3600mhz with some items running in the background.
I would imagine the Nehalem to be above the 4000 mark on Whetstone.
The question is how much above 4000..

Again, my thanks for doing this.
It's not a exact bench but rather will give a good idea of the Nehalems computational power.

Far from your expectation


FYR
...

[Shintai]

Poor Dave...hahaha