Tuesday, February 26, 2013

A closer look at the performance of Google Chrome (link)

One of our upcoming projects aims to deliver a rich, real-time experience directly in the browser. In the course of this work, our engineers bumped into a series of elusive performance issues that seemed to affect only the beta testers who were using Google Chrome.

At first, we suspected that this is our fault. But when we finally looked under the hood of seemingly the fastest browser on the market, we discovered a series of design decisions that may elude conventional benchmarks, but undoubtedly affect the performance of many real-world sites all across the web.


1 comment:

  1. Maybe that kind of thing (obsessive vtable lookups) can be resolved at least partially with the link time optimizations that come with clang/llvm and newer gccs?