132
edits
Dromaeo: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 6: | Line 6: | ||
* The number of test iterations that are run. Currently each test is run, at least, 5 times - it's been requested that this be increased. | * The number of test iterations that are run. Currently each test is run, at least, 5 times - it's been requested that this be increased. | ||
* The calculation of error ranges. Currently the data is fit to a t-distribution, it's been requested that it use a two-variable t-test. | * The calculation of error ranges. Currently the data is fit to a t-distribution, it's been requested that it use a two-variable t-test. | ||
* The quality of the tests. Currently the tests shown are a subset of the tests presented by [http://webkit.org/perf/sunspider-0.9/sunspider.html SunSpider]. There is no particular choice for these tests, other than that they were ones that originated from the original [http://ejohn.org/projects/javascript-engine-speeds/ JavaScript Engine Speeds] compilation. The corpus will likely expand to include all of the SunSpider tests, plus some. | * The quality of the tests. Currently the tests shown are a subset of the tests presented by [http://webkit.org/perf/sunspider-0.9/sunspider.html SunSpider]. There is no particular choice for these tests, other than that they were ones that originated from the original [http://ejohn.org/projects/javascript-engine-speeds/ JavaScript Engine Speeds] compilation. The corpus will likely expand to include all of the SunSpider tests, plus some. Additionally, the use of closures to encapsulate tests is contested and will probably be revised. | ||
All of these points are currently being worked upon - as a unified JavaScript performance analysis platform is a desired goal by all browser vendors. | All of these points are currently being worked upon - as a unified JavaScript performance analysis platform is a desired goal by all browser vendors. | ||