-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Create indices for bookshelves_events table #10593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mekarpeles
merged 1 commit into
internetarchive:master
from
cdrini:feature/checkins-db-indices
Mar 18, 2025
Merged
Create indices for bookshelves_events table #10593
mekarpeles
merged 1 commit into
internetarchive:master
from
cdrini:feature/checkins-db-indices
Mar 18, 2025
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
Tested on prod, it shows a solid improvement in EXPLAIN/ANALYZE! Before: After: Query 1:
Query 2:
Query 3:
After: Query 1:
Query 2:
Query 3:
|
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.
Noticing ~1/3 of time of

/search
spent in db queries according to sentry profiles (link):I created 50k dummy data rows locally, and ran the 3 types of queries we run against this table. The one multi-index seems to have removed all Seq Scans and drastically dropped down the query time!
It might be worth experimenting with adding more indices, but this seems sufficient at the moment. And it would be good to run the below queries on ol-db1 as well before/after.
Results without index:
Query 1:
Query 2:
Query 3:
Results after creating multi-key index:
Query 1:
Query 2:
Query 3:
Technical
Testing
Screenshot
Stakeholders