3 ms·
Here's some more data from Mozilla's own testing setup: http://arewefastyet.com/?machine=5 http://arewefastyet.com/?machine=5 Where JM+TM stands for "Jagermon
by Maciek416 16y ago
Here's some more data from Mozilla's own testing setup:
http://arewefastyet.com/?machine=5 http://arewefastyet.com/?machine=5
Where JM+TM stands for "Jagermonkey + Tracemonkey". It looks to be gaining on V8 and Apple Nitro pretty fast, considering the timeline involved.
- sp332 16y agoGotta love the domain name + favicon :-)
- unwantedLetters 16y agoAlso like the big "No." mid page. The team seems to be pretty focused on getting to be faster than Chrome/Safari. Great idea to have a simple goal, and a simple answer to whether they have achieved it or not.
- acqq 16y agoLooking at their v8 bench speedup: from 0.7 ms to around 0.3 ms we get again 2.3, comparable with the simple loop measurement. But interestingly enough, Google's V8 gets its speed in a very different way, as my mentioned benchmark loop performs much worse in Chrome: 3.9 sec on Chrome 6.0.472, thats 4.4 times slower than ActionScript or Firefox Beta 4.