Thanks, everybody for your feedback. It seems no objections to this
proposal. So I will create the ticket with a description and start the
formal voting for this proposal.
--
Best regards,
Anton Kalashnikov
08.07.2022 04:21, Qingsheng Ren пишет:
+1 for this channel in Slack. Only few people
+1 for this channel in Slack. Only few people know the entrance to the
performance benchmark result page and posting it in a public slack channel will
attract more attention from Flink developers, also emphasis the importance of
performance issues.
Thanks for driving this Anton!
Best,
+1 for creating a public slack channel for benchmark. Like the build
channel, it will help us find potential problems before release.
Best,
Xingbo
Jing Ge 于2022年7月7日周四 22:41写道：
> +1 for moving to the public slack channel. Flink developers should pay more
> attention to the performance test.
>
+1 for moving to the public slack channel. Flink developers should pay more
attention to the performance test.
Best regards,
Jing
On Thu, Jul 7, 2022 at 2:02 PM Yuan Mei wrote:
> +1 for the proposal Anton, and thanks very much to move this effort
> forward!
>
> In long term, I think it would
+1 for the proposal Anton, and thanks very much to move this effort forward!
In long term, I think it would be helpful to ask volunteers to help
watching-out the daily micro benchmark results.
But let's make it more visible as the very first step!
Best Regards,
Yuan
On Tue, Jul 5, 2022 at
Hi Anton,
I recalled that it was brought up before and it was indeed (when the
announcement email was sent [1]).
+1 for doing this.
Best regards,
Martijn
[1] https://lists.apache.org/thread/kqjtrlnw33h1mybyx3gg4ff4390y5wbz
Op di 5 jul. 2022 om 16:12 schreef Piotr Nowojski :
> Hi Anton,
>
>
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 napisał(a):
> Hi everyone,
>
>
> As you know, we have Flink benchmarks[1], and all
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
