-
Notifications
You must be signed in to change notification settings - Fork 25
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
Log repostore timings #1065
base: master
Are you sure you want to change the base?
Log repostore timings #1065
Conversation
Following a chat with Giuliano, we agreed that information of this kind of much more useful as a metric than as log entry parameters. The log entries might be useful for testing/benchmarking. But from a node-operator point of view, the metrics are much more useful. We found that the default collector types are not useful in this case, so a StatSummary type was set up following the example of custom collectors from the metrics library. I bet it'll be useful in other cases as well. (Block retrieval time comes to mind!) Question is: Is it worth removing the log parameter? It doesn't really cost anything to have it. |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Signed-off-by: Ben Bierens <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Signed-off-by: Ben Bierens <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Signed-off-by: Ben Bierens <[email protected]>
This adds a quick and easy way to keep an eye on repostore performance.
Hidden behind a compile flag, enabled in the dist-test images by default.
This can be used to automatically check on the disk IO performance in cluster-test scenarios.