[
https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072350#comment-17072350
]
Yun Tang commented on FLINK-16850:
----------------------------------
[~AHeise], the main benefit is that we could track the performance result of
specific Flink release which is [~NicoK] said if he just want to compare the
performance at Flink-1.10 release. On the other hand, we would not necessarily
run the benchmarks daily on each release branch. We could still only run the
master branch benchmark but just checkout release branch to leave them for some
developers who might be interested to run in the future.
[~pnowojski], I think flink-benchmark has been widely accepted among Flink
developers, and it could be okay to create a new release branch on
flink-benchmark when checkouting release a new branch on Flink in release
steps. The main concern is that not all developers have the access right to
directly create new branch on flink-benchmark which means we might need
flink-benchmark repo owner to involve in each major version release.
> Make flink-benchmark align with different releases of Flink
> -----------------------------------------------------------
>
> Key: FLINK-16850
> URL: https://issues.apache.org/jira/browse/FLINK-16850
> Project: Flink
> Issue Type: Improvement
> Components: Benchmarks
> Affects Versions: 1.10.0
> Reporter: Yun Tang
> Priority: Major
>
> Currently, [flink-benchmark|https://github.com/dataArtisans/flink-benchmarks]
> does not have any releases to align with release branches of Flink. Just
> change the {{flink.version}} when executing benchmark is not enough as
> {{flink-benchmark}} always use the latset interfaces which might not existed
> in previous Flink versions. Take FLINK-15222 for example, this let
> {{flink-benchmark}} to use new version of interface which is only existed
> after Flink-1.11
> I think we could also let {{flink-benchmark}} to have releases or at least
> specific branch to align with releases of Flink.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
