AnandTech: Xbox One vs. PS4 - Hardware comparison


Recommended Posts

No it wont, the ESRAM makes up for the lack of bandwidth and tries to prevent bottlenecks because they used DDR3 ram instead of the much faster GDDR5.

Are you a console developer? I'm not,. I imagine that how the games use the esram(and if they use it), how they will optimze for gddr5 or ddr3 etc. can be specified by a developer. If that's wrong, I'll wait until a professional developer with optimzation experience on a console tells me that. And as always. The esram, the data-move-engine, the touchpad on the ps4 controller, the extra CU, ROP or whatever still doesn't bring the exclusives to the "opponent".

I don't got more time for this anymore. I've got better things to do, since I know WHY I'll buy a specific console instead of wondering how much % extra performance I may be getting. And I got a great internet connection, so I will be able to take advantage of whatever the devs does in the azure cloud.

The PS3 was better on paper yes but the CPU was a nightmare to work with. This generation they have identical CPUs and architectures and both GPUs are of the same family so its an easy comparison to make.

XboxOne.png

Everything is on die is it's a freaking SoC.

so you give me a user drawn image to try to prove your point, from a website with headlines such as "Microsoft admits they lost the console war with Xbox One", and "Microsoft cedes console to Sony, gives up on gaming" . Nice,but youre not fooling anyone.

They are the same family of GPU, AMD Southern Islands, we know they are using Graphics Core Next architecture, we know it can do 768 operations per clock which was straight from the mouth of Microsoft which means we can deduce that it is using 12 CUs and PS4 18CUs.

geez,you really don't know how to read. I know about the compute units,thats not what im arguing.

You calling me ignorant is the same as you believing there are modifications, added parts or extra logic. The only extra logic that Xbone has over PS4 is the ESRAM and Move Engines. While the Move Engines can take care of some of the missing GPGPU stuff it doesn't make up the 6 missing CUs.

that is opinion,not fact. unless you have the silicon masks, everything is opinion until we get teardowns into the chips or explanations about how things inside work from the guys who worked on them. and what I find comical is you being adamant there are no modifications to xbox one chip, but sony made modifications to ps4 chip.

You keep repeating that you think it has "magic extra logic" doesn't mean it is fact either, did you even watch the Microsoft Architectural Briefing?

I never claimed its fact, I am saying it is possible,and giving reasons to back my opinion.

The first Xbox didn't have EDRAM, so your "they did it on the previous version" assumption is false.

previous version to xbox one. I guess you're really reaching here to get "get me".

Do you understand what an SoC is?

This should tell you that the ESRAM isn't external.

This doesnt tell you anything,and I do know what a soc is, I also know busses exist,and the previous xbox used a ram chip/ASIC connected to the main cpu die externally through a dedicated bus,so there is precedent for this kind of thing. Again,this is called opinion,you are speaking like you designed the thing.

Last comment from me :)

No I just read and listen to what Microsoft are saying and am not making assumptions based on what the previous console had.

This is all good. I agree that we can't assume that Xbox One's SoC would work the same way as the old chip(s) did.

The problem is that while you're not making assumptions based on previous console features, you're still making conclusions based on the few details they shared! Did you consider that there may be more details that they DIDN'T say? Like how the esRAM would work, if they included some revolutionary optimization code etc.etc. I'm sure that they didn't reveal the whole chip design at the press event or at the post-show live event.

It's like a salesman revealing that the car has 1000hp. A 1000hp doesn't help me much when he forgot to tell me that the car has no steering wheel. The point is: you don't know the whole design/specifications, so it's wrong to make conclusions about their performance at this point. Both made custom modifications to the chips.

8BmZs7f.png

ESRAM

Durango has no video memory (VRAM) in the traditional sense, but the GPU does contain 32 MB of fast embedded SRAM (ESRAM). ESRAM on Durango is free from many of the restrictions that affect EDRAM on Xbox 360. Durango supports the following scenarios:

  • Texturing from ESRAM
  • Rendering to surfaces in main RAM
  • Read back from render targets without performing a resolve (in certain cases)

The difference in throughput between ESRAM and main RAM is moderate: 102.4 GB/sec versus 68 GB/sec. The advantages of ESRAM are lower latency and lack of contention from other memory clients?for instance the CPU, I/O, and display output. Low latency is particularly important for sustaining peak performance of the color blocks (CBs) and depth blocks (DBs).

As I already stated the ESRAM is there to negate the slow DDR3 RAM and weak GPU they are using to save money so they can afford to bundle Kinect in every box.

The Durango GPU includes a number of fixed-function accelerators. Move engines are one of them.

Durango hardware has four move engines for fast direct memory access (DMA)

This accelerators are truly fixed-function, in the sense that their algorithms are embedded in hardware. They can usually be considered black boxes with no intermediate results that are visible to software. When used for their designed purpose, however, they can offload work from the rest of the system and obtain useful results at minimal cost.

Each move engine can read and write 256 bits of data per GPU clock cycle, which equates to a peak throughput of 25.6 GB/s both ways. Raw copy operations, as well as most forms of tiling and untiling, can occur at the peak rate. The four move engines share a single memory path, yielding a total maximum throughput for all the move engines that is the same as for a single move engine. The move engines share their bandwidth with other components of the GPU, for instance, video encode and decode, the command processor, and the display output. These other clients are generally only capable of consuming a small fraction of the shared bandwidth.

The advantage of the move engines lies in the fact that they can operate in parallel with computation. During times when the GPU is compute bound, move engine operations are effectively free. Even while the GPU is bandwidth bound, move engine operations may still be free if they use different pathways. For example, a move engine copy from RAM to RAM would not be impacted by a shader that only accesses ESRAM.

As I already stated, the Move Engines are there purely to negate the slow memory and bottlenecking, they help offload some of the load from CPU/GPU but they are no way going to make up the difference of the 50% faster PS4 GPU.

and why do you all care about the hardware? the ps3 was better then the 360, but the multi-platform games was in my experience usually better on the 360, and they didn't s*ck even though the 360 was "holding the games back".

You came into a thread titled HARDWARE COMPARISON wondering why everyone is talking about the hardware. Not sure what you were expecting...

This thread is still going? lol.

No one will know what hardware is the "best" until the devices ship.. No one. You can make assumptions on historical trends, pc trends and personal experiences, but until you have actually used & compared these two devices, we're all just bitching and moaning about specs. Specs don't always translate to performance/value/fidelity/experience.

One of the most sought after cars today is a car that fails in so many specs and can barely drive two hours between charges, yet when you put it together as a package and see it for what it is, its value & functionality is simply incomparable to anything else out there.

Way too much assuming in here

As I already stated the ESRAM is there to negate the slow DDR3 RAM and weak GPU they are using to save money so they can afford to bundle Kinect in every box.

I don't think Kinect is as costly as you think (parts wise). That can't be the only reason.

I don't think Kinect is as costly as you think (parts wise). That can't be the only reason.

Just cause it isn't costly doesn't mean microsoft wont jack up the price because of it. Just look back at the 360: If you wanted a 360 with an HDD you had to pay $100 more than one without it. Despite the fact a 250GB HDD didn't cost anywhere near $100.

Just cause it isn't costly doesn't mean microsoft wont jack up the price because of it. Just look back at the 360: If you wanted a 360 with an HDD you had to pay $100 more than one without it. Despite the fact a 250GB HDD didn't cost anywhere near $100.

We are talking material cost here not retail pricing.

TheLegendofMart mentioned Microsoft saving on RAM to accommodate Kinect, I am saying Kinect's material won't be as costly as it seems and there has to be some other reason if they were trying to hit a price point.

In short, my post had nothing to do with the overpriced accessories. Try to follow the conversation.

the raw processing power of the system makes me cringe though after I look at my desktop systems raw power... dev's are going to have to come up with some highly optimized code to make good use of these systems... sure they are faster raw FLOP wise then the 360 and PS3, but compared to a Intel ivy bridge i7 system with a good quality mid range graphics card......

Would you not want fully optimized code to begin with?

I don't got more time for this anymore. I've got better things to do, since I know WHY I'll buy a specific console instead of wondering how much % extra performance I may be getting.
The thread was never about why Graimer will buy a specific console in the first place. If you didn't want to discuss the performance differences between the consoles why bother posting here?

It seems like the majority of people posting in these console comparison threads are only trying to justify their pre-determined choice of one or the other. Gee, be happy with your choice and let those who want to discuss objectively do so.

Whoa, moderation in the gamer's hangout section!? That's a rarity.

Apparently it needs to become more frequent. ;)

Pleeeeeeeease do not close this thread. I am enjoying the debates.

I know it's hard to restrain ourselves at times, but just try to drop the personal attacks.

:shiftyninja:

Just stay within the confines of the community rules and it's all good. :)

Here's a nice 3D render to lighten the mood...

http://majornelson.c...er-of-xbox-one/

Heh made me chuckle that Major Nelson put "May not work on mobile or older browsers " and it actually doesn't work in IE10 as WebGL isn't supported in IE10.

Looks good and nice to see many I/O options on the back.

I noticed some people keep comparing gddr3 to gddr5 and the xbox one uses DDR3 and NOT GDDR3 like the xbox360. GDDR3 is basically ddr2. DDR3 would be better for all purpose computing but if your only doing games gddr5 is better. Basically gddr5 handles large amounts of data better than ddr3 but ddr3 handles small amount of data better. Also gddr5 has horrible latency compared to ddr3 but when doing gpu intensive task it shouldnt matter to much.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!