New feature idea:Benchmarker
#247
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
I propose a new feature
benchmarker
idea based on MetricsCollector #246.In the proposal of the collector, the only responsibility was to collect metrics. This is to provide a way to access metrics not only from scenarios but also from general tools.
Therefore, the Benchmarker aims to make benchmark tests easily executable by having the
Scenario
and theCollector
work together.It would be nice if it could also work well with KEP-184:scheduler-simulation.
Relates: #167
The text was updated successfully, but these errors were encountered: