Speed up queries with job/app index and increase in paging size #297
Conversation
This file contains 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
Increase MAX_PAGE_SIZE from 10_000 to 100_000. The smaller limit causes a huge increase in db query time, and through inspection we have not encountered paging recently. Further inspection required, especially in scenarios with millions of jobs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The increase in paging size from 10K to 100K produces a significant speedup in job queries; in some cases, the speedup is from 30000ms to 2ms. This is in part due to a change in the query plan chosen by the DB server in these cases, and in part due to the new index.
This report was useful: https://dba.stackexchange.com/questions/213262/why-is-this-query-with-where-order-by-and-limit-so-slow