Optimize UpdateFolderCounters Job #4374
Merged
Conversation
This file contains 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.
Problem:
In cases where a mailbox is very active and has numerous custom folders, a high number of jobs are dispatched to update folder counts. Additionally, multiple duplicate jobs are being dispatched for the same folder, leading to unnecessary load on the system.
Solution:
A locking mechanism has been implemented to ensure that if an
UpdateFolderCountersjob for a folder already exists, no duplicate jobs are dispatched for the same folder ID.Result:
This change has significantly reduced the load on the queue system and is functioning smoothly.