Jawed
Legend
This article is quite nice:
AMD hinted at possible further use of Infinity Cache | Diit.cz
and it seems to be written by someone we know quite well around here! (Translate to English works pretty well on this page.)
So the article predates Navi 22 and 23, but the table of hitrates for capacities at various resolutions is a useful reference I think (constructed by no-X rather than quoting AMD, I believe).
The 32MB that we actually got with Navi 23 is listed in the table at a 55% hitrate, with an implied equivalence of 497GB/s.
Assuming Navi 33 also targets 1080p, I have to wonder whether Infinity Cache would be smaller than expected, e.g. 64MB. From the table that gives a 72% hitrate with 993GB/s equivalence. 72% hitrate is very similar to Navi 21 at 1440p, 74%.
A 1080p render target is genuinely going to be around one-quarter of the size of a 4K render target in the worst case (high-complexity deferred rendering with many G-buffer attributes). Additionally, with only 64 ROPs, the demand for bandwidth is actually halved, before taking account of any clock increases seen with Navi 3x.
So it seems like 64MB of Infinity Cache would be "just right" for 1080p at 2x 6600XT performance.
That would save another 64mm² in Navi 21, taking us to (520-128)/1.15 = 340mm².
AMD hinted at possible further use of Infinity Cache | Diit.cz
and it seems to be written by someone we know quite well around here! (Translate to English works pretty well on this page.)
So the article predates Navi 22 and 23, but the table of hitrates for capacities at various resolutions is a useful reference I think (constructed by no-X rather than quoting AMD, I believe).
The 32MB that we actually got with Navi 23 is listed in the table at a 55% hitrate, with an implied equivalence of 497GB/s.
Assuming Navi 33 also targets 1080p, I have to wonder whether Infinity Cache would be smaller than expected, e.g. 64MB. From the table that gives a 72% hitrate with 993GB/s equivalence. 72% hitrate is very similar to Navi 21 at 1440p, 74%.
A 1080p render target is genuinely going to be around one-quarter of the size of a 4K render target in the worst case (high-complexity deferred rendering with many G-buffer attributes). Additionally, with only 64 ROPs, the demand for bandwidth is actually halved, before taking account of any clock increases seen with Navi 3x.
So it seems like 64MB of Infinity Cache would be "just right" for 1080p at 2x 6600XT performance.
That would save another 64mm² in Navi 21, taking us to (520-128)/1.15 = 340mm².