Memory Subsystem

With the same underlying CPU and GPU architectures, porting games between the two should be much easier than ever before. Making the situation even better is the fact that both systems ship with 8GB of total system memory and Blu-ray disc support. Game developers can look forward to the same amount of storage per disc, and relatively similar amounts of storage in main memory. That’s the good news.

The bad news is the two wildly different approaches to memory subsystems. Sony’s approach with the PS4 SoC was to use a 256-bit wide GDDR5 memory interface running somewhere around a 5.5GHz datarate, delivering peak memory bandwidth of 176GB/s. That’s roughly the amount of memory bandwidth we’ve come to expect from a $300 GPU, and great news for the console.

Xbox One Motherboard, courtesy Wired

Die size dictates memory interface width, so the 256-bit interface remains but Microsoft chose to go for DDR3 memory instead. A look at Wired’s excellent high-res teardown photo of the motherboard reveals Micron DDR3-2133 DRAM on board (16 x 16-bit DDR3 devices to be exact). A little math gives us 68.3GB/s of bandwidth to system memory.

To make up for the gap, Microsoft added embedded SRAM on die (not eDRAM, less area efficient but lower latency and doesn't need refreshing). All information points to 32MB of 6T-SRAM, or roughly 1.6 billion transistors for this memory. It’s not immediately clear whether or not this is a true cache or software managed memory. I’d hope for the former but it’s quite possible that it isn’t. At 32MB the ESRAM is more than enough for frame buffer storage, indicating that Microsoft expects developers to use it to offload requests from the system memory bus. Game console makers (Microsoft included) have often used large high speed memories to get around memory bandwidth limitations, so this is no different. Although 32MB doesn’t sound like much, if it is indeed used as a cache (with the frame buffer kept in main memory) it’s actually enough to have a substantial hit rate in current workloads (although there’s not much room for growth).

Vgleaks has a wealth of info, likely supplied from game developers with direct access to Xbox One specs, that looks to be very accurate at this point. According to their data, there’s roughly 50GB/s of bandwidth in each direction to the SoC’s embedded SRAM (102GB/s total bandwidth). The combination of the two plus the CPU-GPU connection at 30GB/s is how Microsoft arrives at its 200GB/s bandwidth figure, although in reality that’s not how any of this works. If it’s used as a cache, the embedded SRAM should significantly cut down on GPU memory bandwidth requests which will give the GPU much more bandwidth than the 256-bit DDR3-2133 memory interface would otherwise imply. Depending on how the eSRAM is managed, it’s very possible that the Xbox One could have comparable effective memory bandwidth to the PlayStation 4. If the eSRAM isn’t managed as a cache however, this all gets much more complicated.

Microsoft Xbox One vs. Sony PlayStation 4 Memory Subsystem Comparison
  Xbox 360 Xbox One PlayStation 4
Embedded Memory 10MB eDRAM 32MB eSRAM -
Embedded Memory Bandwidth 32GB/s 102GB/s -
System Memory 512MB 1400MHz GDDR3 8GB 2133MHz DDR3 8GB 5500MHz GDDR5
System Memory Bus 128-bits 256-bits 256-bits
System Memory Bandwidth 22.4 GB/s 68.3 GB/s 176.0 GB/s

There are merits to both approaches. Sony has the most present-day-GPU-centric approach to its memory subsystem: give the GPU a wide and fast GDDR5 interface and call it a day. It’s well understood and simple to manage. The downsides? High speed GDDR5 isn’t the most power efficient, and Sony is now married to a more costly memory technology for the life of the PlayStation 4.

Microsoft’s approach leaves some questions about implementation, and is potentially more complex to deal with depending on that implementation. Microsoft specifically called out its 8GB of memory as being “power friendly”, a nod to the lower power operation of DDR3-2133 compared to 5.5GHz GDDR5 used in the PS4. There are also cost benefits. DDR3 is presently cheaper than GDDR5 and that gap should remain over time (although 2133MHz DDR3 is by no means the cheapest available). The 32MB of embedded SRAM is costly, but SRAM scales well with smaller processes. Microsoft probably figures it can significantly cut down the die area of the eSRAM at 20nm and by 14/16nm it shouldn’t be a problem at all.

Even if Microsoft can’t deliver the same effective memory bandwidth as Sony, it also has fewer GPU execution resources - it’s entirely possible that the Xbox One’s memory bandwidth demands will be inherently lower to begin with.

CPU & GPU Hardware Analyzed Power/Thermals, OS, Kinect & TV
POST A COMMENT

245 Comments

View All Comments

  • piiman - Saturday, June 22, 2013 - link

    Are you required to use the Kinect controller or can you set what controller you want? I'm betting you can set the one you want to use and not be made to use Kinect?
    It wouldn't surprise me to see a later/lower cost version sold without Kinect though.
    Reply
  • Riseer - Sunday, June 23, 2013 - link

    MS had no choice but to use ESram,DDR3 has 1/3 the bandwidth of GDDR5.It's like using a band-aid on a sinking ship.Sony made Ps4 like a PC,down to the way the GPU uses GDDR5.Latency wise it won't be overly bad for the Cpu. Reply
  • tipoo - Wednesday, May 22, 2013 - link

    On the size and cooling, it's a 100 watt APU, they said in their technical talk with Engadget. Much lower than what the 360 debuted at. The reason it's as large as the launch 360 is that the PSU is internal this time. Reply
  • Noobslayer - Wednesday, May 22, 2013 - link

    No it isn't, psu is still external. Reply
  • tipoo - Wednesday, May 22, 2013 - link

    I don't think either was confirmed at this point, I did see the prototype power brick but who knows with retail hardware. If the One is that big PLUS a huge external brick, wtf. Reply
  • epobirs - Saturday, May 25, 2013 - link

    An MS exec in one interview indicated they prefer an external PSU for simplifying shipping the product into different regions. The core box remains identical with the external brick handling the power localization. It also gets a big heat source out of the box. They're likely to be intent on low cooling noise after the valid criticism the first couple iterations of the 360 received.

    There was a certain amount of rush to the 360's development due to the need to end production of the original Xbox and not leave a huge time gap in the shift to the new platform. The success of the 360, after those early debacles, meant they could take their time on this design and do a lot more testing for industrial factors like noise suppression.
    Reply
  • Riseer - Sunday, June 23, 2013 - link

    Well now it has been confirmed it will have a power brick. Reply
  • tyler31763 - Thursday, May 23, 2013 - link

    http://asset0.cbsistatic.com/cnwk.1d/i/tim2/2013/0...
    This picture basically confirms an external psu.
    Reply
  • RedavutstuvadeR - Saturday, May 25, 2013 - link

    i only see a space for the powercord Reply
  • tipoo - Monday, May 27, 2013 - link

    That could plug into a power cord or PSU. Reply

Log in

Don't have an account? Sign up now