[
https://issues.apache.org/jira/browse/FLINK-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-20127:
-----------------------------------
Description:
Repeat the benchmarks from 1.11 on 1.12 and compare results. Especially focus
on heavy backpressure scenarios.
Also migrate benchmark to new source interface.
----
[General Information about the Flink 1.12 release
testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
When testing a feature, consider the following aspects:
- Is the documentation easy to understand
- Are the error messages, log messages, APIs etc. easy to understand
- Is the feature working as expected under normal conditions
- Is the feature working / failing as expected with invalid input, induced
errors etc.
If you find a problem during testing, please file a ticket (Priority=Critical;
Fix Version = 1.12.0), and link it in this testing ticket.
During the testing keep us updated on tests conducted, or please write a short
summary of all things you have tested in the end.
was:
Repeat the benchmarks from 1.11 on 1.12 and compare results. Especially focus
on heavy backpressure scenarios.
Also migrate benchmark to new source interface.
> Benchmark unaligned checkpointing times under backpressure
> ----------------------------------------------------------
>
> Key: FLINK-20127
> URL: https://issues.apache.org/jira/browse/FLINK-20127
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Checkpointing
> Affects Versions: 1.12.0
> Reporter: Arvid Heise
> Assignee: Arvid Heise
> Priority: Major
>
> Repeat the benchmarks from 1.11 on 1.12 and compare results. Especially focus
> on heavy backpressure scenarios.
> Also migrate benchmark to new source interface.
> ----
> [General Information about the Flink 1.12 release
> testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
> When testing a feature, consider the following aspects:
> - Is the documentation easy to understand
> - Are the error messages, log messages, APIs etc. easy to understand
> - Is the feature working as expected under normal conditions
> - Is the feature working / failing as expected with invalid input, induced
> errors etc.
> If you find a problem during testing, please file a ticket
> (Priority=Critical; Fix Version = 1.12.0), and link it in this testing ticket.
> During the testing keep us updated on tests conducted, or please write a
> short summary of all things you have tested in the end.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
