Chrome canary (v32) performance increases

[Bg Sosh]

Hi,

We are seeing some very substantial performance improvements in our app running in chrome canary v32.  I'd love to understand more about why this is the case.  Have there been some big changes in the JS Engine/GC or perhaps the canvas implementation? What has changed?

Thank you!

[Adam Barth]

It's hard to know without more details of your app's workload.  There are a bunch of architectural improvements to Blink in M32, including lazyAttach and partial layout.  Those can cause large speedups on certain workloads.

Adam

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Nico Weber]

If you're really curious, you can use http://www.chromium.org/developers/bisect-builds-py to narrow down which revision caused the improvement.

[Tony Gentilcore]

Could you share a URL that demonstrates?

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Justin Novosad]

If the app in question is performing a lot of draw calls that fall outside of the bounds of the canvas, then performance may have been greatly increased due to this change: https://src.chromium.org/viewvc/blink?revision=158033&view=revision  

It is an overhaul of viewport culling (actually clip culling to be more precise) in 2D canvases.  With that change, culled draw calls get a performance boost of 3x or more.