Fix caching problem in probegroups #416
Open
Conversation
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
There has been a long going issue, that if aggressive caching is used, the Cache is always expired if a client checks in. This is due to a bug, that clears the cache before retrieving the old information, which leads to the new groups assigned by a probe to be always new, as olddata is always []. This should fix performance for servers that are utilizing the "aggressive" caching mode.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
There has been a long going issue, that if aggressive caching is used, the Cache is always expired if a client checks in.
This is due to a bug, that clears the cache before retrieving the old information, which leads to the new groups assigned by a probe to be always new, as olddata is always [].
This should fix performance for servers that are utilizing the "aggressive" caching mode.