-
Notifications
You must be signed in to change notification settings - Fork 960
Add gauge to time mark duration #1021
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
Conversation
metricsSystem.createLongGauge( | ||
BesuMetricCategory.PRUNER, | ||
"mark_time_duration", | ||
"Total number of seconds spent marking the state trie", |
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.
Cumulative or per marking run? Worth adding some verbiage to the help text to make it clear.
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.
resolved
@@ -94,6 +97,13 @@ public MarkSweepPruner( | |||
BesuMetricCategory.PRUNER, | |||
"sweep_operations_total", | |||
"Total number of sweep operations performed"); | |||
|
|||
markStopwatch = Stopwatch.createUnstarted(); | |||
metricsSystem.createLongGauge( |
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.
Is MarkSweepPruner a singleton for the life of the java process? Counters can handle multiple counters, gauges will throw an exception when the second gauge is created.
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.
Yup, it's a singleton
This is required to do performance monitoring/improvement of mark duration