RUMOR: Microsoft will downclock the GPU on Xbox One
A thread over at NeoGAF that has been up and running now for about 24 hours claims that Microsoft is having issues with the eSRAM yield on the Xbox One, and that this has resulted in Microsoft needing to downclock the GPU.
While I’ll be the first to admit that I can barely make sense of all of the commotion on the thread, there are a couple of explanations that I can understand to some extent, specifically:
(originally posted by thuway on NeoGAF)
For everyone asking- this information is all pretty recent. Around the PlayStation Meeting the Xbox One was way behind (OS + hardware). Engineers were scrambling to get things sorted out.
It turns out, they didn’t sort it out. The OS you saw was a complete and total lie. The current plan is to get the yields up, lower the clock rate, and to have enough units out for a sell out in the Fall.
For those asking how this affects performance- to be perfectly frank; it is nothing turning down features won’t solve. The mass market will never notice a difference between 1080p and 900p; neither will they care about dynamic shadows / global illumination / or tesselation. Go to your PC – and turn shadows from Ultra to medium, disable tesselation, and lower the resolution to 900p; and you’ll find games run totally fine.
Microsoft is purely behind and it’s now time to make drastic decisions. I don’t think any one is happy about the lower clocks, but no one is depressed about it either. The Xbox One is an all-in-on device; and that’s how it will be marketed.
I really found this post by eloj on GiantBomb incredibly informative, even though it is only someone guessing:
There’s a rumor that Microsoft are having problems with the XBone. There’s been rumors before that they’re behind on software, but these latest rumors pertain specifically to the hardware and the combination of eSRAM and GPU. The rumor is saying that they’re having yield problems, specifically related to the eSRAM.
I will now go on and speculate widely. You have been warned.
It is claimed that the XBone APU is a one-die CPU+GPU+eSRAM solution, meaning that it’s very large (~410mm^2). The only thing MS really said at their reveal was “5 billion transistors”. This is interesting, and some correctly pointed out that it probably meant they couldn’t compete with the PS4 on specs, because if they could, they’d be more specific.
The primary risk with large dies of course are low yields, resulting in higher costs to get enough dies that meet your specification. Now, Microsoft was not building a gaming machine first. They wanted to load a familiar operating system on there. They wanted more focus on applications that historically have not been heavily optimized for one platform. A relatively fat OS, and applications from developers who are not used to the scant resources typically awarded a gaming console, leads to one design conclusion; “we need lots of memory!”
So they design for 8GB, from the start. Again, they put applications (and cost) above gaming, and go for a well known, cheap, plentiful technology in DDR3. Back then 8GB of GDDR5 would look too expensive, almost insane, and DDR4 wasn’t on the immediate horizon.
To compensate the gaming side, they now need some fast RAM, hence 32MB eSRAM on-die. The XBone eSRAM is said to be a 6T type, meaning that each bit requires six transistors. 32MB gives us 32*1024*1024*8 bits times six equals 1,610,612,736 transistors. That’s 1.6 billion, a huge chunk out of the total 5 billion!
They do desperately need this very fast cache-like memory to fix the fact that they’re using “slow” DDR3, which they settled on because they wanted to have a lot of it, for apps — not games.
Recap: Decision to not focus on games results in design for a lot of memory, which is “slow” for cost reasons, which is compensated with cache. Result: Large die, with large percentage dedicated to what turns out to be a possible problematic memory to fab. Because the cache use so much die, they have to scale down on GPU.
They’re reportedly roughly 2 billion transistors larger than the APU used by Sony in the PS4, which means worse thermals, which means lower clocks. The rumor is saying that the yields on this APU, due to the eSRAM, is so low, that they may have to cut the clocks on the eSRAM+GPU even further than what they’ve previously communicated to developers under NDA. This would make the XBone even weaker on the GPU side vs the PS4, which was already believed to be quite a bit stronger.
MS probably thought for the longest time, like PS4 devs did, that the PS4 would only have 4GB of GDDR5. Microsoft could work with that, they’d have the fast cache (which no doubt can be awesome when properly used — I’m a huge cache nerd) and more total memory. They designed their system around being the platform with More Memory.
Cerny meanwhile had bet on GDDR5, and his bet has been that availability will increase and cost decrease at such a pace, that even back when they were first thinking about the PS4 and 2GB seemed like ample amounts, as time went on 4GB became viable.. and then at the last second… tick. Out of nowhere Sony steps up on stage and announce that they’ll be using 8GB of GDDR5, twice the amount insiders thought for sure.
And they probably did this to match Microsoft, which has now lost their one advantage in specification. They on their parts are left having to pay the price of designing for apps before games, and that price just went up if this rumor is true.
Now, this is all speculative right now. With E3 coming next week, we may be able to piece together some additional information based on Microsoft’s response to the tech spec questions regarding the Xbox One. If there’s dancing, there’s almost certainly accuracy in these rumors that Microsoft will want to avoid discussing.