Hi Anton, Thanks for the proposal. +1 for this. The higher visibility in the community of the benchmarks, benchmarking process and it's result the better.
Best, Piotrek wt., 5 lip 2022 o 16:10 Anton Kalashnikov <kaa....@yandex.com> napisał(a): > Hi everyone, > > > As you know, we have Flink benchmarks[1], and all of these benchmarks > constantly running several times per day. The result of this can be > found in Codespeed panel[2]. > > The problem is that only several people follow the result of these > benchmarks since it is not possible to ask everybody constantly pay > attention to this result page. > > The idea is to create `dev-benchmarks` channel(the name is discussable). > Then we can create 'Slack app'[3] for benchmarks and send the result of > each benchmark's run to this channel. > > I think it should make benchmarks more visible to the community. > > We can discuss the information that should be sent but the main idea is > to follow all fails and regression of benchmarks. > > It also makes sense to mention that right now it is easy > enough(especially after [4]) to configure our benchmarks in Jenkins > since we have all scripts in the repository. So even in the case, we > will lose our current server we can easily setup the new one. > > > WDYT? > > > [1] https://github.com/apache/flink-benchmarks > > [2] http://codespeed.dak8s.net:8000/changes/ > > [3] https://plugins.jenkins.io/slack/#plugin-content-creating-your-app > > [4] https://issues.apache.org/jira/browse/FLINK-28407 > > -- > > Best regards, > Anton Kalashnikov > >
