docs: Clarify BPF Map Pressure Metric #28682
Merged
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
BPF Map Pressure does not just measure "usage", as the current iteration of the docs suggests. It actually measures the required map size against the configured/allocated map size. This metric is useful at values >= 1.0 as it conveys the scope of the problem to users of the metric. Signed-off-by: Nate Sweet <nathanjsweet@pm.me>
|
/test |
nebril
approved these changes
Oct 19, 2023
This was referenced Oct 24, 2023
This was referenced Nov 12, 2023
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.
BPF Map Pressure does not just measure "usage",
as the current iteration of the docs suggests. It
actually measures the required map size against
the configured/allocated map size. This metric
is useful at values >= 1.0 as it conveys the scope
of the problem to users of the metric.