-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-13843] Optimize collectioncipher readbyuserid #4916
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4916 +/- ##
=======================================
Coverage 41.79% 41.79%
=======================================
Files 1364 1364
Lines 64003 64003
Branches 5871 5871
=======================================
Hits 26751 26751
Misses 36048 36048
Partials 1204 1204 ☔ View full report in Codecov by Sentry. |
No New Or Fixed Issues Found |
WHERE | ||
OU.[Status] = 2 | ||
AND CU.[CollectionId] IS NULL | ||
END |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⛏️ Newline at the end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
* Optimise stored procedure Collectioncipher_ReadByUserId * Optimise stored procedure Collectioncipher_ReadByUserId * Optimise stored procedure Collectioncipher_ReadByUserId
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-13843
📔 Objective
Database Optimization:
Stored procedure [Collectioncipher_ReadByUserId] has regressed in performance and is affecting CPU usage greatly. It has been rewritten to just use inner joins and a union all to maximize index usage.
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes