Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Nice ! Thank you and everyone involved for the hard work. Etienne Le 19/10/2023 à 10:24, Zakelly Lan a écrit : Hi everyone, Flink benchmarks [1] generate daily performance reports in the Apache Flink slack channel (#flink-dev-benchmarks) to detect performance regression [2]. Those benchmarks previously were running on several machines donated and maintained by Ververica. Unfortunately, those machines were gone due to account issues [3] and the benchmarks daily run stopped since August 24th delaying the release of Flink 1.18 a bit. [4]. Ververica donated several new machines! After several weeks of work, I have successfully re-established the codespeed panel and benchmark daily run pipelines on them. At this time, we are pleased to announce that the Flink Speed Center and benchmark pipelines are back online. These new machines have a more formal management to ensure that previous accidents will not occur in the future. What's more, I successfully recovered historical data backed up by Yanfei Lei [5]. So with the old domain [6] redirected to the new machines, the old links that existed in previous records will still be valid. Besides the benchmarks with Java8 and Java11, I also added a pipeline for Java17 running daily. How to use it: We also registered a new domain name 'flink-speed.xyz' for the Flink Speed Center [7]. It is recommended to use the new domain in the future. Currently, the self-service method of triggering benchmarks is unavailable considering the lack of resources and potential vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to submit a benchmark. More info is updated on the wiki[8]. Daily Monitoring: The performance daily monitoring on the Apache Flink slack channel [2] is still unavailable as the benchmark results need more time to stabilize in the new environment. Once the baseline results become available for regression detection, I will enable the daily monitoring. Please feel free to reach out to me if you have any suggestions or questions. Thanks Ververica again for denoting machines! Best, Zakelly [1]https://github.com/apache/flink-benchmarks [2]https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj [3]https://issues.apache.org/jira/browse/FLINK-33052 [4]https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 [5]https://issues.apache.org/jira/browse/FLINK-30890 [6]http://codespeed.dak8s.net:8000 [7]http://flink-speed.xyz [8]https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks Zakelly for the great work! On Fri, Oct 20, 2023 at 5:05 PM Rui Fan <1996fan...@gmail.com> wrote: > Thanks for your effort! It's very useful when some new commits affect > performance. > > Best, > Rui > > On Fri, Oct 20, 2023 at 4:42 PM Yanfei Lei wrote: > > > Thanks for your hard work! > > Looking forward to the daily monitoring being available again soon. > > > > Best, > > Yanfei > > > > Yuan Mei 于2023年10月20日周五 16:19写道： > > > > > > Thank you for your great efforts! > > > > > > Best > > > Yuan > > > > > > On Fri, Oct 20, 2023 at 4:08 PM Sergey Nuyanzin > > wrote: > > > > > > > Thanks a lot for working on this! > > > > > > > > On Fri, Oct 20, 2023 at 9:27 AM Yangze Guo > wrote: > > > > > > > > > Thanks for the effort, Zhaoqian! > > > > > > > > > > Best, > > > > > Yangze Guo > > > > > > > > > > On Fri, Oct 20, 2023 at 2:55 PM Leonard Xu > > wrote: > > > > > > > > > > > > Thanks Zakelly for the great work. > > > > > > > > > > > > Best, > > > > > > Leonard > > > > > > > > > > > > > 2023年10月19日 下午7:39，Jing Ge 写道： > > > > > > > > > > > > > > Hi Zakelly, > > > > > > > > > > > > > > Thank you for your effort! Really appreciate it! > > > > > > > > > > > > > > Best regards, > > > > > > > Jing > > > > > > > > > > > > > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang > > wrote: > > > > > > > > > > > > > >> Thanks for Zakelly's great work! > > > > > > >> > > > > > > >> > > > > > > >> Best > > > > > > >> Yun Tang > > > > > > >> > > > > > > >> From: Piotr Nowojski > > > > > > >> Sent: Thursday, October 19, 2023 17:56 > > > > > > >> To: dev@flink.apache.org > > > > > > >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark > > daily > > > > > run are > > > > > > >> back online > > > > > > >> > > > > > > >> Thank you! > > > > > > >> > > > > > > >> czw., 19 paź 2023 o 11:31 Konstantin Knauf > > > > > > napisał(a): > > > > > > >> > > > > > > >>> Thanks a lot for working on this! > > > > > > >>> > > > > > > >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > > > > > > >>> zakelly@gmail.com>: > > > > > > >>> > > > > > > Hi everyone, > > > > > > > > > > > > Flink benchmarks [1] generate daily performance reports in > the > > > > > Apache > > > > > > Flink slack channel (#flink-dev-benchmarks) to detect > > performance > > > > > > regression [2]. Those benchmarks previously were running on > > > > several > > > > > > machines donated and maintained by Ververica. Unfortunately, > > those > > > > > > machines were gone due to account issues [3] and the > > benchmarks > > > > > daily > > > > > > run stopped since August 24th delaying the release of Flink > > 1.18 a > > > > > > bit. [4]. > > > > > > > > > > > > Ververica donated several new machines! After several weeks > of > > > > > work, I > > > > > > have successfully re-established the codespeed panel and > > benchmark > > > > > > daily run pipelines on them. At this time, we are pleased to > > > > > announce > > > > > > that the Flink Speed Center and benchmark pipelines are back > > > > online. > > > > > > These new machines have a more formal management to ensure > > that > > > > > > previous accidents will not occur in the future. > > > > > > > > > > > > What's more, I successfully recovered historical data backed > > up by > > > > > > Yanfei Lei [5]. So with the old domain [6] redirected to the > > new > > > > > > machines, the old links that existed in previous records > will > > > > still > > > > > be > > > > > > valid. Besides the benchmarks with Java8 and Java11, I also > > added > > > > a > > > > > > pipeline for Java17 running daily. > > > > > > > > > > > > How to use it: > > > > > > We also registered a new domain name 'flink-speed.xyz' for > > the > > > > > Flink > > > > > > Speed Center [7]. It is recommended to use the new domain in > > the > > > > > > future. Currently, the self-service method of triggering > > > > benchmarks > > > > > is > > > > > > unavailable considering the lack of resources and potential > > > > > > vulnerabilities of Jenkins. Please contact one of Apache > Flink > > > > PMCs > > > > > to > > > > > > submit a benchmark. More info is updated on the wiki[8]. > > > > > > > > > > > > Daily Monitoring: > > > > > > The performance daily monitoring on the Apache Flink slack > > channel > > > > > [2] > > > > > > is still unavailable as the benchmark results need more time > > to > > > > > > stabilize in the new environment. Once the baseline results > > become > > > > > > available for regression detection, I will enable the daily > > > > > > monitoring. > > > > > > > > > > > > Please feel free to reach out to me if you have any > > suggestions or > > > > > > questions. Thanks Ververica again for denoting machines! > > > > > > > > > > > > > > > > > > Best, > > > >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks for your effort! It's very useful when some new commits affect performance. Best, Rui On Fri, Oct 20, 2023 at 4:42 PM Yanfei Lei wrote: > Thanks for your hard work! > Looking forward to the daily monitoring being available again soon. > > Best, > Yanfei > > Yuan Mei 于2023年10月20日周五 16:19写道： > > > > Thank you for your great efforts! > > > > Best > > Yuan > > > > On Fri, Oct 20, 2023 at 4:08 PM Sergey Nuyanzin > wrote: > > > > > Thanks a lot for working on this! > > > > > > On Fri, Oct 20, 2023 at 9:27 AM Yangze Guo wrote: > > > > > > > Thanks for the effort, Zhaoqian! > > > > > > > > Best, > > > > Yangze Guo > > > > > > > > On Fri, Oct 20, 2023 at 2:55 PM Leonard Xu > wrote: > > > > > > > > > > Thanks Zakelly for the great work. > > > > > > > > > > Best, > > > > > Leonard > > > > > > > > > > > 2023年10月19日 下午7:39，Jing Ge 写道： > > > > > > > > > > > > Hi Zakelly, > > > > > > > > > > > > Thank you for your effort! Really appreciate it! > > > > > > > > > > > > Best regards, > > > > > > Jing > > > > > > > > > > > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang > wrote: > > > > > > > > > > > >> Thanks for Zakelly's great work! > > > > > >> > > > > > >> > > > > > >> Best > > > > > >> Yun Tang > > > > > >> > > > > > >> From: Piotr Nowojski > > > > > >> Sent: Thursday, October 19, 2023 17:56 > > > > > >> To: dev@flink.apache.org > > > > > >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark > daily > > > > run are > > > > > >> back online > > > > > >> > > > > > >> Thank you! > > > > > >> > > > > > >> czw., 19 paź 2023 o 11:31 Konstantin Knauf > > > > napisał(a): > > > > > >> > > > > > >>> Thanks a lot for working on this! > > > > > >>> > > > > > >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > > > > > >>> zakelly@gmail.com>: > > > > > >>> > > > > > Hi everyone, > > > > > > > > > > Flink benchmarks [1] generate daily performance reports in the > > > > Apache > > > > > Flink slack channel (#flink-dev-benchmarks) to detect > performance > > > > > regression [2]. Those benchmarks previously were running on > > > several > > > > > machines donated and maintained by Ververica. Unfortunately, > those > > > > > machines were gone due to account issues [3] and the > benchmarks > > > > daily > > > > > run stopped since August 24th delaying the release of Flink > 1.18 a > > > > > bit. [4]. > > > > > > > > > > Ververica donated several new machines! After several weeks of > > > > work, I > > > > > have successfully re-established the codespeed panel and > benchmark > > > > > daily run pipelines on them. At this time, we are pleased to > > > > announce > > > > > that the Flink Speed Center and benchmark pipelines are back > > > online. > > > > > These new machines have a more formal management to ensure > that > > > > > previous accidents will not occur in the future. > > > > > > > > > > What's more, I successfully recovered historical data backed > up by > > > > > Yanfei Lei [5]. So with the old domain [6] redirected to the > new > > > > > machines, the old links that existed in previous records will > > > still > > > > be > > > > > valid. Besides the benchmarks with Java8 and Java11, I also > added > > > a > > > > > pipeline for Java17 running daily. > > > > > > > > > > How to use it: > > > > > We also registered a new domain name 'flink-speed.xyz' for > the > > > > Flink > > > > > Speed Center [7]. It is recommended to use the new domain in > the > > > > > future. Currently, the self-service method of triggering > > > benchmarks > > > > is > > > > > unavailable considering the lack of resources and potential > > > > > vulnerabilities of Jenkins. Please contact one of Apache Flink > > > PMCs > > > > to > > > > > submit a benchmark. More info is updated on the wiki[8]. > > > > > > > > > > Daily Monitoring: > > > > > The performance daily monitoring on the Apache Flink slack > channel > > > > [2] > > > > > is still unavailable as the benchmark results need more time > to > > > > > stabilize in the new environment. Once the baseline results > become > > > > > available for regression detection, I will enable the daily > > > > > monitoring. > > > > > > > > > > Please feel free to reach out to me if you have any > suggestions or > > > > > questions. Thanks Ververica again for denoting machines! > > > > > > > > > > > > > > > Best, > > > > > Zakelly > > > > > > > > > > [1] https://github.com/apache/flink-benchmarks > > > > > [2] > > > > https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > > > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > > > > [4] > > > > https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > > > > [5] https://issues.apache.org/jira/browse/FLINK-30890 >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks for your hard work! Looking forward to the daily monitoring being available again soon. Best, Yanfei Yuan Mei 于2023年10月20日周五 16:19写道： > > Thank you for your great efforts! > > Best > Yuan > > On Fri, Oct 20, 2023 at 4:08 PM Sergey Nuyanzin wrote: > > > Thanks a lot for working on this! > > > > On Fri, Oct 20, 2023 at 9:27 AM Yangze Guo wrote: > > > > > Thanks for the effort, Zhaoqian! > > > > > > Best, > > > Yangze Guo > > > > > > On Fri, Oct 20, 2023 at 2:55 PM Leonard Xu wrote: > > > > > > > > Thanks Zakelly for the great work. > > > > > > > > Best, > > > > Leonard > > > > > > > > > 2023年10月19日 下午7:39，Jing Ge 写道： > > > > > > > > > > Hi Zakelly, > > > > > > > > > > Thank you for your effort! Really appreciate it! > > > > > > > > > > Best regards, > > > > > Jing > > > > > > > > > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote: > > > > > > > > > >> Thanks for Zakelly's great work! > > > > >> > > > > >> > > > > >> Best > > > > >> Yun Tang > > > > >> > > > > >> From: Piotr Nowojski > > > > >> Sent: Thursday, October 19, 2023 17:56 > > > > >> To: dev@flink.apache.org > > > > >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily > > > run are > > > > >> back online > > > > >> > > > > >> Thank you! > > > > >> > > > > >> czw., 19 paź 2023 o 11:31 Konstantin Knauf > > > napisał(a): > > > > >> > > > > >>> Thanks a lot for working on this! > > > > >>> > > > > >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > > > > >>> zakelly@gmail.com>: > > > > >>> > > > > Hi everyone, > > > > > > > > Flink benchmarks [1] generate daily performance reports in the > > > Apache > > > > Flink slack channel (#flink-dev-benchmarks) to detect performance > > > > regression [2]. Those benchmarks previously were running on > > several > > > > machines donated and maintained by Ververica. Unfortunately, those > > > > machines were gone due to account issues [3] and the benchmarks > > > daily > > > > run stopped since August 24th delaying the release of Flink 1.18 a > > > > bit. [4]. > > > > > > > > Ververica donated several new machines! After several weeks of > > > work, I > > > > have successfully re-established the codespeed panel and benchmark > > > > daily run pipelines on them. At this time, we are pleased to > > > announce > > > > that the Flink Speed Center and benchmark pipelines are back > > online. > > > > These new machines have a more formal management to ensure that > > > > previous accidents will not occur in the future. > > > > > > > > What's more, I successfully recovered historical data backed up by > > > > Yanfei Lei [5]. So with the old domain [6] redirected to the new > > > > machines, the old links that existed in previous records will > > still > > > be > > > > valid. Besides the benchmarks with Java8 and Java11, I also added > > a > > > > pipeline for Java17 running daily. > > > > > > > > How to use it: > > > > We also registered a new domain name 'flink-speed.xyz' for the > > > Flink > > > > Speed Center [7]. It is recommended to use the new domain in the > > > > future. Currently, the self-service method of triggering > > benchmarks > > > is > > > > unavailable considering the lack of resources and potential > > > > vulnerabilities of Jenkins. Please contact one of Apache Flink > > PMCs > > > to > > > > submit a benchmark. More info is updated on the wiki[8]. > > > > > > > > Daily Monitoring: > > > > The performance daily monitoring on the Apache Flink slack channel > > > [2] > > > > is still unavailable as the benchmark results need more time to > > > > stabilize in the new environment. Once the baseline results become > > > > available for regression detection, I will enable the daily > > > > monitoring. > > > > > > > > Please feel free to reach out to me if you have any suggestions or > > > > questions. Thanks Ververica again for denoting machines! > > > > > > > > > > > > Best, > > > > Zakelly > > > > > > > > [1] https://github.com/apache/flink-benchmarks > > > > [2] > > > https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > > > [4] > > > https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > > > [5] https://issues.apache.org/jira/browse/FLINK-30890 > > > > [6] http://codespeed.dak8s.net:8000 > > > > [7] http://flink-speed.xyz > > > > [8] > > > > > > > > >>> > > > > >> > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > > > > > > >>> > > > > >>> > > > > >>> -- > > > > >>> https://twitter.com/snntrable > > > > >>> https://github.com/knaufk > > > > >>> > > > > >> > > > > > > > > > > > > > -- > > Best regards, > > Sergey > >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thank you for your great efforts! Best Yuan On Fri, Oct 20, 2023 at 4:08 PM Sergey Nuyanzin wrote: > Thanks a lot for working on this! > > On Fri, Oct 20, 2023 at 9:27 AM Yangze Guo wrote: > > > Thanks for the effort, Zhaoqian! > > > > Best, > > Yangze Guo > > > > On Fri, Oct 20, 2023 at 2:55 PM Leonard Xu wrote: > > > > > > Thanks Zakelly for the great work. > > > > > > Best, > > > Leonard > > > > > > > 2023年10月19日 下午7:39，Jing Ge 写道： > > > > > > > > Hi Zakelly, > > > > > > > > Thank you for your effort! Really appreciate it! > > > > > > > > Best regards, > > > > Jing > > > > > > > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote: > > > > > > > >> Thanks for Zakelly's great work! > > > >> > > > >> > > > >> Best > > > >> Yun Tang > > > >> > > > >> From: Piotr Nowojski > > > >> Sent: Thursday, October 19, 2023 17:56 > > > >> To: dev@flink.apache.org > > > >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily > > run are > > > >> back online > > > >> > > > >> Thank you! > > > >> > > > >> czw., 19 paź 2023 o 11:31 Konstantin Knauf > > napisał(a): > > > >> > > > >>> Thanks a lot for working on this! > > > >>> > > > >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > > > >>> zakelly@gmail.com>: > > > >>> > > > Hi everyone, > > > > > > Flink benchmarks [1] generate daily performance reports in the > > Apache > > > Flink slack channel (#flink-dev-benchmarks) to detect performance > > > regression [2]. Those benchmarks previously were running on > several > > > machines donated and maintained by Ververica. Unfortunately, those > > > machines were gone due to account issues [3] and the benchmarks > > daily > > > run stopped since August 24th delaying the release of Flink 1.18 a > > > bit. [4]. > > > > > > Ververica donated several new machines! After several weeks of > > work, I > > > have successfully re-established the codespeed panel and benchmark > > > daily run pipelines on them. At this time, we are pleased to > > announce > > > that the Flink Speed Center and benchmark pipelines are back > online. > > > These new machines have a more formal management to ensure that > > > previous accidents will not occur in the future. > > > > > > What's more, I successfully recovered historical data backed up by > > > Yanfei Lei [5]. So with the old domain [6] redirected to the new > > > machines, the old links that existed in previous records will > still > > be > > > valid. Besides the benchmarks with Java8 and Java11, I also added > a > > > pipeline for Java17 running daily. > > > > > > How to use it: > > > We also registered a new domain name 'flink-speed.xyz' for the > > Flink > > > Speed Center [7]. It is recommended to use the new domain in the > > > future. Currently, the self-service method of triggering > benchmarks > > is > > > unavailable considering the lack of resources and potential > > > vulnerabilities of Jenkins. Please contact one of Apache Flink > PMCs > > to > > > submit a benchmark. More info is updated on the wiki[8]. > > > > > > Daily Monitoring: > > > The performance daily monitoring on the Apache Flink slack channel > > [2] > > > is still unavailable as the benchmark results need more time to > > > stabilize in the new environment. Once the baseline results become > > > available for regression detection, I will enable the daily > > > monitoring. > > > > > > Please feel free to reach out to me if you have any suggestions or > > > questions. Thanks Ververica again for denoting machines! > > > > > > > > > Best, > > > Zakelly > > > > > > [1] https://github.com/apache/flink-benchmarks > > > [2] > > https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > > [4] > > https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > > [5] https://issues.apache.org/jira/browse/FLINK-30890 > > > [6] http://codespeed.dak8s.net:8000 > > > [7] http://flink-speed.xyz > > > [8] > > > > > > >>> > > > >> > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > > > > >>> > > > >>> > > > >>> -- > > > >>> https://twitter.com/snntrable > > > >>> https://github.com/knaufk > > > >>> > > > >> > > > > > > > > -- > Best regards, > Sergey >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks a lot for working on this! On Fri, Oct 20, 2023 at 9:27 AM Yangze Guo wrote: > Thanks for the effort, Zhaoqian! > > Best, > Yangze Guo > > On Fri, Oct 20, 2023 at 2:55 PM Leonard Xu wrote: > > > > Thanks Zakelly for the great work. > > > > Best, > > Leonard > > > > > 2023年10月19日 下午7:39，Jing Ge 写道： > > > > > > Hi Zakelly, > > > > > > Thank you for your effort! Really appreciate it! > > > > > > Best regards, > > > Jing > > > > > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote: > > > > > >> Thanks for Zakelly's great work! > > >> > > >> > > >> Best > > >> Yun Tang > > >> > > >> From: Piotr Nowojski > > >> Sent: Thursday, October 19, 2023 17:56 > > >> To: dev@flink.apache.org > > >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily > run are > > >> back online > > >> > > >> Thank you! > > >> > > >> czw., 19 paź 2023 o 11:31 Konstantin Knauf > napisał(a): > > >> > > >>> Thanks a lot for working on this! > > >>> > > >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > > >>> zakelly@gmail.com>: > > >>> > > Hi everyone, > > > > Flink benchmarks [1] generate daily performance reports in the > Apache > > Flink slack channel (#flink-dev-benchmarks) to detect performance > > regression [2]. Those benchmarks previously were running on several > > machines donated and maintained by Ververica. Unfortunately, those > > machines were gone due to account issues [3] and the benchmarks > daily > > run stopped since August 24th delaying the release of Flink 1.18 a > > bit. [4]. > > > > Ververica donated several new machines! After several weeks of > work, I > > have successfully re-established the codespeed panel and benchmark > > daily run pipelines on them. At this time, we are pleased to > announce > > that the Flink Speed Center and benchmark pipelines are back online. > > These new machines have a more formal management to ensure that > > previous accidents will not occur in the future. > > > > What's more, I successfully recovered historical data backed up by > > Yanfei Lei [5]. So with the old domain [6] redirected to the new > > machines, the old links that existed in previous records will still > be > > valid. Besides the benchmarks with Java8 and Java11, I also added a > > pipeline for Java17 running daily. > > > > How to use it: > > We also registered a new domain name 'flink-speed.xyz' for the > Flink > > Speed Center [7]. It is recommended to use the new domain in the > > future. Currently, the self-service method of triggering benchmarks > is > > unavailable considering the lack of resources and potential > > vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs > to > > submit a benchmark. More info is updated on the wiki[8]. > > > > Daily Monitoring: > > The performance daily monitoring on the Apache Flink slack channel > [2] > > is still unavailable as the benchmark results need more time to > > stabilize in the new environment. Once the baseline results become > > available for regression detection, I will enable the daily > > monitoring. > > > > Please feel free to reach out to me if you have any suggestions or > > questions. Thanks Ververica again for denoting machines! > > > > > > Best, > > Zakelly > > > > [1] https://github.com/apache/flink-benchmarks > > [2] > https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > [4] > https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > [5] https://issues.apache.org/jira/browse/FLINK-30890 > > [6] http://codespeed.dak8s.net:8000 > > [7] http://flink-speed.xyz > > [8] > > > > >>> > > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > > >>> > > >>> > > >>> -- > > >>> https://twitter.com/snntrable > > >>> https://github.com/knaufk > > >>> > > >> > > > -- Best regards, Sergey
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks for the effort, Zhaoqian! Best, Yangze Guo On Fri, Oct 20, 2023 at 2:55 PM Leonard Xu wrote: > > Thanks Zakelly for the great work. > > Best, > Leonard > > > 2023年10月19日 下午7:39，Jing Ge 写道： > > > > Hi Zakelly, > > > > Thank you for your effort! Really appreciate it! > > > > Best regards, > > Jing > > > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote: > > > >> Thanks for Zakelly's great work! > >> > >> > >> Best > >> Yun Tang > >> > >> From: Piotr Nowojski > >> Sent: Thursday, October 19, 2023 17:56 > >> To: dev@flink.apache.org > >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are > >> back online > >> > >> Thank you! > >> > >> czw., 19 paź 2023 o 11:31 Konstantin Knauf napisał(a): > >> > >>> Thanks a lot for working on this! > >>> > >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > >>> zakelly@gmail.com>: > >>> > Hi everyone, > > Flink benchmarks [1] generate daily performance reports in the Apache > Flink slack channel (#flink-dev-benchmarks) to detect performance > regression [2]. Those benchmarks previously were running on several > machines donated and maintained by Ververica. Unfortunately, those > machines were gone due to account issues [3] and the benchmarks daily > run stopped since August 24th delaying the release of Flink 1.18 a > bit. [4]. > > Ververica donated several new machines! After several weeks of work, I > have successfully re-established the codespeed panel and benchmark > daily run pipelines on them. At this time, we are pleased to announce > that the Flink Speed Center and benchmark pipelines are back online. > These new machines have a more formal management to ensure that > previous accidents will not occur in the future. > > What's more, I successfully recovered historical data backed up by > Yanfei Lei [5]. So with the old domain [6] redirected to the new > machines, the old links that existed in previous records will still be > valid. Besides the benchmarks with Java8 and Java11, I also added a > pipeline for Java17 running daily. > > How to use it: > We also registered a new domain name 'flink-speed.xyz' for the Flink > Speed Center [7]. It is recommended to use the new domain in the > future. Currently, the self-service method of triggering benchmarks is > unavailable considering the lack of resources and potential > vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to > submit a benchmark. More info is updated on the wiki[8]. > > Daily Monitoring: > The performance daily monitoring on the Apache Flink slack channel [2] > is still unavailable as the benchmark results need more time to > stabilize in the new environment. Once the baseline results become > available for regression detection, I will enable the daily > monitoring. > > Please feel free to reach out to me if you have any suggestions or > questions. Thanks Ververica again for denoting machines! > > > Best, > Zakelly > > [1] https://github.com/apache/flink-benchmarks > [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > [3] https://issues.apache.org/jira/browse/FLINK-33052 > [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > [5] https://issues.apache.org/jira/browse/FLINK-30890 > [6] http://codespeed.dak8s.net:8000 > [7] http://flink-speed.xyz > [8] > > >>> > >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > >>> > >>> > >>> -- > >>> https://twitter.com/snntrable > >>> https://github.com/knaufk > >>> > >> >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks Zakelly for the great work. Best, Leonard > 2023年10月19日 下午7:39，Jing Ge 写道： > > Hi Zakelly, > > Thank you for your effort! Really appreciate it! > > Best regards, > Jing > > On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote: > >> Thanks for Zakelly's great work! >> >> >> Best >> Yun Tang >> >> From: Piotr Nowojski >> Sent: Thursday, October 19, 2023 17:56 >> To: dev@flink.apache.org >> Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are >> back online >> >> Thank you! >> >> czw., 19 paź 2023 o 11:31 Konstantin Knauf napisał(a): >> >>> Thanks a lot for working on this! >>> >>> Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < >>> zakelly@gmail.com>: >>> Hi everyone, Flink benchmarks [1] generate daily performance reports in the Apache Flink slack channel (#flink-dev-benchmarks) to detect performance regression [2]. Those benchmarks previously were running on several machines donated and maintained by Ververica. Unfortunately, those machines were gone due to account issues [3] and the benchmarks daily run stopped since August 24th delaying the release of Flink 1.18 a bit. [4]. Ververica donated several new machines! After several weeks of work, I have successfully re-established the codespeed panel and benchmark daily run pipelines on them. At this time, we are pleased to announce that the Flink Speed Center and benchmark pipelines are back online. These new machines have a more formal management to ensure that previous accidents will not occur in the future. What's more, I successfully recovered historical data backed up by Yanfei Lei [5]. So with the old domain [6] redirected to the new machines, the old links that existed in previous records will still be valid. Besides the benchmarks with Java8 and Java11, I also added a pipeline for Java17 running daily. How to use it: We also registered a new domain name 'flink-speed.xyz' for the Flink Speed Center [7]. It is recommended to use the new domain in the future. Currently, the self-service method of triggering benchmarks is unavailable considering the lack of resources and potential vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to submit a benchmark. More info is updated on the wiki[8]. Daily Monitoring: The performance daily monitoring on the Apache Flink slack channel [2] is still unavailable as the benchmark results need more time to stabilize in the new environment. Once the baseline results become available for regression detection, I will enable the daily monitoring. Please feel free to reach out to me if you have any suggestions or questions. Thanks Ververica again for denoting machines! Best, Zakelly [1] https://github.com/apache/flink-benchmarks [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj [3] https://issues.apache.org/jira/browse/FLINK-33052 [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 [5] https://issues.apache.org/jira/browse/FLINK-30890 [6] http://codespeed.dak8s.net:8000 [7] http://flink-speed.xyz [8] >>> >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 >>> >>> >>> -- >>> https://twitter.com/snntrable >>> https://github.com/knaufk >>> >>
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Hi Zakelly, Thank you for your effort! Really appreciate it! Best regards, Jing On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote: > Thanks for Zakelly's great work! > > > Best > Yun Tang > > From: Piotr Nowojski > Sent: Thursday, October 19, 2023 17:56 > To: dev@flink.apache.org > Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are > back online > > Thank you! > > czw., 19 paź 2023 o 11:31 Konstantin Knauf napisał(a): > > > Thanks a lot for working on this! > > > > Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > > zakelly@gmail.com>: > > > > > Hi everyone, > > > > > > Flink benchmarks [1] generate daily performance reports in the Apache > > > Flink slack channel (#flink-dev-benchmarks) to detect performance > > > regression [2]. Those benchmarks previously were running on several > > > machines donated and maintained by Ververica. Unfortunately, those > > > machines were gone due to account issues [3] and the benchmarks daily > > > run stopped since August 24th delaying the release of Flink 1.18 a > > > bit. [4]. > > > > > > Ververica donated several new machines! After several weeks of work, I > > > have successfully re-established the codespeed panel and benchmark > > > daily run pipelines on them. At this time, we are pleased to announce > > > that the Flink Speed Center and benchmark pipelines are back online. > > > These new machines have a more formal management to ensure that > > > previous accidents will not occur in the future. > > > > > > What's more, I successfully recovered historical data backed up by > > > Yanfei Lei [5]. So with the old domain [6] redirected to the new > > > machines, the old links that existed in previous records will still be > > > valid. Besides the benchmarks with Java8 and Java11, I also added a > > > pipeline for Java17 running daily. > > > > > > How to use it: > > > We also registered a new domain name 'flink-speed.xyz' for the Flink > > > Speed Center [7]. It is recommended to use the new domain in the > > > future. Currently, the self-service method of triggering benchmarks is > > > unavailable considering the lack of resources and potential > > > vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to > > > submit a benchmark. More info is updated on the wiki[8]. > > > > > > Daily Monitoring: > > > The performance daily monitoring on the Apache Flink slack channel [2] > > > is still unavailable as the benchmark results need more time to > > > stabilize in the new environment. Once the baseline results become > > > available for regression detection, I will enable the daily > > > monitoring. > > > > > > Please feel free to reach out to me if you have any suggestions or > > > questions. Thanks Ververica again for denoting machines! > > > > > > > > > Best, > > > Zakelly > > > > > > [1] https://github.com/apache/flink-benchmarks > > > [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > > [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > > [5] https://issues.apache.org/jira/browse/FLINK-30890 > > > [6] http://codespeed.dak8s.net:8000 > > > [7] http://flink-speed.xyz > > > [8] > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > > > > > > > -- > > https://twitter.com/snntrable > > https://github.com/knaufk > > >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks for Zakelly's great work! Best Yun Tang From: Piotr Nowojski Sent: Thursday, October 19, 2023 17:56 To: dev@flink.apache.org Subject: Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online Thank you! czw., 19 paź 2023 o 11:31 Konstantin Knauf napisał(a): > Thanks a lot for working on this! > > Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > zakelly@gmail.com>: > > > Hi everyone, > > > > Flink benchmarks [1] generate daily performance reports in the Apache > > Flink slack channel (#flink-dev-benchmarks) to detect performance > > regression [2]. Those benchmarks previously were running on several > > machines donated and maintained by Ververica. Unfortunately, those > > machines were gone due to account issues [3] and the benchmarks daily > > run stopped since August 24th delaying the release of Flink 1.18 a > > bit. [4]. > > > > Ververica donated several new machines! After several weeks of work, I > > have successfully re-established the codespeed panel and benchmark > > daily run pipelines on them. At this time, we are pleased to announce > > that the Flink Speed Center and benchmark pipelines are back online. > > These new machines have a more formal management to ensure that > > previous accidents will not occur in the future. > > > > What's more, I successfully recovered historical data backed up by > > Yanfei Lei [5]. So with the old domain [6] redirected to the new > > machines, the old links that existed in previous records will still be > > valid. Besides the benchmarks with Java8 and Java11, I also added a > > pipeline for Java17 running daily. > > > > How to use it: > > We also registered a new domain name 'flink-speed.xyz' for the Flink > > Speed Center [7]. It is recommended to use the new domain in the > > future. Currently, the self-service method of triggering benchmarks is > > unavailable considering the lack of resources and potential > > vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to > > submit a benchmark. More info is updated on the wiki[8]. > > > > Daily Monitoring: > > The performance daily monitoring on the Apache Flink slack channel [2] > > is still unavailable as the benchmark results need more time to > > stabilize in the new environment. Once the baseline results become > > available for regression detection, I will enable the daily > > monitoring. > > > > Please feel free to reach out to me if you have any suggestions or > > questions. Thanks Ververica again for denoting machines! > > > > > > Best, > > Zakelly > > > > [1] https://github.com/apache/flink-benchmarks > > [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > [5] https://issues.apache.org/jira/browse/FLINK-30890 > > [6] http://codespeed.dak8s.net:8000 > > [7] http://flink-speed.xyz > > [8] > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > > > -- > https://twitter.com/snntrable > https://github.com/knaufk >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thank you! czw., 19 paź 2023 o 11:31 Konstantin Knauf napisał(a): > Thanks a lot for working on this! > > Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < > zakelly@gmail.com>: > > > Hi everyone, > > > > Flink benchmarks [1] generate daily performance reports in the Apache > > Flink slack channel (#flink-dev-benchmarks) to detect performance > > regression [2]. Those benchmarks previously were running on several > > machines donated and maintained by Ververica. Unfortunately, those > > machines were gone due to account issues [3] and the benchmarks daily > > run stopped since August 24th delaying the release of Flink 1.18 a > > bit. [4]. > > > > Ververica donated several new machines! After several weeks of work, I > > have successfully re-established the codespeed panel and benchmark > > daily run pipelines on them. At this time, we are pleased to announce > > that the Flink Speed Center and benchmark pipelines are back online. > > These new machines have a more formal management to ensure that > > previous accidents will not occur in the future. > > > > What's more, I successfully recovered historical data backed up by > > Yanfei Lei [5]. So with the old domain [6] redirected to the new > > machines, the old links that existed in previous records will still be > > valid. Besides the benchmarks with Java8 and Java11, I also added a > > pipeline for Java17 running daily. > > > > How to use it: > > We also registered a new domain name 'flink-speed.xyz' for the Flink > > Speed Center [7]. It is recommended to use the new domain in the > > future. Currently, the self-service method of triggering benchmarks is > > unavailable considering the lack of resources and potential > > vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to > > submit a benchmark. More info is updated on the wiki[8]. > > > > Daily Monitoring: > > The performance daily monitoring on the Apache Flink slack channel [2] > > is still unavailable as the benchmark results need more time to > > stabilize in the new environment. Once the baseline results become > > available for regression detection, I will enable the daily > > monitoring. > > > > Please feel free to reach out to me if you have any suggestions or > > questions. Thanks Ververica again for denoting machines! > > > > > > Best, > > Zakelly > > > > [1] https://github.com/apache/flink-benchmarks > > [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > > [3] https://issues.apache.org/jira/browse/FLINK-33052 > > [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > > [5] https://issues.apache.org/jira/browse/FLINK-30890 > > [6] http://codespeed.dak8s.net:8000 > > [7] http://flink-speed.xyz > > [8] > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > > > > > -- > https://twitter.com/snntrable > https://github.com/knaufk >
Re: [ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Thanks a lot for working on this! Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan < zakelly@gmail.com>: > Hi everyone, > > Flink benchmarks [1] generate daily performance reports in the Apache > Flink slack channel (#flink-dev-benchmarks) to detect performance > regression [2]. Those benchmarks previously were running on several > machines donated and maintained by Ververica. Unfortunately, those > machines were gone due to account issues [3] and the benchmarks daily > run stopped since August 24th delaying the release of Flink 1.18 a > bit. [4]. > > Ververica donated several new machines! After several weeks of work, I > have successfully re-established the codespeed panel and benchmark > daily run pipelines on them. At this time, we are pleased to announce > that the Flink Speed Center and benchmark pipelines are back online. > These new machines have a more formal management to ensure that > previous accidents will not occur in the future. > > What's more, I successfully recovered historical data backed up by > Yanfei Lei [5]. So with the old domain [6] redirected to the new > machines, the old links that existed in previous records will still be > valid. Besides the benchmarks with Java8 and Java11, I also added a > pipeline for Java17 running daily. > > How to use it: > We also registered a new domain name 'flink-speed.xyz' for the Flink > Speed Center [7]. It is recommended to use the new domain in the > future. Currently, the self-service method of triggering benchmarks is > unavailable considering the lack of resources and potential > vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to > submit a benchmark. More info is updated on the wiki[8]. > > Daily Monitoring: > The performance daily monitoring on the Apache Flink slack channel [2] > is still unavailable as the benchmark results need more time to > stabilize in the new environment. Once the baseline results become > available for regression detection, I will enable the daily > monitoring. > > Please feel free to reach out to me if you have any suggestions or > questions. Thanks Ververica again for denoting machines! > > > Best, > Zakelly > > [1] https://github.com/apache/flink-benchmarks > [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj > [3] https://issues.apache.org/jira/browse/FLINK-33052 > [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 > [5] https://issues.apache.org/jira/browse/FLINK-30890 > [6] http://codespeed.dak8s.net:8000 > [7] http://flink-speed.xyz > [8] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847 > -- https://twitter.com/snntrable https://github.com/knaufk
[ANNOUNCE] The Flink Speed Center and benchmark daily run are back online
Hi everyone, Flink benchmarks [1] generate daily performance reports in the Apache Flink slack channel (#flink-dev-benchmarks) to detect performance regression [2]. Those benchmarks previously were running on several machines donated and maintained by Ververica. Unfortunately, those machines were gone due to account issues [3] and the benchmarks daily run stopped since August 24th delaying the release of Flink 1.18 a bit. [4]. Ververica donated several new machines! After several weeks of work, I have successfully re-established the codespeed panel and benchmark daily run pipelines on them. At this time, we are pleased to announce that the Flink Speed Center and benchmark pipelines are back online. These new machines have a more formal management to ensure that previous accidents will not occur in the future. What's more, I successfully recovered historical data backed up by Yanfei Lei [5]. So with the old domain [6] redirected to the new machines, the old links that existed in previous records will still be valid. Besides the benchmarks with Java8 and Java11, I also added a pipeline for Java17 running daily. How to use it: We also registered a new domain name 'flink-speed.xyz' for the Flink Speed Center [7]. It is recommended to use the new domain in the future. Currently, the self-service method of triggering benchmarks is unavailable considering the lack of resources and potential vulnerabilities of Jenkins. Please contact one of Apache Flink PMCs to submit a benchmark. More info is updated on the wiki[8]. Daily Monitoring: The performance daily monitoring on the Apache Flink slack channel [2] is still unavailable as the benchmark results need more time to stabilize in the new environment. Once the baseline results become available for regression detection, I will enable the daily monitoring. Please feel free to reach out to me if you have any suggestions or questions. Thanks Ververica again for denoting machines! Best, Zakelly [1] https://github.com/apache/flink-benchmarks [2] https://lists.apache.org/thread/zok62sx4m50c79htfp18ymq5vmtgbgxj [3] https://issues.apache.org/jira/browse/FLINK-33052 [4] https://lists.apache.org//thread/5x28rp3zct4p603hm4zdwx6kfr101w38 [5] https://issues.apache.org/jira/browse/FLINK-30890 [6] http://codespeed.dak8s.net:8000 [7] http://flink-speed.xyz [8] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847
