[jira] [Commented] (FLINK-23399) Add a performance benchmark for statebackend rescaling

["Yun Tang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-23399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515858#comment-17515858 ] 

Yun Tang commented on FLINK-23399:
----------------------------------

The benchmark code in flink repo merged in master: 562b182464cc4da8ee0984527e6e16725b0cfe7c

> 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)