Function racer

The number below each method is the number of milliseconds consumed for the total operations performed (above the methods).
The operation size (at the top) is scaled to keep the framerate between 29 and 32.

Click on it to start the race. Click off of it to stop the race.

Method A is always faster than Method B (except sometimes in firefox for some reason) on my computer, but the difference is minimal (like .5%). There are obviously little ways in which we can tweak the algorithms. For example: we could not declare a0, a1, b0, and b1 every single time.

Comments

This is on my work computer. P4 3ghz. Strange that it outperforms my home machine, An Athlon X2 3800+ which got around 15k ops per frame. Also Method B is ~1% faster than Method A on this computer? Running Chrome. I had a lot of stuff open at the same time, so that might be goofing the results.