OCZ EL DDR PC-3500 Gold GX Dual Channel
Performance:
The system used to test the OCZ EL DDR PC-3500 Gold GX was nForce4 based and contained the following components:
Hardware Components | |
Processor: | AMD Athlon 64 3200+ (Venice) |
Motherboard: | DFI UT nF4 Ultra-D |
Graphics Card: | eVGA 6800GT PCI-Express |
Hard Drives: | 120GB Maxtor, 160GB Maxtor SATA |
Optical Drives: | NEC ND-3540A |
Add-On Devices: | Chaintech AV-710 |
Cooling: | Thermalright XP-90 |
Power Supply: | Cooler Master Real Power 450 |
Software Components | |
Operating System: | FedoraCore4 |
Linux Kernel: | 2.6.12-1.1398 |
GCC (GNU Compiler): | 4.0.0 |
Graphics Driver: | NVIDIA 1.0-7667 |
Xorg 6.8.2 |
The motherboard we have chosen for today’s tests is none other than the DFI Ultra-D. This choice was made primarily because of its unparalleled overclocking capabilities and also for the wide selection of memory voltages up to 4V. Not that you ever want to run 4V through your memory, but up to around 3.6V is still very useful for UTT-BH5 chips. The board was flashed with Merlin's 510-2f (Tune Up) w/ Hellfire's 3.16 to help in pushing these modules to the max. After many hours of low voltage burn-in and testing, the maximum speed we reached was a blazing 261MHz at 2-2-2-8 latencies with 3.6V (again don’t do this at home unless you want to void your warranty, because OCZ’s voltage warranty only covers up to 3.1V + 5%). At these kinds of voltages, the memory gets extremely hot, so we removed the heatspreaders and aimed an extra 120mm fan directly on the modules. This is extremely important if you are going to run your memory anywhere above 3V. As for benchmarks, we used Doom 3 (1.3.1302), LAME (3.96.1), time make, RAMspeed (2.3.1), and SpecViewPerf (v8.1) for some real world performance tests. The comparison RAM was the PQI Turbo TCCD’s running at 200MHz 2-2-2-8. The OCZ GX modules were run at PC3200 instead of PC3500. This is due to the fact that the modules that we are testing are the GX and not the PQI, so we did not wish to overclock the PQI Turbos. Now let’s skip to the benchmarking action.