By using this site, you agree to our Privacy Policy and our Terms of Use. Close
curl-6 said:
fatslob-:O said:
curl-6 said:

A crappy web browser could  still easily bring down the overall result.

What's more, in a game environment, Espresso is designed to work in tandem with the system's GPGPU, Latte. I doubt a generalized browser benchmark test leveraged Latte's contributions.

Read my response to forethought14.

I'll let him take that one, so we don't end up creating two pointlessly samey threads of conversation, haha.

You can do it now. I don't think he's going to reply. 

repost:

forethought14 said:
@fatslob 

Espresso is slow compared to PS360 if you make it perform floating point performance tasks. Its only method for doing these SIMD tasks is via paired singles, and at this clock, it likely doesn't match those two. Though there were benchmarks done by a member of Neogaf (blu) that proves that the architecture of Broadway isn't too bad at these tasks at all, just likely not at the same level as PS360. But it's a processor with strengths in places like GP or integer code, something the PS360 are just terrible at. Calling Espresso "slow" is not fair at all, since it's not designed to do much of those floating point tasks. Probably why Iwata encourages GPGPU, because that could alleviate Espresso.

You do realize that doing gpgpu is awkward on a VLIW architecture, right ? (What's more is that it's awkward for alot of developers.)

And what's more is that gameplay physics is best done on a cpu that depends on floating point power so does this mean that the WII U won't have alot of rigid body physics ?