Navigate: Advice Beginners BIOS Guide CPUs Links Mainboards Memory Network Storage Video/Sound Cards Contact Forum SiteMap Sponsors WebNews Home	.	.
CPU Intel P4 840 D P4 820 D P4 630 P4 640 P4 650 P4 660 P4 670 AMD Athlon64 3500+ 3700+ 3800+ 4000+ X2-3800+ X2-4200+ X2-4400+ X2-4600+ X2-4800+ 1-Way Opteron Opteron 144 Opteron 146 Opteron 148 Opteron 150 Opteron 152 2-Way Opteron Opteron 240 Opteron 242 Opteron 244 Opteron 246 Opteron 248 Opteron 250 Opteron 252 2-Way Dual Core Opteron Opteron 270 Opteron 275 nVidia GF 7800GT GF 6800GT GF 6600GT ATI R X850 XT PE R X850 XT R X800 XT PE R X800 XT R X800 XL Memory Corsair Crucial Kingston Mushkin OCZ What are you shopping for?

As 3D-application, Expendable is most likely to heavily depend on FPU performance including FPU memory bandwidth, rather than on integer performance including CPU memory bandwidth. The FPU memory bandwidth scores were not affected as badly by the 143 MHz setting as the CPU memory bandwidth and, therefore, one might expect less of a relative performance hit.

At 3:3:3 settings, Expendable "go.exe" would show some erratic behavior in that the frame rates were not consistent from one run to another, particularly at the higher bus speed settings, In addition, the system tended to crash frequently or simply exit the benchmark without finishing. I am, therefore, not including these frame rates.

Similarly, at 2:3:2 settings and 150 MHz using Corsair CAS-2 DIMMs, the system would hang occasionally, whereas, with the same DIMMs, the system would run flawlessly at 2:2:2 (150 MHz!!!) latencies.

Expendable frame rates at 100, 133, 143, 154 and 166 MHz, 2:3:2 latency settings

At 143 MHz, Expendable frame rates are slightly faster than at 133 MHz, consistent with the higher FPU memory bandwidth.

Expendable frame rates at 100, 133, 143, 154 MHz, 2:2:2 latency settings

Remember that at 2:2:2 timing settings, FPU memory bandwidth was identical for the 133 and the 143 MHz memory bus frequency? Expendable frame rates duplicate this result. Note that it was impossible to run at 166 MHz and 2:2:2 settings.

next page:    => conclusion =>