FantomX
GPU Guru
- Učlanjen(a)
- 01.04.2009.
- Poruka
- 4.849
- Rezultat reagovanja
- 3
Moja konfiguracija
CPU & cooler:
iMac 24"
Other:
¿ʞɔnɟ əɥʇ ʇɐɥʍ
i7 Turbo 6.8
http://www.fileden.com/files/2008/3/3/1794507/Turbo.zip
This tool is designed to test for Turbo throttling which can occur on some X58 motherboards when overclocking at high load levels as you approach the TDP limit of your CPU. Most motherboards allow you to turn off TDP based throttling in the bios but not all of them do and not all bios versions work correctly. If you are using the Turbo feature of a Core i7 processor, it's a good idea to make sure that your motherboard properly supports this feature.
The multiplier for a Core i7-920 is typically 20.0 and if Turbo mode is enabled, you get a +1.0 boost for a total of 21.0. With a 920, even if a bios lets you select a multiplier of 21.0 directly, internally it is still using the Turbo feature of your CPU. Turbo throttling can occur at high loads where the +1.0 Turbo boost will start to rapidly cycle on and off hundreds of times a second as you approach the TDP limit. When this first starts to happen, not all software is able to detect that your multiplier is intermittently dropping down to 20.0. Software that only samples your multiplier once per second might completely miss this problem.
There are two ways to read the current multiplier from a CPU. The typical way is to read a model specific register (MSR) within the CPU. This gives you a snapshot of what the multiplier is at that particular instant. If software only reads this value once per second then it can miss what's really going on.
The second way that Intel recommends is to compare two high performance internal timers within their CPU and then to use that information to calculate what the multiplier is.
The Intel Turbo White Paper outlines this method:
http://download.intel.com/design/pro...ots/320354.pdf
The advantage of the calculated multiplier is that during a one second sample period, it can be used to very accurately calculate the average multiplier during that interval. This method tends to be extremely precise when the CPU is fully loaded.
Unfortunately, at idle, the calculated multiplier has a tendency to wander depending on how your motherboard and C-States are set up. If your Windows power settings and C-State settings in the bios are in agreement, the amount of wander will be minimal.
Edit: If you are not getting consistent results from i7 Turbo at full load then try turning off any additional monitoring programs that might be interfering with the Calculated Multiplier. Programs that sample a lot of motherboard voltages like HW Monitor and Everest have been known to cause problems on some motherboards when testing with i7 Turbo.
Edit #2: RealTemp 3.00 can also cause issues with i7 Turbo results when the internal timers overflow and wrap around back to zero. When you are testing, I recommend that you update to RealTemp 3.30 which handles timer wrap around better.
http://www.fileden.com/files/2008/3/...alTempBeta.zip
i7 Turbo displays both the calculated multiplier as well as the traditional MSR based multiplier. On a Core i7-920 at full load with the Turbo fully engaged, both of these values should be firmly locked on 21.000. At full load, if the calculated multiplier starts to drop, that is an excellent warning sign that Turbo throttling is starting to occur.
For the MSR based multi, I am sampling it once per thread per second to improve its accuracy. If you have hyper threading enabled and it samples 7 of your threads at a multiplier of 21.0 but the eighth thread has dropped down to 20.0 by the time it gets sampled, then it will display 20.875 showing that the Turbo was mostly enabled during that sample period. On Core i7, the multiplier is a whole number and at any instant in time it will be the same for each thread but with multiple samples during a one second interval, we should see better results from the MSR based multiplier.
For severe cases, both multipliers will drop down to 20.000 and clearly show Turbo throttling in progress. Other times, maybe the calculated multiplier will give you an earlier warning of this problem.
Both multipliers and the Average CPU Load can be logged for further analysis. The load of each thread is displayed in the GUI. While testing, you can easily add a note directly to your log file like, "Started Prime95" or "Started LinX." You can use either the Enter key or click on the Add Log Note feature.
The EIST section reads this information directly from the CPU. If it disagrees with what you set in the bios then that's usually a sign that your bios is not turning off this feature.
The Load Filter option for the Calculated Multiplier lets you weed out any bad data from the Min and Max areas that can occur with this method when the CPU is lightly loaded. If you set it to 0% then all calculated multiplier data will show up in the Min/Max area. If you use 90% then data will only be added to the Min/Max area if the CPU load is 90% or greater. I added this so if you're gaming, light load between rounds or when going back to the desktop won't interfere with your results.