Reduce high zoom "long tail" of jobs #370
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…for prod run, but I ran into it when testing). And added more detail on assertion failure.
iandees
approved these changes
Feb 26, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow coordinates for high zoom meta jobs to be anywhere between the
queue_zoomandgroup_by_zoom(i.e: RAWR tile zoom) inclusive. That's usually between 7 and 10, respectively. This means we can submit jobs which take a long time individually at zoom 10, rather than grouping them at zoom 7 to reduce the overall number of jobs.Connects to tilezen/tileops#17, required by tilezen/tileops#47.