Chrome becomes faster on Windows with Profile Guided Optimization

Google Chrome on Windows was criticized many times for its enormous RAM usage and crashes when there were a lot tabs open. Moreover Google never admitted the problem and continued to improve other aspects of the browser not taking into account the performance, and making only small changes and optimizations that weren't enough. However, with the recent releases of Chrome 53 for 64-bit Windows systems and Chrome 54 for 32-bit Windows, Google claims to have finally improved its performance significantly.

chrome-new

This was made possible by implementing the Profile Guided Optimization (PGO) mechanism available in the C++ compiler used on Windows. The secret behind it is that the browser with PGO enabled will track what features and API functions are used the most and after analyzing this data, the compiled version will optimize the code behind the most used features making it faster.

According to Google, using Microsoft's GPO has improved the startup time by 16.8% while overall page loading speed improved by 14.8%. The New Tab also loads 5.9% faster in the new versions.

To learn more about the changes behind these releases, head over to the Chromium Blog post. To get more information about the PGO optimisation mechanism you should visit this MSDN article.

3 thoughts on “Chrome becomes faster on Windows with Profile Guided Optimization

  1. Jack

    “track what features and API functions are used” – whats new in Google tracking? Oh I see, now they say its even better when they track the users! Oh wait, they have been saying this since always! Now they say its a whopping 15% better than ever before! Whatever next …

    Like or Dislike: Thumb up 2 Thumb down 0

    Reply
    1. sketch

      Is it also true for Chromium builds (http://chromium.woolyss.com/download/, https://www.chromium.org/getting-involved/download-chromium) or Vivaldi also?

      Like or Dislike: Thumb up 0 Thumb down 0

      Reply

Leave a Reply

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