from what i've read the l3 cache is a spilloff cache, and the memory controller feeds the l2, so the CPU isn't held up by the l3 latency (which would result in a pretty bad performance hit). cache latency (seconds) = latency (clocks) * duration of a clock (seconds)
and duration of a clock (seconds) = 1/frequency (to get seconds per cycle instead of cycles per second)
so latency (clocks) = latency (seconds) / (1/frequency) = latency (seconds) * frequency
using 23ns @ 2ghz, 19ns @ 2.5ghz:
(23*10^-9)*(2*10^9) = 46 clocks
(19*10^-9)*(2.5*10^9) = 47.5 clocks
latency in clockcycles increased going to 2.5ghz, there's no way you'll get better than linear scaling... that was a myth



Reply With Quote
Bookmarks