No, it's showing the combined total bandwidth of the CPU+GPU decreases disproportionally as you use more CPU bandwidth.
Actually it says exactly that right on the slide, heh.
Repost of the slide since I just saw it posted on GAF anyway
I thought a portion of the bandwidth was reserved specifically for the CPU? Doesn't the CPU have direct access to memory somewhere in the 20GB/s range? Wouldn't this in part be responsible for the relative numbers?
Do you know how graphs work?
The curious part is that the BW is still 140GB even when no CPU appears to take any bandwidth in the graph
With DDR3 you pretty much take the number of bits on the interface, multiply by the speed and that's how you get 68GB/s. That equivalent on ESRAM would be 218GB/s. However, just like main memory, it's rare to be able to achieve that over long periods of time so typically an external memory interface you run at 70-80 per cent efficiency.
No, the PS4 APU has an internal bus dedicated to the CPU, which is hooked up to the internal memory controller crossbar. That doesn't make some memory bandwidth dedicated for anything per se. It may be that the memory controller prioritizes CPU memory accesses though (due to latency concerns and whatnot), which in reality would have pretty much the same effect.I thought a portion of the bandwidth was reserved specifically for the CPU?
This is just bizarre pedantry. Look at the fking graph, what does it show you? Seriously, just look at it. Tell us what you see.Yes! and nowhere on that graph does it say the memory bandwidth is now 140GB/s & not 176GB/s.
I'm not sure if you're being obtuse on purpose or if it simply comes natural to you. That graph shows an effective bandwidth representation, alright? A real-world situation, not a paper spec number. 176 = paper spec, graph = approximation of real world performance.What exactly make people think that because the PS4 GPU is shown using 140GB/s that the GDDR5 has somehow changed from 176GB/s to 140GB/s?
No, the PS4 APU has an internal bus dedicated to the CPU, which is hooked up to the internal memory controller crossbar. That doesn't make some memory bandwidth dedicated for anything per se. It may be that the memory controller prioritizes CPU memory accesses though (due to latency concerns and whatnot), which in reality would have pretty much the same effect.
It would be pretty silly to set aside N gigabytes per second of bandwidth for CPU use if the CPU never even uses that much...
This is just bizarre pedantry. Look at the fking graph, what does it show you? Seriously, just look at it. Tell us what you see.
I'm not sure if you're being obtuse on purpose or if it simply comes natural to you. That graph shows an effective bandwidth representation, alright? A real-world situation, not a paper spec number. 176 = paper spec, graph = approximation of real world performance.
That graph isn't changing anything the 176GB/s bandwidth is still the same as it was before. how much they are able to get out of it doesn't change the specs that we already knew.
It's still the same 176GB/s peak memory bandwidth. just because the CPU/GPU isn't using 100% of that bandwidth doesn't change it from being 176GB/s peak memory.
That graph isn't changing anything the 176GB/s bandwidth is still the same as it was before. how much they are able to get out of it doesn't change the specs that we already knew.
It's still the same 176GB/s peak memory bandwidth. just because the CPU/GPU isn't using 100% of that bandwidth doesn't change it from being 176GB/s peak memory.
We know the spec is 176GB/s but the value that matters is the 140GB/s which is accessible, Some of us were curious why 36GB are practically unusable
We know the spec is 176GB/s but the value that matters is the 140GB/s which is accessible, Some of us were curious why 36GB are practically unusable
True but this was the message that Sony was sending to PlayStation 4 developers. Unless Sony are in the habit of trying to mislead developers for kicks, I think we can safely assume that the point of this slide is to convey 'average' real world cases.The graph doesn't provide information on the methodology used for the test, or whether it was just some kind of average over a range of workloads.