Xbox One (Durango) Technical hardware investigation

Discussion in 'Console Technology' started by Love_In_Rio, Jan 21, 2013.

Thread Status:
Not open for further replies.
  1. Cjail

    Cjail Fool
    Veteran

    Joined:
    Feb 1, 2013
    Messages:
    2,027
    Likes Received:
    211
    Ok next time I will use a more explanatory link.
     
  2. Xbat

    Veteran

    Joined:
    Jan 31, 2013
    Messages:
    1,650
    Likes Received:
    1,315
    Location:
    A farm in the middle of nowhere
    Does not say much for MS hardware engineers if they only figured this out now.
     
  3. warb

    Veteran

    Joined:
    Sep 18, 2006
    Messages:
    1,057
    Likes Received:
    1
    Location:
    UK
    Huh, so DDR3 + eSRAM bandwidth actually is more than 200GB/s.
     
  4. Love_In_Rio

    Veteran

    Joined:
    Apr 21, 2004
    Messages:
    1,627
    Likes Received:
    226
    Is ridiculous.Maybe they find next time that from production came 14 CUs instead of 12.Wasnt Richard from DF a technical journalist?.
     
  5. dskneo

    Regular

    Joined:
    Jul 25, 2005
    Messages:
    816
    Likes Received:
    298
    Using fantasy land mathematics, yes, more than 200
     
  6. Cranky

    Newcomer

    Joined:
    May 22, 2013
    Messages:
    134
    Likes Received:
    0
    This does seem to explain the over 200 gb/s quote from the hardware panel quite nicely.
     
  7. warb

    Veteran

    Joined:
    Sep 18, 2006
    Messages:
    1,057
    Likes Received:
    1
    Location:
    UK
    Or the final hardware is a somewhat more capable than old documents suggested, and they wanted to get that out there.
     
  8. MarkoIt

    Regular

    Joined:
    Mar 1, 2007
    Messages:
    392
    Likes Received:
    0
    The interface width is 128 byte. If the clock is 800 Mhz, there no way you can exchange more data than 102 Gb/s. If indeed this news is true, then they may have changed the clock of the interface and/ or only of the ROPs... running at double the GPU frequency? Than, in the same GPU cycle, you could read and write simultaneously.
     
  9. Love_In_Rio

    Veteran

    Joined:
    Apr 21, 2004
    Messages:
    1,627
    Likes Received:
    226
    Is the same.The 102GB/s is read 102GB/s write.They found out now that both can be done simultaneously?.
     
  10. Cranky

    Newcomer

    Joined:
    May 22, 2013
    Messages:
    134
    Likes Received:
    0

    Sigh, there is nothing fantasy about it. 200 gb/s can be moved through the memory units simultaneously. It is just that the data needs to be split into at least two pools for that to happen - 1 main memory and 1 esram. MS even highlight the type of work loads that are best suited for esram.
     
  11. dragonelite

    Veteran

    Joined:
    Dec 20, 2009
    Messages:
    1,556
    Likes Received:
    1
    Location:
    netherlands
    haha 7790 dream continues :lol:
     
  12. Mandrion

    Newcomer

    Joined:
    May 15, 2013
    Messages:
    14
    Likes Received:
    0
    So basically the theoretical peak performance for eSRAM is 192GB/s and DDR3+eSRAM combined will be 260GB/s?

    So according to this

    http://www.vgleaks.com/durango-memory-system-overview/

    The GPU can theoretical read with up to 260GB/s and can write with up to 192GB/s.
     
  13. patsu

    Legend

    Joined:
    Jun 25, 2005
    Messages:
    27,709
    Likes Received:
    145
    From the DF article, it sounds like they can do read and write together under some circumstances (when they found some "holes" to squeeze some processing inside).
     
  14. Scott_Arm

    Legend

    Joined:
    Jun 16, 2004
    Messages:
    15,134
    Likes Received:
    7,680

    So, they're adding the read and write bandwidth together. Isn't that sort of ... dumb. That's basically the same specs we had before, just added together to look better. I thought Digital Foundry was a little bit better than that.
     
  15. Love_In_Rio

    Veteran

    Joined:
    Apr 21, 2004
    Messages:
    1,627
    Likes Received:
    226
    In fact isnt this news talking about a downgrade?. If clock was still 800Mhz the theorical max bandwidth if writing and reading at the same time would be 204 GB/s.They claim 192 that reversing would take us to 96 GB/s read 96 GB/s write and a clock of 750MHz.
     
  16. MarkoIt

    Regular

    Joined:
    Mar 1, 2007
    Messages:
    392
    Likes Received:
    0
    On the same 128 byte interface how can you transfer more information than what is theoreticaly possible? Because this is what we are talking about.
     
  17. QualityAssurance

    Newcomer

    Joined:
    May 24, 2013
    Messages:
    5
    Likes Received:
    0
    Location:
    Washington, DC

    That's what I was thinking. Sounds like PR fluff to me.
     
  18. patsu

    Legend

    Joined:
    Jun 25, 2005
    Messages:
    27,709
    Likes Received:
    145
    I have no idea but I am just wondering why can't they post a higher test result if they can go 192.

    Perhaps some conditions need to be "aligned" ?
     
  19. Shifty Geezer

    Shifty Geezer uber-Troll!
    Moderator Legend

    Joined:
    Dec 7, 2004
    Messages:
    44,106
    Likes Received:
    16,898
    Location:
    Under my bridge
    Bidirectional bus? It doesn't make a lot of sense. Peak theoretical hardware limit is bus*clock. Can't get past that. If the bus is bidirectional by design, you'd get double peak BW. The key info in the DF article is 'holes', which means nothing to me.

    It does match what Cranky's said, though, that with 133 GB/s realistic BW, plus 68 GB/s DDR3, we get the 200 GB/s of the E3 conference. I just can't see what the hole is and how it gets filled. :???:
     
  20. Hornet

    Newcomer

    Joined:
    Nov 28, 2009
    Messages:
    120
    Likes Received:
    0
    Location:
    Italy
    Maybe they have alpha blending logic on the ESRAM, similarly to the Xbox 360 (but without MSAA or depth-testing support). If this is the case, the GPU <-> ESRAM bandwidth might still be 102.4 GB/s, but a single-pixel read-modify-write cycle for alpha-blending is performed on the ESRAM, without the need to move the data back to the ROPs. So it might be that the engineers of course already knew of this feature, but they didn't take it into account in the performance figure provided earlier to the developers.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page

  • About Us

    Beyond3D has been around for over a decade and prides itself on being the best place on the web for in-depth, technically-driven discussion and analysis of 3D graphics hardware. If you love pixels and transistors, you've come to the right place!

    Beyond3D is proudly published by GPU Tools Ltd.
Loading...