Nowadays Google effectively working on Chrome to make it faster and apparently, the main focus lights are on Android and Mac in a set of speeds. A number of devices of Android are in working under Chrome such as Speedometer 2.1 will start running faster 30% of the benchmark. Not even this also highlights the performance of the high-end device.
However, Speedometer 2.1 has grown by 10% over the course of three months due to a series of improvements and optimizations on Chrome (for Mac):
- We discovered some targeted optimizations for the highly used JS `Object.prototype.toString` and `Array.prototype. join functions. We also implemented targeted improvements in CSS’s InterpolableColor.
- `innerHTML` is a very common way of updating the DOM via JavaScript so we added specialized fast paths for parsing.
- Pointer compression is used to save memory in both V8 and Oilpan (the garbage collector for DOM objects). We made optimizations to how we compress and decompress pointers, and we avoid compressing high-traffic fields. Given how frequently these operations are done, it has a widespread impact on performance. We also moved frequently accessed objects like JavaScript’s `undefined` to the beginning of the memory bases, allowing them to be accessed using faster machine code.
