[
https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071071#comment-17071071
]
Arvid Heise commented on FLINK-16850:
-------------------------------------
For me, the main question is what is the main benefit. Let's assume we have a
symmetric release to major versions in Flink. (So there is one 1.10 branch of
the benchmarks for all 1.10.X Flink releases). My train of though on benefits
but also potentially undesired consequences.
* I guess we would gain that we could more easily track performance changes
when doing maintenance releases on older branches.
* We would need to maintain flink-benchmark as well for older versions.
* It wouldn't immediately solve the issue that new benchmarks cannot be
retroactively applied on old versions.
* We would need to setup the benchmark UI to support multiple runs for the
supported major versions.
* We would need more processing power. On the other hand, changes to older
branches happen relatively rare, so our current setup may be enough.
> 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)
