![]() ![]() Although the new rapid development cycle may be hurting Firefox in our reliability benchmarks, it also allows Mozilla to keep pace with Google Chrome on the performance front. A bit of trouble in CSS performance, as well as a high number of merely acceptable scores, are all that hold back Firefox from taking the gold. It takes first or second place on every platform for things like Kraken, Dromaeo, and SunSpider, but takes last or second-last place for more mundane tests like “How long does it take to load page X?” or “How long does it take to open up the browser?” Of course, given how much emphasis they’ve placed on benchmarks, I’m surprised they came in last in the maze solver race by such an embarassing margin.įTA: “With only one weakness and the highest number of non-winning strong scores, Mozilla Firefox is once again our runner-up. ![]() Looks to me like Firefox is over-optimizing for benchmarks. I hope all browser makers look at the tests and see if they can learn something from it, because all perform bad in atleast some of the tests. I know it isn’t a real performance test, I’m just wondering. They specifically choose not to implement it because of that.įor example the SVG font test that is done is testing something that is actually broken as I understand it.Īlso why not have a performance benchmark for the Acid3-test ? I wonder what the results would be. Interresting enough the Acid3 test is included, the parts Firefox does not implement actually didn’t make it into the final specifications. You may agree or disagree with the choice the Firefox developers made, but they are testing different things (there is a setting to disable this behaviour if I remember correctly). So memory management is different in that case for Firefox. Thus you can’t just look at the memory usage of the browser and say it doesn’t clean up the memory. I’m just wondering because I noticed the same things and benchmarks usually don’t depend on the above mentioned things so that might explain it.Īlso with the memory management tests, I think Firefox keeps closed tabs in memory so when you choose to ‘open a recently closed tab’ it will just load the rendered page from memory I think. I also wonder about the page-load tests if they load the same page from a proxy or something like that, what about ads ? Does it load the same ad ? What about DNS ? Or do they just run the test 25 times, clearing the cache each time and hope for the best ? I couldn’t find how they actually test that though. Take the ‘eight tabs’-test, Firefox when you start it up with ‘tabs open’ will first load the page from cache and than refresh to see if something changed. Knowing a bit how Firefox handles these things, I would say it very much depend on how you test. They may be fast, but don’t load the whole page. At least they added a ‘reliabilty benchmark/proper page loads’ section which shows that Chrome and IE don’t always actually load the page properly.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |