48 ms·
I had a recent experience that forced me to better understand the development process of Chromium. My OpenLayers mapping application suddenly got VERY slow. t
by Waterluvian 7y ago
I had a recent experience that forced me to better understand the development process of Chromium.
My OpenLayers mapping application suddenly got VERY slow. tl;dr: Chromium team had made an optimization change to canvas `getImageData` which slowed it to ~1/40th performance in some cases. It was frustrating to have to convince them this is a problem at all.
But what frustrated me more was how they came to decide to sacrifice performance in one way to benefit it in another. I'm sure they came to the conclusion somehow, but it ended up just utterly breaking apps that are already out there. One teacher struggled with a school-board-wide course that just didn't function because the main software was broken by this.
https://bugs.chromium.org/p/chromium/issues/detail?id=1001845 https://bugs.chromium.org/p/chromium/issues/detail?id=100184...
- kevingadd 7y agogetImageData and other canvas APIs randomly regressing in performance is a common occurrence, sadly. Google frequently makes changes to the 2D graphics stack and they don't test a wide set of scenarios, just particular cherry-picked ones. Back when I still maintained some games using canvas it was pretty typical to see my framerates shift wildly every 6 weeks when a new release rode the trains. Two other scenarios that will often change in performance is canvas-to-canvas draws and canvas<->WebGL interop, because how those are implemented is complex. In the past particular behaviors would instantly disable hardware acceleration for a given canvas, tanking your performance.
- strictnein 7y ago> I'm sure they came to the conclusion somehow My money would be on that it improved performance on something google related: maps, youtube, etc