[FLINK-30185] Provide the flame graph to the subtask level

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.17.0
• Component/s: Runtime / REST, Runtime / Web Frontend
• Labels: pull-request-available
• Assignee: Rui Fan
• Reporter: Rui Fan
• Created: 24/Nov/22 06:52
• Updated: 06/Jan/23 07:13
• Resolved: 05/Jan/23 11:25

Description

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

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. 

 

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

 

 

 

Issue Links

• links to: GitHub Pull Request #21447