- Joined
- Mar 21, 2021
- Messages
- 5,396 (3.70/day)
- Location
- Colorado, U.S.A.
System Name | CyberPowerPC ET8070 |
---|---|
Processor | Intel Core i5-10400F |
Motherboard | Gigabyte B460M DS3H AC-Y1 |
Memory | 2 x Crucial Ballistix 8GB DDR4-3000 |
Video Card(s) | MSI Nvidia GeForce GTX 1660 Super |
Storage | Boot: Intel OPTANE SSD P1600X Series 118GB M.2 PCIE |
Display(s) | Dell P2416D (2560 x 1440) |
Power Supply | EVGA 500W1 (modified to have two bridge rectifiers) |
Software | Windows 11 Home |
Of course, slower memory is NOT better; I did not mean to imply anything of the sort.
What I meant is that CAS latency only looks like it is getting worse with speed, since it is in clock cycles. So, it will only look like it is getting better if one runs the memory slower, which would be a crazy thing to do, although technically the number would get less.
Put another way, if the CAS number doubles with doubling speed, the CAS latency has stayed the same, not got worse. One could see that with the data I gave for my DDR3 RAM
Running at 381.0 MHz would improve the CAS# but not the real CAS Latency (which is 13nS in both cases)
So, if I had RAM that could run at double 761.9 MHz, I should not view a CAS# of 20 as a drop in CAS performance.
What I meant is that CAS latency only looks like it is getting worse with speed, since it is in clock cycles. So, it will only look like it is getting better if one runs the memory slower, which would be a crazy thing to do, although technically the number would get less.
Put another way, if the CAS number doubles with doubling speed, the CAS latency has stayed the same, not got worse. One could see that with the data I gave for my DDR3 RAM
Frequency | CAS# Latency |
381.0 MHz | 5 |
761.9 MHz | 10 |
Running at 381.0 MHz would improve the CAS# but not the real CAS Latency (which is 13nS in both cases)
So, if I had RAM that could run at double 761.9 MHz, I should not view a CAS# of 20 as a drop in CAS performance.
Last edited: