AMD tended to increase memory latency in tandem with increases in the OoO and latency-hiding capabilities of the cores, with varying levels of success.
Jaguar's resources are more limited, which means it shouldn't be expected to compensate for the same kind of latencies that Bulldozer or Trinity are expected to deal with.
The cycle numbers for Durango's L2 to L2 cache hits point to a memory pipeline that, is likely at least somewhat longer latency than Trinity's, without knowing if the remote snoop is additive to main memory latency.
It may be that the much lower clocks are what AMD is counting on to help mitigate the IPC losses due to trips to memory.
As for the comment concerning how AMD arbitrates under load: I haven't run across a review that runs a cache/mem latency benchmark while the GPU is also running at speed. The latency benchmarks for APUs tend to measure CPU memory latency when the GPU isn't fighting for access, and they are mediocre.
Jaguar's resources are more limited, which means it shouldn't be expected to compensate for the same kind of latencies that Bulldozer or Trinity are expected to deal with.
The cycle numbers for Durango's L2 to L2 cache hits point to a memory pipeline that, is likely at least somewhat longer latency than Trinity's, without knowing if the remote snoop is additive to main memory latency.
It may be that the much lower clocks are what AMD is counting on to help mitigate the IPC losses due to trips to memory.
As for the comment concerning how AMD arbitrates under load: I haven't run across a review that runs a cache/mem latency benchmark while the GPU is also running at speed. The latency benchmarks for APUs tend to measure CPU memory latency when the GPU isn't fighting for access, and they are mediocre.
Last edited by a moderator: