Thus covering not just JavaScript performance but also HTML and CSS performance

Posted by Manoj Singh Rathore
10
Apr 21, 2017
102 Views

The best protection against this kind of gaming is to develop better benchmarks. Google has developed infrastructure to allow it to repeatably and consistently time the loading of entire Web pages (thus covering not just JavaScript performance but also HTML and CSS performance) which it uses to measure real-world performance on 25 popular sites and guide development. The Safari developers created JetStream to replace SunSpider, containing a wider mix of tasks and a greater proportion of real applications. The Speedometer benchmark, also from WebKit/Safari developers, is artificial, but Google has discovered that it corresponds well to real-world performance of popular sites.

Google, who says it started to focus on how JavaScript is being interpreted on real websites, says it improved page load times in Chrome by 10-20%, depending on CPU architecture, based on "real-world performance data," instead of Octane's narrowly focused static tests.

"Comparing page snapshots [tests] to Octane revealed that Octane was a poor approximation of most websites," Google engineers said. "Given the plateau of Octane scores across web browsers and the over-optimization of peak performance, we decided to retire the benchmark as a general-purpose measure of real-world JavaScript performance."

In addition, sites like Facebook, Twitter, and Wikipedia have demonstrated that the Octane benchmark wasn’t accurately reflecting how Google’s V8 JavaScript engine actually worked on real sites. Therefore, Octane wasn’t actually capturing important information on how V8 and other JavaScript engines perform in the modern web environment.

Finally, it became apparent that efforts to gain higher Octane benchmark results were actually having a deleterious effect on performance in real-world scenarios. The combination of Octane’s increasing disconnect with how web sites actually work with developers’ efforts to achieve higher and higher Octane scores meant an increasingly negative impact on how JavaScript engines were designed to perform when it really matters. Even bugs in Octane have been leveraged by developers to gain higher benchmark results.

Learn by techstack digital marketing course in delhi

Comments
avatar
Please sign in to add comment.