i7 Turbo GT testing program with Gulftown support

[unclewebb]

i7 Turbo GT
http://www.fileden.com/files/2008/3/.../i7TurboGT.zip



i7 Turbo has been updated to support the 6 core Gulftown CPUs.

This should also correctly report Dual 4 core Nehalem Xeon systems. Dual Gulftown support is still in the future.

I don't have any hardware like this to test with so if you have one of the above, post some pics and let me know if there are any problems. Thanks.

[ottoyu34]

I will test it on my 980X with/without OC when possible. Thanks!!

[eva2000]

Thanks for the hard work! Any chance of arranging GUI interface with 4 columns of 4 rows of cores instead of 8 columns of 2 rows of cores ?

[unclewebb]

Any chance of arranging GUI interface with 4 columns of 4 rows of cores instead of 8 columns of 2 rows of cores ?

Probably not. Gulftown data is two groups of 6 threads. If you stick that in a 4x4 grid, then it makes it more difficult to compare the multiplier to the C0% for each thread. Don't worry. The GUI will look more square when I throw another couple of rows of data in there to support the dual Gulftown setups.

[eva2000]

Ah i see.. 8x4 grid - dam dual gulftown does sound nice - well until you actually tally the cost price

[Sam_oslo]

Well. I'm not using turbo, but the readings and layout looks fine on X56xx.

At idle:


EDIT: and one under Prime-load if you need to see what's going on under load.

[acebmxer]

heres a pic of my 930 running with turbo on.



here is unloaded

[kup]

Would it be possible to have the app' show only the number of columns/rows for the CPU in the system instead of loads of blanks?

[unclewebb]

The GT in the i7 Turbo GT title means that this app is designed for the 6 core Gulftown CPUs and the Dual Xeon 8 core Gainestown systems. Most people usually have hyper threading enabled so that will fill up 12 or 16 boxes with lots of numbers.

If you have a 4C/8T CPU then you can use the original i7 Turbo program which is located in the RealTemp download. I'll be updating it shortly for proper QX support but other than that, it works great on the 4C/8T CPUs and has a lot less empty boxes. The 8C/16T Gulftowns aren't that far in the future so I wanted to get prepared for them.

[Sam_oslo]

The GT in the i7 Turbo GT title means that this app is designed for the 6 core Gulftown CPUs and the Dual Xeon 8 core Gainestown systems. Most people usually have hyper threading enabled so that will fill up 12 or 16 boxes with lots of numbers.

If you have a 4C/8T CPU then you can use the original i7 Turbo program which is located in the RealTemp download. I'll be updating it shortly for proper QX support but other than that, it works great on the 4C/8T CPUs and has a lot less empty boxes. The 8C/16T Gulftowns aren't that far in the future so I wanted to get prepared for them.

Good idea, that's not too many. Actually it could have more. 12C/24T for EVGA SR-2 which is roiling out now.

I've just downloaded the final version and it is working fine too, with the exact same readings. The only different I can see is the added CPIID.
Good job with writing code right on the spot without having the HW on hand.

Final ver.:
At Idle:


Edit: A quick Prime-run looks just fine too.

[unclewebb]

Thanks Sam_oslo. I added CPUID so I can easily see what CPU is being used when I see a screen shot.

There's some blank room in the top line. Maybe I will add BCLK or some other data up there to help fill in the blank space.

When fully loaded, using the high performance timers within Intel CPUs results in a deadly accurate look at what the multiplier for each thread is up to as long as other third party monitoring software is not screwing with these timers. At idle there is a slight amount of random variation. Typically less than +/- 0.010. A difference much larger than that is usually a good sign that something is going on inside your CPU that probably shouldn't be.

The programmer of Core Temp is also seeing the light and is considering using this method that is well documented in the November 2008 Intel Turbo White Paper.
http://download.intel.com/design/pro...ots/320354.pdf

[Vandre]

Looking good, unclewebb.

(By chance, the screenshot was taken in the lull between IntelBurnTest runs, thus the strange C0 state percentages)

[unclewebb]

That looks normal between rounds of IBT or LinX / Linpack testing. One core or thread stays at or near full load while the others take a break before the torture begins again.

As long as your board is maintaining the full 30.0 multiplier while fully loaded, everything is good.