You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2022/04/11 08:49:00 UTC
[jira] [Resolved] (FLINK-23399) Add a performance benchmark for statebackend rescaling
[ https://issues.apache.org/jira/browse/FLINK-23399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yun Tang resolved FLINK-23399.
------------------------------
Resolution: Fixed
Merged in flink-benchmarks repo: 57cc8064db4a9f934f77a5fa5038712cb01e5183
> Add a performance benchmark for statebackend rescaling
> ------------------------------------------------------
>
> Key: FLINK-23399
> URL: https://issues.apache.org/jira/browse/FLINK-23399
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.14.0
> Reporter: Yanfei Lei
> Assignee: Yanfei Lei
> Priority: Minor
> Labels: pull-request-available, stale-assigned
> Fix For: 1.16.0
>
>
> We notice that rescaling is not covered in the current state benchmark, so we'd like to introduce a benchmark to test performance of state backend restore durign rescaling in flink-benchmark.
> The benchmark process is:
> (1) generate some states,
> (2) change the parallelism of the operator, and restore from these states generate before.
> The implementation of this benchmark is based on {{RocksIncrementalCheckpointRescalingTest}}, and *_AverageTime_* is used to measure the rescaling performance on each subtask.
>
> And this benchmark does not conflict with `RocksIncrementalCheckpointRescalingBenchmarkTest` in
> PR([#14893|https://github.com/apache/flink/pull/14893]). Compare with `RocksIncrementalCheckpointRescalingBenchmarkTest`, this benchmark supports testing rescaling on different state backends, and has a finer granularity.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)