The original Splinter Cell pretty much paints the same picture. In a way that's good - even users with value memory can still push their memory to achieve slightly higher frame rates without changing their memory timings. But in all honesty, you really don't have to, since frame rates are already high enough. even with the default timings we've used (3-3-3-8-2T).
No significant or even noticeable differences here. The results are really too close to call which configuration has the higher frame rates. Overall, using CAS Latency 2 with Command Rate 1T seems to give us the highest frame rates, but again, it's really to close to call.
Now, we've seen the performance numbers from games with memory footprints still within 512 MB or slightly above it. Although CAS Latency 2 and Command Rate 1T theoretically should give us the higher frame rates, it's not always so. Sometimes, changing Command Rate from 2T to 1T is enough. This is most probably because we're using an Athlon 64, a processor with an on-die memory controller. Integrating the memory controller into the processor save enough cycles, that changing latencies will not give us that big of a boost. So, what about load times?
| In msec | In percent | ||||
| CL 3 2T | CL 3 1T | CL 2 1T | CL 3 2T to CL 3 1T | CL 3 2T to CL 2 1T | |
| Brothers in Arms | 2270.33 | 1853 | 2215 | -18.38% | -2.44% |
| DS | 4221.33 | 3237 | 3955.67 | -23.32% | -6.29% |
| DS II | 8855.33 | 8776.33 | 8611 | -0.89% | -2.76% |
| F1 | 19409.67 | 18072.33 | 19086.33 | -6.89% | -1.67% |
| FSW | 14496 | 14219 | 14034.33 | -1.91% | -3.18% |
| HW2 | 5183.67 | 6147.33 | 4839.33 | 18.59% | -6.64% |
| Lock On | 39541.67 | 39051.33 | 39924.67 | -1.24% | 0.97% |
| N2003 | 3460 | 3195.67 | 3394 | -7.64% | -1.91% |
| RBR | 6137.33 | 5044 | 5190 | -17.81% | -15.44% |
| SC | 1671 | 1044.67 | 1090.67 | -37.48% | -34.73% |
| SW:KOTOR | 2754.33 | 2320.67 | 2230.33 | -15.74% | -19.02% |
| Average |
-10.25% | -8.46% |
Since time is the metric here, lower numbers are better and negative percentage values means less time loading. Overall, we still see the most improvement just by changing Command Rate from 2T to 1T (-10.25 %). On a game-per-game basis, the improvement can be less or a lot more - up to around 15 to 20 %. Of course, that might just be jittery fingers. In actually, the games with the most decrease in loading times are already pretty fast - around 5 seconds or less.
[Previous Page]
[Go to top]
[Next Page]