This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[performance] Avoid resolving addresses multiple times
Parts of commhistory (GroupManager) will send a stream of resolve requests with many duplicates. This used to be tolerable because requests were handled slowly in the event loop, but now that they have higher priority it has become a problem. I went for the simple solution of ignoring requests that are identical to still-active requests (same uids, same listener, same requireComplete flag). It's not optimal (we could combine more requests into the same backend query if we tried), but it solves the problem without adding a lot of bookkeeping.
- Loading branch information
Showing
2 changed files
with
46 additions
and
1 deletion.
There are no files selected for viewing
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
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