Page 2:More Memory, Please
Page 3:A Pair Of 64-Bit Gaming Case Studies
Page 4:Tom's Hardware Sits Down With Chuck Walbourn
Page 5:Tell Me More About Hacking LAA
Page 6:Setting Up An In-Depth Look At Performance
Page 7:Crysis: Testing Native 64-Bit Performance
Page 8:World In Conflict: Adding Frame Rate Minimums
Page 9:Far Cry 2
Page 10:Grand Theft Auto 4
Page 11:Left 4 Dead
Page 12:3DMark Vantage
Crysis: Testing Native 64-Bit Performance
Yes, we know that this horse is getting long in the tooth. But Crysis still presents a challenge to the fastest systems available. And it is one of the only metrics available with a native 64-bit executable to test against a 32-bit version.
For all intents and purposes, there is very little difference in performance here, save the 32-bit version of the game running a hair faster at 1920x1200. Otherwise, the scores are remarkably close.
We really shouldn’t be surprised here. As Microsoft’s Walbourn mentioned, there weren’t really any specific optimizations made to improve performance in 64-bit. More interesting is the fact that moving from 3 GB of memory to 6 GB makes absolutely no difference in frame rate.
Perhaps RAM has more of an effect on frame rate minimums. Let’s check that out using World in Conflict next.
- More Memory, Please
- A Pair Of 64-Bit Gaming Case Studies
- Tom's Hardware Sits Down With Chuck Walbourn
- Tell Me More About Hacking LAA
- Setting Up An In-Depth Look At Performance
- Crysis: Testing Native 64-Bit Performance
- World In Conflict: Adding Frame Rate Minimums
- Far Cry 2
- Grand Theft Auto 4
- Left 4 Dead
- 3DMark Vantage