[
https://issues.apache.org/jira/browse/FLINK-28243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558494#comment-17558494
]
Anton Kalashnikov commented on FLINK-28243:
-------------------------------------------
FLINK-28241should be reverted as soon as this task will be done
> Considering only time of targeted operation for calculation benchmarks
> performance
> ----------------------------------------------------------------------------------
>
> Key: FLINK-28243
> URL: https://issues.apache.org/jira/browse/FLINK-28243
> Project: Flink
> Issue Type: Improvement
> Components: Benchmarks
> Reporter: Anton Kalashnikov
> Priority: Major
>
> Right now, in many benchmarks, the iteration time consists of many parts
> which are not always connected to the target of the particular benchmark. For
> example, if we want to benchmark async operator, we want to take into account
> only the time which was spent on this operator but currently, the time of one
> iteration of asyncOperatorBenchmark is `job/tasks initialization phase` +
> `operator execution` + `shutdown phase`.
> Ideally, we want to isolate somehow `operator execution` time and consider
> only it in this benchmark but `job/tasks initialization phase` should be
> benchmarked separately.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
