[
https://issues.apache.org/jira/browse/FLINK-30185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-30185:
-----------------------------------
Labels: pull-request-available (was: )
> Provide the flame graph to the subtask level
> --------------------------------------------
>
> Key: FLINK-30185
> URL: https://issues.apache.org/jira/browse/FLINK-30185
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST, Runtime / Web Frontend
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
> Attachments: image-2022-11-24-14-49-42-845.png,
> image-2022-11-28-14-38-47-145.png, image-2022-11-28-14-48-20-462.png
>
>
> FLINK-13550 supported for CPU FlameGraphs in web UI.
> As Flink doc mentioned:
> https://nightlies.apache.org/flink/flink-docs-master/docs/ops/debugging/flame_graphs/#sampling-process
> {code:java}
> Note: Stack trace samples from all threads of an operator are combined
> together. If a method call consumes 100% of the resources in one of the
> parallel tasks but none in the others, the bottleneck might be obscured by
> being averaged out.
> There are plans to address this limitation in the future by providing “drill
> down” visualizations to the task level. {code}
>
> The flame graph at the subtask level is very useful when a small number of
> subtasks are bottlenecked. So we should provide the flame graph to the
> subtask level
>
> !image-2022-11-24-14-49-42-845.png!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
