Aiosa

@rsimon wow looks awesome. Maybe I will try your annotations as well :)

When a canvas object is retrieved, the original image data is thrown away to avoid duplicate copies in memory. The Image getter on the older way of 'advanced data pipeline'...

Otherwise I also don't see a reason for HTML drawer...

That's how it is implemented btw within cache overhaul - conversion is done only when needed, and drawers define which formats they accept. So if you start with image data...

That would be because canvas is processed on CPU.. I think :D

Since we wanted to push v5 (at least I thought so) also with cache overhaul that deprecates `context2d` and other hack props, all these issues should resolve by themselves... Deprecation...

Nice, one thing I keep noticing is that people do tend to use `getTileUrl` for anything related to the tile fetching, rather than using `getTilePostData`. I am not sure whether...

Hmm maybe. But that description is meant for people who need to fetch basic image queries, not re-implement the fetching process as such. iMHO that's too much of a detail...

You could just try to access/view and measure loading time for each tile URL directly through developer tools in the browser. Tile URLs are in the networking tab. I bet...

> With the older SVS files, each tile takes ~20-25 ms to be read as an RGB array. With the newer SVS, this varies from 60-120 ms. Just a sidenote,...