Optimize Drafts retrieval#295
Merged
Merged
Conversation
This adds a database index to speed up retrieval of Drafts. It is untested with SQLite.
Member
Author
|
Merging now. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 adds a database index to speed up retrieval of Drafts.
Most small instances won't notice any difference from this change, but it'll ensure they stay fast as they grow. It was driven by the performance issues we've encountered on Write.as as we've approached 800,000 posts on the platform. Response times for our "Drafts" page (labelled as "Posts") dropped from several seconds to under half a second with this change.
This is a draft, since it's untested with SQLite.Ready for review now.