Have monitor thread calculate hitrate using unique success packets, not filtered success packets#864
Merged
Have monitor thread calculate hitrate using unique success packets, not filtered success packets#864
Conversation
zakird
approved these changes
May 1, 2024
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
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.
Closes #863
Used
git bisectto find this bug, looks like it's been in the code since 2021. (introduced in commita66169).We want to calculate hit-rate using the de-duplicated success packets. By using
filter_success, the default behavior is to not de-duplicate responses. This led to the wild hit-rates.Testing
mainPhillip/863(with fix)v2.1.1(old behavior)