• Arts
• Business
• Computers
• Games
• Health
• Home
• Kids and Teens
• News
• Recreation
• Reference
• Regional
• Science
• Shopping
• Society
• Sports

Chromium Blog

tag:blogger.com,1999:blog-2471378914199150966 tag:blogger.com,1999:blog-2471378914199150966.post-5856635287663277864 Compiling in the background for a smoother user experience We aim to make Chrome the fastest browser possible. One way <a href="https://developers.google.com/v8/">V8</a> helps with this goal is by compiling JavaScript into native machine code to execute scripts quickly. Historically, Chrome compiled JavaScript on the main thread, where it could interfere with the performance of the JavaScript application. In the latest <a href="https://www.google.com/intl/en/chrome/browser/beta.html">Chrome Beta</a> we've enabled concurrent compilation, which offloads a large part of the optimizing compilation phase to a background thread. The result is that JavaScript applications remain responsive and performance gets a boost. <br /><br />Let’s have a look under the hood of V8 to understand how this works. To reduce the overall time spent compiling, V8 defers compilation of JavaScript functions until immediately before they are executed the first time. This compilation phase is fast but doesn’t focus on optimizing the code, just on getting it done quickly. In V8, pieces of code that are executed very often are compiled a second time by a specialized <a href="http://blog.chromium.org/2010/12/new-crankshaft-for-v8.html">optimizing compiler</a>. This second compilation pass makes use of many advanced optimization techniques, meaning it takes more time than the first pass but delivers much faster code. <br /><br />Until now, V8 took turns compiling optimized Javascript code and executing it. For large pieces of code this could become a nuisance, and in complex applications like games it could even lead to stuttering and dropped frames. Concurrent compilation tackles this issue. <br /><br />The grap

Contact Information