-
Notifications
You must be signed in to change notification settings - Fork 742
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
Register processor queue length as histogram #6012
Conversation
dc56662
to
7e86b90
Compare
7e86b90
to
5795cc6
Compare
…ocessor-queue-histogram
@@ -987,46 +1008,48 @@ impl<E: EthSpec> BeaconProcessor<E> { | |||
.map_or(false, |event| event.drop_during_sync); | |||
|
|||
let idle_tx = idle_tx.clone(); | |||
match work_event { | |||
let modified_queue_id = match work_event { |
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.
why is this variable called modified queue ID? it never gets modified
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.
This refers to what queue has been mutated by a pop operation. Tells downstream code "the queue associated with this queue ID has been mutated, so register its length"
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.
oh yeah I get you, makes sense
let's do it
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 modulo my query about variable naming
I would like to merge this ASAP so it doesn't conflict with:
@mergify queue |
🛑 The pull request has been removed from the queue
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 51091a4 |
Issue Addressed
Second attempt at
BeaconProcessor
queue lengths #4515It would be very useful to know how often queues reach zero or very high capacity values. Today we only have sparse snapshots of the queue length, which can change very rapidly in miliseconds
Proposed Changes
Register the queue length as histogram instead of a gauge.
This PR registers the length metric for a single queue instead of for all queues. Reasons why:
Metrics breaking changes
All metrics previously used to track queue lengths change. Also the type label for all metrics in the processor changes capitalization from
gossip_block
toGossipBlock
. Is that okay? Does theIntoStaticStr
macro support a different capitalization?