Flash based cpu tests?

Jongamer · Post by **Jongamer** » Sun Jun 03, 2007 9:03 pm

Does anyone have a link to a flash based cpu speed test, because the only one i found had a broken link.

I would like it to be flash as I want to try to uncover the wii`s cpu power through the opera browser.

Dr. KillGood · Post by **Dr. KillGood** » Sun Jun 03, 2007 10:51 pm

LOL It is prolly like 1GHz.

Wii is the failure. It is great for the first week than it gets old.

atari2600a · Post by **atari2600a** » Sun Jun 03, 2007 11:40 pm

I believe the Wii was clocked somewhere in the 750MHz range. I'm not sure, it's on Wikipedia though...

daguuy · Post by **daguuy** » Sun Jun 03, 2007 11:47 pm

It's epically underpowered. In the 720's if I remember correctly. But since it's much less powerful than the competition, game makers treat it like it's even weaker and make games that look like they belong on PSone

Felino · Post by **Felino** » Mon Jun 04, 2007 1:47 am

Google man!

Wiki <- Google me wrote:
Processors:

CPU: PowerPC based "Broadway" processor, made with a 90 nm SOI CMOS process, clocked at 729 MHz
GPU: ATI "Hollywood" GPU made with a 90 nm CMOS process, clocked at 243 MHz.

Please remove that avatar.

Jongamer · Post by **Jongamer** » Mon Jun 04, 2007 12:14 pm

Yeah problem is thats not a confirmed number. and was probably taken from wikipedia

Limewater · Post by **Limewater** » Mon Jun 04, 2007 12:23 pm

Haven't you folks ever heard of benchmarks?

There's a lot more that goes into "processing power" than just clock speed, and clock often isn't even a very good indicator of how "fast" a processor is.

tom61 · Post by **tom61** » Mon Jun 04, 2007 12:35 pm

Limewater wrote:Haven't you folks ever heard of benchmarks?

There's a lot more that goes into "processing power" than just clock speed, and clock often isn't even a very good indicator of how "fast" a processor is.

Neither is Flash, as it is an interpreter, so the code isn't running natively.

Limewater · Post by **Limewater** » Mon Jun 04, 2007 2:23 pm

tom61 wrote: Neither is Flash, as it is an interpreter, so the code isn't running natively.

I don't know a whole lot about flash in particular, but you actually can do some decent benchmarking in interpreted languages if they have one-line tasks and commands that highly computationally intensive.

Interpreting adds a lot of overhead to sequential code, but they still eventually wind up calling native processes.

To do speed tests, you just have to make sure that the interpretation overhead of executing your test are very small compared with the load of running the tasks you call.