overlay: cache metrics so we don't keep looking them up. #2161
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.
Description
Somewhat embarrassingly, stellar-core currently looks up a metric (due to the peer load manager) once every message read, and due to medida's not-very-fast representation of metric names and their lookup, this accounts for a nontrivial amount of CPU usage when dealing with regular network load. It's not even a different metric or a peer-specific one: we just look up the same one over and over and over.
This PR caches the lookup. Along the way it moves all the overlay metrics into their own helper struct that outlives any individual peer.
Checklist
clang-format
v5.0.0 (viamake format
or the Visual Studio extension)