Subject: General Tech | February 17, 2014 - 08:10 AM | Scott Michaud
Tagged: web browser, Google Chrome, chromium
This stutter was 628 milliseconds, or about 38 consecutive frames at 60 FPS.
Image Credit: Chromium Project Blog
Web browsers are designed under the assumption that a single thread of instructions will weave through every task, one by one, until everything is done. At some point, since the early 1990s, computers have been give multiple cores (and some of those designs can have multiple threads shoved through at once). The problem is now that, since "Task A" was designed to occur before "Task B", doing them separately... can break stuff good.
A simplified browser execution flowchart. Execution follows the arrow.
Image Credit: Mozilla
In case you are wondering, Mozilla started to move compilation to a background thread as of Firefox 21. Firefox 29 will move the entire just-in-time (JIT) compilation process off the main thread. This is currently in their "Aurora" release channel. To the rest of the world: it's an alpha.
This optimization is currently available in Google Chrome Beta (33).
Introduction and Design
We have our heads in the clouds. Once a dream, cloud computing is now common and used to support everything from file sharing to email. Here at PC Perspective, for example, we often make use of Dropbox. Storing certain files “in the cloud” is much easier than directly emailing them to and fro.
Google is one of the cloud’s most ardent supporters. The Internet seems to be Google’s answer to everything from emails to file sharing to document editing. All these tasks can be accomplished online through a browser with a Google utility.
When Google announced that it was going to develop an entire OS based off its Chrome web browser there was much shock, speculation and excitement. In hindsight, however, this development was probably inevitable given the company’s love of everything online. Now, Google Chrome OS is a retail product. Let’s find out if a cloud OS can compete with more traditional options.