Crysis Warhead
We measured Warhead performance using the FRAPS frame-rate recording tool and playing over the same 60-second section of the game five times on each processor. This method has the advantage of simulating real gameplay quite closely, but it comes at the expense of precise repeatability. We believe five sample sessions are sufficient to get reasonably consistent results. In addition to average frame rates, we've included the low frame rates, because those tend to reflect the user experience in performance-critical situations. In order to diminish the effect of outliers, we've reported the median of the five low frame rates we encountered.

We tested at relatively modest graphics settings, 1024x768 resolution with the game's "Mainstream" quality settings, because we didn't want our graphics card to be the performance-limiting factor. This is, after all, a CPU test.

Far Cry 2
After playing around with Far Cry 2, I decided to test it a little bit differently by recording frame rates during the jeep ride sequence at the very beginning of the game. I found that frame rates during this sequence were generally similar to those when running around elsewhere in the game, and after all, playing Far Cry 2 involves quite a bit of driving around. Since this sequence was repeatable, I just captured results from three 90-second sessions.

Again, I didn't want the graphics card to be our primary performance constraint, so although I tested at fairly high visual quality levels, I used a relatively low 1024x768 display resolution and DirectX 9.

Performance in both of these games is also affected by the slower cache in the retail chip. We're not talking about the sort of delta you're likely to feel by the seat of your pants as you play, but the effect is real, regardless.