Update query planner statistics of database after library scan finished #4199
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
Pull Request Test Coverage Report for Build 1133670393
💛 - Coveralls |
daschuer
reviewed
Aug 14, 2021
tools/mixxxdb_cleanup.sql
Outdated
| VACUUM; | ||
| -- Update statistics for the query planner | ||
| -- https://www.sqlite.org/lang_analyze.html | ||
| ANALYZE; |
There was a problem hiding this comment.
What is the rational for Analyze before Vacuum? I would swap it intuitively.
Can you add a comment?
There was a problem hiding this comment.
I don't know which order is correct and why to choose one over the other:
There was a problem hiding this comment.
Found it:
https://sqlite.org/forum/forumpost/62fb63a29c5f7810?t=h
Richard Hipp himself recommends to run VACCUM before ANALYZE.
Holzhaus
reviewed
Aug 15, 2021
uklotzde
changed the title
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.
This operation turned out to be crucial for achieving an acceptable performance after a mass import into aoide. Otherwise some queries took 30-90s on a large library or just stalled at 100% CPU! Though the issue might not affect Mixxx which uses a simpler schema that requires less JOINs.
The operation typically finishes after ~5-10 sec.