You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Anton Kalashnikov <ka...@yandex.com> on 2022/07/05 14:09:17 UTC
[DISCUSS] Creating benchmark channel in Apache Flink slack
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
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Anton Kalashnikov <ka...@yandex.com>.
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 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,
> Qingsheng
>
>> On Jul 8, 2022, at 10:08, Xingbo Huang <hx...@gmail.com> wrote:
>>
>> +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 <ji...@ververica.com> 于2022年7月7日周四 22:41写道：
>>
>>> +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 <yu...@gmail.com> wrote:
>>>
>>>> +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 10:18 PM Martijn Visser <martijnvisser@apache.org
>>>>
>>>> wrote:
>>>>
>>>>> 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 <
>>> pnowojski@apache.org
>>>>> :
>>>>>
>>>>>> 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 <ka...@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
>>>>>>>
>>>>>>>
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Qingsheng Ren <re...@gmail.com>.
+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,
Qingsheng
> On Jul 8, 2022, at 10:08, Xingbo Huang <hx...@gmail.com> wrote:
>
> +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 <ji...@ververica.com> 于2022年7月7日周四 22:41写道：
>
>> +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 <yu...@gmail.com> wrote:
>>
>>> +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 10:18 PM Martijn Visser <martijnvisser@apache.org
>>>
>>> wrote:
>>>
>>>> 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 <
>> pnowojski@apache.org
>>>> :
>>>>
>>>>> 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 <ka...@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
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Xingbo Huang <hx...@gmail.com>.
+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 <ji...@ververica.com> 于2022年7月7日周四 22:41写道：
> +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 <yu...@gmail.com> wrote:
>
> > +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 10:18 PM Martijn Visser <martijnvisser@apache.org
> >
> > wrote:
> >
> > > 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 <
> pnowojski@apache.org
> > >:
> > >
> > > > 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 <ka...@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
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Jing Ge <ji...@ververica.com>.
+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 <yu...@gmail.com> wrote:
> +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 10:18 PM Martijn Visser <ma...@apache.org>
> wrote:
>
> > 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 <pnowojski@apache.org
> >:
> >
> > > 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 <ka...@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
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Yuan Mei <yu...@gmail.com>.
+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 10:18 PM Martijn Visser <ma...@apache.org>
wrote:
> 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 <pn...@apache.org>:
>
> > 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 <ka...@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
> > >
> > >
> >
>
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Martijn Visser <ma...@apache.org>.
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 <pn...@apache.org>:
> 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 <ka...@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
> >
> >
>
Re: [DISCUSS] Creating benchmark channel in Apache Flink slack
Posted by Piotr Nowojski <pn...@apache.org>.
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 <ka...@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
>
>