-
Notifications
You must be signed in to change notification settings - Fork 141
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
Benchmark history cleanup #1074
Conversation
Do the benchmarks still run on PR branches or did we remove that and it runs just on master? |
This PR only removes the results of old PR benchmarks. For the rest I did not change anything. So when benchmarks are running is still the same. As far as I know PR benchmarks are still running. |
BTW, this is a low risk change. If it doesn't work, we can simply revert and all the data is back! 🙂 |
Also: remove data for one more `JMHSample_01_HelloWorld.wellHelloThere` benchmark
Removing these because this branch causes such a huge peak in the graph that the rest of the graph became less readable.
Benchmarks `zio.kafka.bench.ConsumersComparisonBenchmark.*` were moved to another package. By renaming the old data, these data points are joined again in the same graphs.
643b37c
to
edc41ce
Compare
One more correction in 24e7382 we get: |
This PR contains a number of commits that each clean up a part of the benchmark history:
JMHSample_01_HelloWorld.wellHelloThere
benchmarkZioKafkaNoOptimisticResumeBenchmarks
benchmark (plus one moreJMHSample_01_HelloWorld.wellHelloThere
)ZioKafkaNoPrefetchingBenchmarks
New commit interface
branch to get rid of the high peak in the graphszio.kafka.bench.ConsumersComparisonBenchmark.*
were moved to another package. By renaming the old data, these data points are joined again in the same graphs.The last step was done with a bash script and can be repeated regularly. Documentation for that will follow in a later PR.