2 ms·
It's important to note that "twice the speed" refers to transfer speed, not latency or cycle time. Modern DRAM technology has capped out at a cycle time of abo
by ajross 14y ago
It's important to note that "twice the speed" refers to transfer speed, not latency or cycle time. Modern DRAM technology has capped out at a cycle time of about 30MHz, and isn't going to change much in the future. That time is limited by the time required to precharge the bit lines to a voltage accurate enough to measure the stored values against. These are big wires going across the whole chip by definition, so they don't see improvements due to process shrinkage. On a modern DDR3-1600 part, there are 1.6G potential transfers per second, but a full random access cycle requires about 60 of these (10-10-10-30 timings are typical). The time taken to issue the command is 2 clocks, and the time taken to read the data is 4. The rest is just idle waiting. So even "infinitely clocked" dram would be only about 10% faster in the worst case.
- codex 14y agoIs this 30Mhz value per chip, or per memory channel? Would it be possible to increase total random access throughput by adding more chips to a channel and pipelining more requests?
- Tuna-Fish 14y agoIt's per memory cell. And that's what all modern memory does. Ignoring chop (afaik, no modern widely used memory controller makes use of it), the smallest request you can make from a 64-bit DDR3 stick is 64 bytes. All those 512 bits are accessed in parallel, and when done, sent over the memory bus over 8 bus transfers. While the controller is waiting for those bits to become available, you can issue commands to different banks within the same chip. (And in fact must do so to get anywhere close to the nominal bandwidth). Modern memory controllers interleave requests both between banks of the same chip and between different chips on the same channel.
- ajross 14y agoIt's per "bank". Chips often are partitioned into multiple banks, each with its own row/column array. This gives some parallelism, because an access to one bank won't invalidate the already-loaded row in the others (reads of bits in the same row as the previous one are faster because they are stored/cached in digital logic -- this is why sequential access to DRAM is faster than random acccess). Obviously the width of the DRAM bus itself is a parallelism design: fundamentally DRAM is always "one bit wide", you get wider busses by using multiple devices and feeding them the same commands. And you can get even more parallelism by using more than one DRAM channel. Intel Desktop CPUs have 2x 64 bit channels, the LGA2011 server parts have 4x64, Apple's new A6 made news this week by moving to a 2x32 bit design. But note that those are all bandwidth improvements. They don't do anything to the time it takes to get a bit out of an idle DRAM part. DRAM latency is largely fixed in the modern world, until we find a different way of storing bits.
- tisme 14y agoOr switch to more expensive but faster SRAM.
- darkstalker 14y agoSo, for best performance look at the lowest latency and ignore the clock speed?
- ajross 14y agoSort of, but true latency doesn't change much across devices. So really clock speed is your only tunable. It's just that it doesn't make much difference in practice. But if you're an overclocker looking to squeeze out an extra 3%, it's an option.