I don't necessarely disagree, just wanted to point out that ESRAM isn't completely trade-off free. It's transistor expensive - transistors that especially could be used for other things, like more CUs like in Sonys case...
Exactly. FWIR, ~1.5B dedicated to the 32mb esram.
Cape Verde = 1.5B transistors
I would have thought a smarter design would stick with 1tsram and increase the size six fold. 192mb of scratch pad memory could have yielded something more interesting than what they ended up with. Or MS could have designed the esram to provide enough bandwidth to do something interesting and unique only possible with esram. Or (ideally) dedicate 64mb 1tsram/edram (high bandwidth) and the rest of the transistors to more CU's.
Given AMD's ability to source memory controllers in their gpu's which can support either ddr3 or gddr5, I'd think they could have provided this option to MS as a way out to drop this boat anchor on their design.
Honestly I'm still dumbfounded that the team green-lighted a design which called for 1.5B transistors just to make up for anemic ddr3. Why not 4gb ddr3 + 4gb GDDR5? The whole thing is just a lot of spend for not much performance. Just to avoid GDDR5.
Bottom line, their business decision to dedicate 3gb to non-gaming functions is what lead them into this cluster **** design. From there I'd call it a failure on the design team not to push back against the suits for more performance.
Last edited by a moderator: