2 ms·
Oh, a note: "Latency" is a bit ambiguous because I don't really know how the sisoftware code works. If they measured latency by performing one operation, then p
by dragontamer 9y ago
Oh, a note: "Latency" is a bit ambiguous because I don't really know how the sisoftware code works. If they measured latency by performing one operation, then perhaps RL + tRC (15+7.5 nanoseconds) would be closer to the expected performance of the RLDRAM3.
If they measure latency by randomly jumping around Ryzen's L3 memory and determining the delay, then RLDRAM3's performance would almost never stall and you effectively can get an answer on every clock cycle (~1ns), with a worst-case performance of waiting tRC if you visit the same memory bank (7.5ns). That's why I focused on tRC last post.
Thinking about it now however, maybe the 20ns figure for RLDRAM3 is a better comparison against Ryzen's measured 40ns L3 latency. It really depends on how SiSoftware's benchmark is coded.
In any case, its clear that RLDRAM3 has incredibly good latency metrics, rivaling that of Ryzen's L3 cache. Expected 22.5-ns of realistic latency compared to 40ns measured means RLDRAM3 is still way faster than Ryzen.
Plus, you know, the ability to hold a 9MB data-set or larger. An ASIC would be able to chain up as many RLDRAM3 chips as they have pins, so you can probably hold upto 640MB or so (assuming you have enough pins for 10x RLDRAM3 chips)