Page History

...

In order to submit a benchmark request you need to contact someone with write access to httpshave an access to the jenkins (  http://github.com/apache/flink/tree/benchmark-request (benchmarking codespeed.dak8s.net:8080 benchmarking infrastructure is hosted using resources outside of the Apache foundation). To get an access contact one of Apache Flink PMCs. If you already have the write access you should:

1. Push your changes to some Flink's clone github repository branch.
2. Trigger a new build on Jenkins benchmark request project. You can specify the branch and which github repository should be used for this benchmark request both for the benchmarked Flink code and the benchmark code itself.
   1. Please
   to https://github.com/apache/flink/tree/benchmark-request branch, probably using `–force` to overwrite previous changes. In this step, please
   1. make sure that nobody else is doing some benchmarking at the same time.
   You can check this by looking at the last modification date of this branch and or
   1. Benchmark runs are being queued one after another, but comparison view in the benchmarks WebUI compares only the single latest result against the latest master, so make sure you do not overwrite someone else results as he is analysing them with that someone's else knowledge. You can check who and when was doing the last comparison by looking when was the last benchmark request run on the Jenkins and who has started it. If last activity was more than a day ago, you are probably good to go. If not, please contact the person that
   made the most recent changes.Trigger a new build on Jenkins benchmark request project
   1. triggered the latest build and coordinate the efforts.
3. Once benchmark request build finishes, the results will be:
   • archived as the build artefact on the Jenkins as CSV file   
   • pushed to comparison UI

...