Skip to content

Conversation

@pnorman
Copy link
Contributor

@pnorman pnorman commented Sep 21, 2023

When these limits were set in 2008 (a16d3b7) it would take a few minutes to clear through the dirty tile queue, giving it the ability to even out load over a few minute timescale, and let the work in the queue be done when the server is no longer busy. These days, a server can clear through 1000 metatiles in seconds, meaning the queue fills up nearly instantly and starts dropping tiles.

Increasing these limits by 8x attempts to restore some of the old utility of the queue.

By my estimates, in 2008 a server might have been doing 5 metatiles/second, while now it's 100 metatiles/second.

If we were starting over, I wouldn't consider the gains of having the queue worth the additional code complexity.

When these limits were set in 2008 (a16d3b7) it would take a few
minutes to clear through the dirty tile queue, giving it the
ability to even out load over a few minute timescale, and let the
work in the queue be done when the server is no longer busy. These
days, a server can clear through 1000 metatiles in seconds, meaning
the queue fills up nearly instantly and starts dropping tiles.

Increasing these limits by 8x attempts to restore some of the old
utility of the queue.
@mboeringa
Copy link

Is anything in unmerged #152 of 2017 possibly still relevant?

@pantierra pantierra merged commit fe23892 into openstreetmap:master Sep 27, 2023
@pnorman pnorman deleted the queue_sizes branch September 27, 2023 06:54
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.

3 participants