canmove, Confirmed users
1,584
edits
Performance/MemShrink: Difference between revisions
Jump to navigation
Jump to search
m
→areweslimyet.com: link to Kraken
m (→areweslimyet.com: link to Kraken) |
|||
| Line 204: | Line 204: | ||
http://arewefastyet.com is a very successful site used to track the performance of Firefox's JavaScript engine. Why was arewefastyet.com so successful? Some key characteristics. | http://arewefastyet.com is a very successful site used to track the performance of Firefox's JavaScript engine. Why was arewefastyet.com so successful? Some key characteristics. | ||
* The benchmarks were easy to choose: everybody already used | * The benchmarks were easy to choose: everybody already used SunSpider and V8, and then Mozilla released [[Kraken]]. They run quickly, too, which is nice for devs, and allows expensive tools (like Cachegrind) to be used. | ||
* The metrics were easy to choose. SS time, V8 time, Kraken time. They can be measured easily, precisely, and fairly repeatably. You can break the total time down into per-benchmark times, which really helps with understanding improvements and regressions. They're easy for devs to run on their own machine. | * The metrics were easy to choose. SS time, V8 time, Kraken time. They can be measured easily, precisely, and fairly repeatably. You can break the total time down into per-benchmark times, which really helps with understanding improvements and regressions. They're easy for devs to run on their own machine. | ||
* There was a well-defined goal: match or beat the other browsers. | * There was a well-defined goal: match or beat the other browsers. | ||