feat(backend): add indexes for noteId in note_favorite and user_note_pining tables#17511
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #17511 +/- ##
===========================================
- Coverage 24.92% 24.89% -0.04%
===========================================
Files 1160 1160
Lines 39555 39553 -2
Branches 11016 11012 -4
===========================================
- Hits 9861 9845 -16
- Misses 23796 23807 +11
- Partials 5898 5901 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
|
このPRによるapi.jsonの差分 |
Contributor
Backend memory usage comparisonBefore GC
After GC
After Request
|
Member
|
👍 |
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
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.
What
note_favorite と user_note_pining にそれぞれnoteId単独のIndexを追加します。
これによりリモートノートクリーナーの削除対象検索処理が若干早くなります。
Why
fix #17508
close #17057
Additional info (optional)
ジョブで構築されるSQL相当のクエリを作成し、自分のサーバで実行計画の before / afterを取得しました。200ms弱ほど早くなっています。
…が、おひとり鯖なので利用状況に偏りがあります。あくまで参考程度に…
before
after
Checklist