It may have being an issue when hitting HD resolutions but developers had a form of solution called "tiling" which allowed it to split up the render targets and depth buffers into "tiles". 

Another thing unique thing about the xbox 360's eDRAM was that it had an 8 extra ROPS which essentially allowed it "free anti aliasing". This had meant that blending operations were possible on a separate die such as the eDRAM. 

Memory bandwidth is still an issue seeing as how the eDRAM doesn't solve the texturing bandwidth of the WII U. It essentially limits the amount of high resolution textures the WII U can have.

curl-6 said:

Tiling still wasn't as good as actually having the space.

32 mb isn't a whole lot either sooo  it really doesn't do much in the grand scheme of things compared to having 8 extra ROPs ...

And again, both Shin'en and the dev from the Eurogamer article stated that memory bandwidth was not an issue. Plus, it didn't stop Need for Speed and Trine 2 using better-than-PS360 textures.

Shin'en has never clarified the bottleneck of the WII U ... They have only spoken about it's strengths and not the weaknesses. Those games had better mip mapping to mitigate the bandwidth weaknesses and they weren't much better than the last generation HD twins.

32MB is still over thee times more than 10MB. Instead of just being a framebuffer, Wii U's eDRAM is available for other tasks requiring fast memory, like some GPU writes and CPU-intense work.

"Theoretical RAM bandwidth in a system doesn’t tell you too much because GPU caching will hide a lot of this latency" -Shin'en on RAM bandwith not being a bottleneck.

"This wasn't really a problem for us. The GPU could fetch data rapidly with minimal stalls (via the EDRAM) and we could efficiently pre-fetch" - Dev from the Eurogamer article on the same thing.

Trine 2 improvements:

-       Textures 

-       Normal map compression 

-       Anti-aliasing  

-       Locked screen resolution 

-       Physics

-       Water effects

Need for Speed improvements:

-       Textures

-       Reflection mapping

-       Framerate

It's best suited to just being a framebuffer ... Why would the CPU need that much bandwidth when it only has a 64 bit wide SIMD engine ?

As for your second account that doesn't matter because GPUs are meant to work on large data sets therefore having more bandwidth is beneficial than lower access times. Despite the fact that the xbox one can cache it's data faster it's still gets thrashed hard by the PS4. 

But it's big enough to have room to spare even after a 1080p frame is stored, and the free space is available to both the CPU and GPU for anything that needs fast memory access.

Basically, you prioritise high speed tasks to the eDRAM, so that the main RAM bandwidth doesn't become an issue as it's primarily used for slower operations.

The thing is, though, that the PS3 was much more difficult to develop for than the 360 because of its use of the Cell processor, so multiplatform games ran better on the 360 than on the PS3 because they were coded better (at least, they ran better for the first part of the generation, I'm not sure if devs have gotten used to the Cell enough to close the gap). Neither Bayonetta 1 on 360 nor Bayonetta 2 on Wii U have this problem, so it makes more sense to compare those two versions.

You need more than just a 1080p frame though ... Did you forget about depth and stencil buffers which are required for z-buffering and shadowing ? 

The only thing that the eDRAM can meaningfully priortise are render targets which are related to framebuffer operations ... Great that'll be enough to saturate the ROPS but how do I solve bandwidth for texturing purposes ? 

 " konzoloa"? What the hell  is that? Is that how rednecks spell the word " console"?