Testing Methodology
Comparison Memory |
||||
|---|---|---|---|---|
| Corsair Vengeance LPX 3,200 |
Corsair Vengeance LPX 2,133
|
|||
| Model | CMK16GX4M4B3200C16 |
CMK16GX4M4A2133C13 |
||
| Capacity | 16GB (4x4GB) |
8GB (2x4GB) |
||
| Speed | 3,200MHz |
2,133MHz |
||
| Timings | 16-18-18-36-2T |
15-15-15-35-2T |
||
| Voltage | 1.35V |
1.20V |
||
| Price* | £140 |
£110 |
||
| Cost per GB* | £8.75 |
£6.87 |
||
| *Approximate, correct at time of writing | ||||
Test Platform |
||||
| CPU | Intel Core i7-6700K | |||
| Motherboard | Asus Z170-K (0323 BIOS) | |||
| Storage Device | SK hynix Canvas SC300 512GB | |||
| Graphics Card | Nvidia GeForce GTX 980 4GB | |||
| Power Supply | Corsair AX760i | |||
| Operating System | Windows 10 64-bit | |||
Benchmarks |
||||
| HEXUS.PiFast | Our number-crunching benchmark stresses a single core by calculating Pi to 10m places | |||
| CINEBENCH R15 | Using Cinebench's multi-CPU render, this cross-platform benchmark stresses all cores | |||
| HandBrake 0.10.2 | Free-to-use video encoder that stresses all CPU cores (64-bit) | |||
| wPrime 2.1.0 | Another number-crunching benchmark that stresses all available CPU cores/threads | |||
| AIDA64 v5.30.3500 | Memory analysis tool supporting Skylake CPUs | |||
| 3DMark | DX11, Fire Strike default test | |||
| Grand Theft Auto V | DX11, 1,920x1,080, very high quality (GTX 980) and normal quality (IGP) | |||
| Middle-earth: Shadow of Mordor | DX11, 1,920x1,080, ultra quality (GTX 980) and low quality (IGP) | |||
| Total War: Rome II | DX11, 1,920x1,080, extreme quality (GTX 980) and medium quality (IGP) | |||
Notes
The simplest way to examine the effect of memory speed and timings is to look at the relative performance of the 2,133MHz and 3,200MHz kits.
Overclocking
We've chosen three arbitrary speeds and timings in order to evaluate the overclocking potential of the Corsair modules. Voltage was increased to 1.45V.
| 3,333MHz (16-18-18-36-2T) |
3,400MHz (16-18-18-36-2T) |
3,400MHz (17-17-17-39-2T) |
|
|---|---|---|---|
| Corsair @ 1.45V |
 |
 |
|
Jumping up to 3,333MHz is easy at the specified timings but going any higher is problematic. The precise reason for this is unknown - it could be due to a memory ceiling or inability of the integrated memory controller on the Core i7-6700K to service higher speeds.