As mentioned on our testing methodology page, all FPS are tracked using FRAPS 2.82 except for Prey, which is the only title here to use a timedemo. There are two reasons for this. First, the game limits the framerate to 60FPS, while the timedemo does not. The downside is that at that point, it’s more CPU dependant than GPU dependant. In the case of this review though, that’s a good thing.
All games are run at 1600×1200 with mid-level AA and AF. The exception is Supreme Commander which is run at 1920×1200 and completely maxed out settings. An 8800GTX card is used to remove as much of a bottleneck as possible, so that any increase of Avg FPS will be solely because of the faster processor. Note that Half-Life 2, Stalker, NFS: Carbon and SupCom are completely manual play-throughs, so variances in each run could cause a CPU achieve a lower score.
Half-Life 2 is a heavily CPU-bound game, although the game doesn’t take advantage of dual core or higher processors. With 160FPS as is though, do we really need it to?
As evidenced by comparing the E6600 to Q6600, STALKER is single-threaded, but improved by faster CPU frequencies. Compared to our 2.4GHz processors, the QX6850 gave us an FPS-boost of 32%.
As much as I love the Need for Speed series, there’s no denying that they are far more GPU dependant than CPU dependant, clearly obvious by the graph above. If you have a good CPU, your only worry will be your GPU.
Being a timedemo, the highest FPS will automatically go to the fastest processor. It gives us a general idea of what benefits to expect from moving up to a faster frequency, however. As mentioned on our testing methodology page, SupCom is run with maxed out graphics (8xAA) at 1920×1200 to push our GPU as much as possible and also to see if more than one CPU core will be used.
The level chosen is Finn’s Revenge, run off a saved-game that we previously made which begins us late into the mission. For this run, we create a few extra killing machines in addition to what we already have, and command them to go destroy the enemy. The entire process takes about eight minutes, and you can see an example of how much action and bots are on the screen on our testing methodology page.
At any given time, not more than 1.5 cores were used, and that was only random peaks. I am not sure what it would take to have even more usage, but the fact is, if you have at least a dual core processor, you can expect good results. By comparison, I disabled one of the cores on the E6600 processor and received an average of 37FPS.
With all of our benchmarks out of the way, let’s continue on into our power consumption tests and also temperatures.