top

Google retires Octane JavaScript benchmark to avoid Cheating

On 12th April 2017, Google has made a huge announcement of octane javascript benchmark which is being retired. Google says that it’s no longer useful for browser developers to optimize their engines of javascript. Octane benchmark suite was introduced in 2012 by the developers of V8 and javascript engine used in chrome. JavaScript benchmarks were initially created to measure workloads and typescripts of the compiler which were important for new cases. This change has rendered individual finite lifespans to benchmarks. Since JavaScript itself has changed in terms of the cutdown versions, the standardized version of javascript ECMAScript 2015 introduced a range of new frameworks and libraries which have emerged recently. None of these are tested by the Octane suite. First and foremost, Octane solely focuses on engine developers, which highlight the areas of improvement. But just as with Sunspider (first JavaScript benchmark) that preceded it, Google has found that optimizations have been developed to boost Octane, even if it interferes with other scenarios. The content of octane benchmark suite which measures javascript performance as follows: 1. Diminishing returns and over optimization: Octane provides a single value to the javascript virtual machine ecosystem, which provides various applications to perform.This technique helps most of the real websites load faster. This has led to a significant regression in the existing node.js applications. 2.Beyond octane and other synthetic benchmarks: Beyond octane, which enables the JS ecosystems in computationally expensive javascript to make large gains and other benchmarks investing time in understanding real-world node applications, it also measures server-side Javascript performance through workloads such as AcmeAir.

Google retires Octane JavaScript benchmark to avoid Cheating

By Geneva Clark 17th Apr, 2017
Google retires Octane JavaScript benchmark to avoid Cheating

On 12th April 2017, Google has made a huge announcement of octane javascript benchmark which is being retired. Google says that it’s no longer useful for browser developers to optimize their engines of javascript. 


Octane benchmark suite was introduced in 2012 by the developers of V8 and javascript engine used in chrome. JavaScript benchmarks were initially created to measure workloads and typescripts of the compiler which were important for new cases. This change has rendered individual finite lifespans to benchmarks. 


Since JavaScript itself has changed in terms of the cutdown versions, the standardized version of javascript ECMAScript 2015 introduced a range of new frameworks and libraries which have emerged recently. None of these are tested by the Octane suite. 


First and foremost, Octane solely focuses on engine developers, which highlight the areas of improvement. But just as with Sunspider (first JavaScript benchmark) that preceded it, Google has found that optimizations have been developed to boost Octane, even if it interferes with other scenarios. 


The content of octane benchmark suite which measures javascript performance as follows:


1. Diminishing returns and over optimization:


Octane provides a single value to the javascript virtual machine ecosystem, which provides various applications to perform.This technique helps most of the real websites load faster. This has led to a significant regression in the existing node.js applications.


2.Beyond octane and other synthetic benchmarks: 


Beyond octane, which enables the JS ecosystems in computationally expensive javascript to make large gains and other benchmarks investing time in understanding real-world node applications, it also measures server-side Javascript performance through workloads such as AcmeAir.

Geneva

Geneva Clark

Blog Author
Geneva specializes in back-end web development and has always been fascinated by the dynamic part of the web. Talk to her about modern web applications and she and loves to nerd out on all things Ruby on Rails.

Leave a Reply

Your email address will not be published. Required fields are marked *