Battlefield 2 - Gulf of Oman, 1024 x 768
CL 3 2T
CL 3 1T
CL 2 1T
While it is tempting to jump to the conclusion that CAS Latency 2 and Command Rate 1T is mostly responsible for these results, that doesn't necessarily be true. Particularly since we're seeing a lower minimum fps and a much higher maximum fps. Under the same load, it looks like changing Command Rate won't do much in this game. But what's more important of all, this game still stutters like hell for about half a minute or so with a 512 MB system. Only when the hard disk stopped trashing around, do we have a somewhat stable frame rate. So, Battlefield 2 can still be ran at high details on a 512 MB system (if you're patient enough).
A much more older, but more stable game, Call of Duty is keeping to the tradition of the game engine it uses - Quake III Team Arena. This engine (and of course most games based on it) is very sensitive to changes in processor clocks, front side bus and memory timings. Here we see the same ting as before: changing Command Rate to 1T alone is enough to boost frame rates.
These results maybe too close to call, but we can see a trend - lower timings and Command Rate does boost performance (slightly). Looks like it might even be handy to boost minimum frame rates as well. But with frame rates that low, you'll definitely can still see stuttering time to time in F.E.A.R. So, it looks like this game also can use the memory upgrade to at least 1 GB.
[Previous Page]
[Go to top]
[Next Page]