761
edits
Benchmarks: Difference between revisions
→Javascript
Jprosevear (talk | contribs) |
Jprosevear (talk | contribs) |
||
| Line 77: | Line 77: | ||
* '''[http://www.webkit.org/perf/sunspider/sunspider.html Sunspider]''' | * '''[http://www.webkit.org/perf/sunspider/sunspider.html Sunspider]''' | ||
** Tests run very fast which makes measurement error significant and means that the tasks are not scaled to a significant amount of work. | ** Tests run very fast which makes measurement error significant and means that the tasks are not scaled to a significant amount of work. | ||
*** Has 26 tests that run in 200-300ms, depending on the machine, so about 10ms per test. The differences between current browsers are now on the order of running a test in 9ms instead of 10ms, so practical significance is limited. Another problem with SunSpider is that with 10ms per tests, making a more advanced JIT doesn't improve your score, because the compile time ends up outweighing the improved run time. This doesn't matter so much for comparing browsers, but it means SunSpider doesn't really drive JS engines to get faster on big apps. If anything, it tells browsers to create new startup modes so they can run small programs a shade faster. (dmandelin) | |||
=== DOM === | === DOM === | ||