Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Running at full speed all the time?
I did this to my q8200 but cannot remember!!
Cheers
What is it with people who try to put off people wanting to do what they want to do! Give the guy a solution not a lecture![]()
Pointless for some, yes, but for others there is a requirement to run a rig at it's full speed 24/7.
There is latency. Takes time to spin up and to poll load requirements.
Car analogy is a rolling start compared to starting on the grid. Starting on the grid produce a slower lap time than the second lap.
PC 24/7 but the required app may be on demand: when you want it to run you want it immediately, and not wait for the speed to ramp up.
The app may only run for milliseconds, rest for seconds and then activate again. It is the rest time which lowers the speed such that the next start will be slow speed and need to ramp up. Leaving it on max speed 24/7 will prevent this startup lag.
but generate un-needed power consumption and temps surely?
PC 24/7 but the required app may be on demand: when you want it to run you want it immediately, and not wait for the speed to ramp up.
The app may only run for milliseconds, rest for seconds and then activate again. It is the rest time which lowers the speed such that the next start will be slow speed and need to ramp up. Leaving it on max speed 24/7 will prevent this startup lag.
I am curious then....
if the CPU runs at 1.6 when not under load, if you fired up CPUZ what speed would be reported ? Would it show as being 3.3ghz or would it just show a snapshot of what it is currently running at.
If you are benchmarking you would want the speed to be fixed at its max rather than starting low and ramping on demand ? e.g I am going to run superpi test, chip is currently tooting along at 1.6, superpi fires up, system goes 'need more power to the engines Scotty !!!!!!', CPU puts pedal to the metal and increases speed to meet demand. Does it fire straight up to 3.3 or what ever speed you clocked or does it just carry on ramping up at a certain rate until process finishes or until it hits max speed and continues process to completion ?
Man I am confused !!!!!
I am curious then....
if the CPU runs at 1.6 when not under load, if you fired up CPUZ what speed would be reported ? Would it show as being 3.3ghz or would it just show a snapshot of what it is currently running at.
If you are benchmarking you would want the speed to be fixed at its max rather than starting low and ramping on demand ? e.g I am going to run superpi test, chip is currently tooting along at 1.6, superpi fires up, system goes 'need more power to the engines Scotty !!!!!!', CPU puts pedal to the metal and increases speed to meet demand. Does it fire straight up to 3.3 or what ever speed you clocked or does it just carry on ramping up at a certain rate until process finishes or until it hits max speed and continues process to completion ?
Man I am confused !!!!!
would show as 1.6GHz if your idle or using little resources, if your running something intensive in the background it will show as 3.3GHz.
there is no reason to turn speedstep off, unless you are overclocking. even then it is suggested you leave it on some boards.
its basically saving you energy when you dont need to use the cpu. it takes less than the blink of an eye to go from 1.6 to 3.3, so it would not affect any applications or benchmarks. it switches instantly.