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


Your max is a little off. Broadway runs a 723 MHz. Assuming your 32 times slow statement is corret, If it was upped to 3 core then it would only need to run at 2 MHz to match the xenos. 2.5 would put it ahead.


Wait a seccond that doesn't sound right, each Xenon core should obliterate the Broadway at the same clock, it has a SIMD: VMX128 with 2× (128×128 bit) registers and SMT capabilities, plus a more modern instruction set.

The actual numbers are 2.9 Gflops for Broadway at 729 MHz (the reported clock of the Wii). 76.8 GFLOPS for the Xenon so ~26X faster in terms of flops. So Xenon 25.6GFlops per core at 3.2GHZ is over 8.8X faster than the Wii's Broadway at 729Mhz in terms of raw Flops so wouldn't each Broadway core wouldn't it have to be clocked at 6.435GHz to match it with tri core vs tri core?

But I don't think anyone is suggesting that it's just 3 overclocked Broadway cores.

Forgive my ignorance, but what exactly does the number of FLOPS (FLoating point Operations Per Second, right?) determine? What aspect of performance does it contribute to?

Because IIRC, the PS2 CPU had more 4 times more FLOPS than the original Xbox's, and more than double the Wii's, yet the PS2 is regared as the weaker system.

basically the number of floating point numbers (http://en.wikipedia.org/wiki/Floating-point) that a proccessor can proccess each seccond. It doesn't really mean all that much for most aplications but it's probably the most widely used performance metric in terms of raw performance. It only really mesures one aspect of CPU performance tho. The PS2's CPU had two coproccessors dedicated to doing floating point math, but the tasks that were performed on them were mostly tasks handled by GPU components in the Gamecube and Xbox.  



@TheVoxelman on twitter

Check out my hype threads: Cyberpunk, and The Witcher 3!