[
https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071770#comment-17071770
]
Nico Kruber commented on FLINK-16850:
-------------------------------------
I would actually support at least creating (light-weight) release branches, for
the following reasons:
* being able to use our benchmarks to evaluate the current released version of
Flink, e.g. I'm currently preparing an in-depth blog post and performance
analysis on Flink's serializers for which have the benchmarks at hand already.
However, I would also like to refer to Flink 1.10(.*) and not 1.11-SNAPSHOT
because that may diverge from the release significantly and may not reflect the
current situation.
* being able to compare different releases, e.g. when Flink 1.11 is out, you
may want to compare and blog about the performance differences
* having a reference for those benchmarks and not just saying "I took the
current master and reverted any incompatible change"
We don't necessarily have to monitor these branches' individual performance
improvements/degradations though; but this could be easily done at will.
We could actively backport new (incompatible) benchmarks if needed (for the
above reasons and with the advantage of having an official backport).
> 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)
