Just curious, but what are the advantages of using esram instead of just using edram like for the Xbox 360? It will probably take a lot less amount of transistors just putting edram in there and therefore lowering costs.
People are very fixated on the transistor count numbers but they don't dictate costs alone, different designs allow for different transistor density. SRAM tends to be the densest, can be a lot denser than typical logic. 32MB eSRAM on TSMC 28nm is big but not necessarily gigantic (could be ~50mm^2 or even smaller) and its cost will not be nearly as high as its transistor count represents.
Why MS is bragging transistor counts at all is a mystery to me, they must think big numbers will impress people.. looks like it's actually having the opposite effect, now people think it'll be big and expensive..
eDRAM can still be substantially denser than eSRAM on a similar node - I think something like 3x in current times. However, there are a lot of disadvantages too:
- Not everyone offers it and the ones offering modern iterations of it seem to be dwindling more and more. AFAIK TSMC doesn't offer it at 28nm right now, according to a chart I've seen anyway. This is a problem today but poses an even bigger potential risk for years down the road. While being able to benefit from shrinking eSRAM is pretty much a given. And if you can only get it a node behind then you lose a lot of density advantage you would have gotten in the first place.
- It adds extra manufacturing steps/needs more layers AFAIK so it's more expensive. Either you eat the cost of making the whole die more expensive - bad choice if it's just for memory that's just a relatively small fraction of the total die cost like it'd be here - or you put it on another die. The latter is what MS always did on XBox 360.. eventually even the CPU and GPU were integrated onto the same die but the eDRAM never was. But having a separate die adds various cost overheads too.
- eDRAM is less power efficient so eats a bit more out of the TDP budget
It's really all down to the size. For example if we were talking something like 2MB no one would argue that you should use eDRAM over eSRAM (unless it's IBM pitching a CPU for Nintendo.. I still have no idea how that design got approved!). If it was something like 128MB MS would have no realistic choice but to use eDRAM. 32MB is on the upper end of what they can reasonably use eSRAM with before it becomes a huge liability; it's possible that the choice for eSRAM dictated the 32MB size, but 32MB could be sufficient.