We are about to release a new version of Hyper (probably later today) and would like to also update the ClickBench results.
I noticed that #993 put new automation in place.
Would you like us to still measure ourselves and create pull requests containing the new results?
Or should updates use the new benchmark-manual.yml Github flow? (We can't trigger flows ourselves, though, so we would need your support doing so)
Or should we pin the Hyper version in https://github.com/ClickHouse/ClickBench/blob/main/hyper/install, such that version bumps are done via explicit pull requests, which will trigger the benchmark-pr.yml Github flow?
We are about to release a new version of Hyper (probably later today) and would like to also update the ClickBench results.
I noticed that #993 put new automation in place.
Would you like us to still measure ourselves and create pull requests containing the new results?
Or should updates use the new
benchmark-manual.ymlGithub flow? (We can't trigger flows ourselves, though, so we would need your support doing so)Or should we pin the Hyper version in https://github.com/ClickHouse/ClickBench/blob/main/hyper/install, such that version bumps are done via explicit pull requests, which will trigger the
benchmark-pr.ymlGithub flow?