2 ms·
> Actually it's super easy, barely an inconvenience Wow wow wow. Your references are TIGHT. ---------- The main RAM / CPU issue is latency: it takes over 10
by dragontamer 7y ago
> Actually it's super easy, barely an inconvenience
Wow wow wow.
Your references are TIGHT.
----------
The main RAM / CPU issue is latency: it takes over 100-clock cycles to communicate with DDR4, which a CPU could process ~400 instructions if they were lined up just right (modern CPUs are super-scalar, executing multiple instructions per clock tick).
Only once you have sizable caches + data locality will you solve the latency problem.
Without locality, I'm not sure if the latency problem can be solved at all. Fortunately, many problems have an element of locality that can be taken advantage of.
- fulafel 7y agoMemory controllers do prefetching for streaming memory accesses. Yes a lot of workloads are more latency sensitive, but it's not like sequential streaming memory accesses are hard given the prefetching. (Anyone have pointers to current EPYC vs Xeon STREAM results?)