By: Gabriele Svelto (gabriele.svelto.delete@this.gmail.com), May 18, 2013 5:48 am
Room: Moderated Discussions
Exophase (exophase.delete@this.gmail.com) on May 17, 2013 10:41 pm wrote:
> And maybe most relevant, most of the non-Javascript benchmarks (although unfortunately Javascript
> still make up a big chunk). The Javascript benchmarks are not that representative of anything
> outside of web browser performance and even that can be questionable, but as far as a lot of people
> are considered phones and tablets are just web browsing devices so maybe that's fair.
Browsers are still compiled as native applications and any JS benchmark which has a visible component will leverage compiled infrastructure quite heavily. Firefox performance can change quite a bit depending on the compiler and optimization choices (some parts benefit greatly from link-time optimization for example). It's important to keep in mind that outside of benchmarks JavaScript performance does not equate with browser performance.
> And maybe most relevant, most of the non-Javascript benchmarks (although unfortunately Javascript
> still make up a big chunk). The Javascript benchmarks are not that representative of anything
> outside of web browser performance and even that can be questionable, but as far as a lot of people
> are considered phones and tablets are just web browsing devices so maybe that's fair.
Browsers are still compiled as native applications and any JS benchmark which has a visible component will leverage compiled infrastructure quite heavily. Firefox performance can change quite a bit depending on the compiler and optimization choices (some parts benefit greatly from link-time optimization for example). It's important to keep in mind that outside of benchmarks JavaScript performance does not equate with browser performance.