Fix issue #383: Optimize SQL queries for notification storm prevention #399
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.
Checklist
Reference to Existing Issue
Closes #383.
Description of Changes
This PR optimizes SQL queries in the notification system to address performance issues when sending notifications to multiple recipients. The main improvements include:
Performance Optimizations:
bulk_create()
instead of individual savesCount()
withQ()
filters instead of separate COUNT queries per recipientTechnical Changes:
notify_handler()
inhandlers.py
to use bulk creation with proper signal managementbulk_check_notification_storm_and_unread_count()
function for efficient multi-recipient storm checkingbulk_notification_update_handler()
for optimized websocket updates