The SunSpider base64 subtest is running 20x slower since build 55043 (Feb 19) using Safari.
base64: *20.1x as slow* 16.0ms +/- 16.5% 320.8ms +/- 6.3% significant
Oddly, this is the only test that was slower!?!
I first noticed this when I compared a recent nightly build with the most recent Apple version installed on my Mac 10.6.2.
Also, it appears that build 55027 (also Feb 19) was the last build that performs base64 well.
Changing URL in bugreport to specific test (string-base64.html) allowing for faster verifying.
http://trac.webkit.org/changeset/55035 looks like probable cause of performance regression with strings-base64 SunSpider test.
I can reproduce this in r55636.
If this performance drop is only seen "in-browser only", then perhaps a non-browser test that
mimics the browser action needs to be added to the test suite (if not currently skipped).
Seems that a 20x performance drop is not something that should go unnoticed by an
automated test suite.
Unfortunately, I can also confirm that this fix (r55035) caused a performance regression on ARM (JSValue32).
See the summarized results at:
** TOTAL **: *1.24x as slow* 7730.2ms +/- 0.3% 9608.5ms +/- 0.4% significant
string: *2.07x as slow* 1720.9ms +/- 0.2% 3562.5ms +/- 0.3% significant
base64: *10.1x as slow* 202.1ms +/- 0.7% 2049.5ms +/- 0.4% significant
55035 reverted in 55679, I'll land a new fix for the problem.
(keeping this bug open until the new fix lands).
Landed new version in r56021.