Skip to content

feat: add customizable delay to individual tile loading#2224

Draft
JaffaKetchup wants to merge 3 commits into
masterfrom
tile-load-delay
Draft

feat: add customizable delay to individual tile loading#2224
JaffaKetchup wants to merge 3 commits into
masterfrom
tile-load-delay

Conversation

@JaffaKetchup

Copy link
Copy Markdown
Member

Sparked by the fix #2217, and discussed with @mootw.

At the moment, tiles start loading (ignoring the influence of TileUpdateTransformer) after they become visible. If they are destroyed, then loading is stopped (assuming the tile provider can support this, which it does by default).

However, it would be better not to start loading tiles that the user is unlikely to look at. Unfortunately this is difficult to estimate. Therefore, this introduces a delay on each individual tile load.
During fast gestures, the tile will therefore be destroyed before it starts loading, which has numerous benefits (including potentially speeding up tile loading of the tiles we do want by reducing interfering network traffic, although that was reduced by the universal introduction of abortable loading).
The tradeoff is another 30 milliseconds (by default) for each tile to load, which is barely noticable, but is not insignificant in the numbers.

Minor change to Android demo app build config
@JaffaKetchup JaffaKetchup requested review from a team and mootw July 2, 2026 00:09
@JaffaKetchup JaffaKetchup marked this pull request as draft July 2, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant