I can report no disappointment. One of the sticks was faulty, so I cannot usefully report bandwidth, but these 2666 sticks will happily do DDR4-2933 @ 1.35v 16-15-15-36-50 by simply keying in the values in the BIOS. I haven’t changed anything else from stock.
I did try CAS 14, but it won’t POST. Internet says that Threadripper rounds odd numbered CAS up to even in any case, so that report of CAS 15 working I mentioned last post he was probably at CAS 16 and didn’t realise.
2933 @ CAS 16 = 10.9 ns. My previous GSkill RAM was 3200 @ 16-18-18-38-56 = 10 ns. Benchmarking the difference in Windows, this overclocked Samsung RAM is now exactly on par with default configuration Threadripper v2 @ 71.2 ns main memory latency, whereas the previous faster GSkill stuff benchmarked at 67.7 ns, which is a 5.2% increase in latency from the CPU.
How much of that is due to the main memory being slower, or simply the Threadripper’s internal fabric running 9% slower, I cannot say. I would say that the non-CAS timings are much tighter for the Samsung memory, so maybe that explains why the latency increase from the CPU is half as bad as the internal fabric and RAM would suggest.
Anyway, all in all everything seems to be working fine with this 128Gb temporarily minus 16Gb setup, and the ECC is operating correctly according to Windows (no indication in the BIOS though). Just need the defective stick to be replaced, and I’ll be able to tell you about effects on memory bandwidth.
|Go to previous entry||Go to next entry||Go back to the archive index||Go back to the latest entries|