-
-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(beacon-node): network worker event latency metrics #5800
Conversation
Performance Report✔️ no performance regression detected 🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
94afbec
to
2c3d7e1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should clarify in this PR if we want Sec
-suffix or not before merging it.
I think we should omit that see #5800 (comment) and conversation here #5800 (comment).
I agree with what @dapplion mentioned in #5800 (comment)
As outlined here #5800 (comment), we do not suffix metric variable names with a time unit right now, or at least not besides a few outliers. |
…ric" This reverts commit 59f12ff.
41b1d88
to
537d465
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
🎉 This PR is included in v1.12.0 🎉 |
NOTE panel updates moved to PR#5827
Motivation
Add metrics for network event latency and message port latency to network worker. Similar to how we collect data for latency across bls worker message port. Also captures latency from initial emit of network event until re-emit of event on other thread event bus.
Description
Add additional metrics to help resolve #5604