JingGe commented on code in PR #24279: URL: https://github.com/apache/flink/pull/24279#discussion_r1483214554
########## docs/content.zh/docs/ops/debugging/flame_graphs.md: ########## @@ -27,36 +27,37 @@ under the License. # Flame Graphs -[Flame Graphs](http://www.brendangregg.com/flamegraphs.html) are a visualization that effectively surfaces answers to questions like: -- Which methods are currently consuming CPU resources? -- How does consumption by one method compare to the others? -- Which series of calls on the stack led to executing a particular method? +[Flame Graphs](http://www.brendangregg.com/flamegraphs.html) 是一种有效的可视化工具，可以回答以下问题： + +- 目前哪些方法正在消耗CPU资源？ +- 一个方法的消耗与其他方法相比如何？ +- 堆栈中的一系列调用导致执行特定方法？ Review Comment: ```suggestion - 哪一系列的堆栈调用导致了特定方法的执行? ``` ########## docs/content.zh/docs/ops/debugging/flame_graphs.md: ########## @@ -27,36 +27,37 @@ under the License. # Flame Graphs -[Flame Graphs](http://www.brendangregg.com/flamegraphs.html) are a visualization that effectively surfaces answers to questions like: -- Which methods are currently consuming CPU resources? -- How does consumption by one method compare to the others? -- Which series of calls on the stack led to executing a particular method? +[Flame Graphs](http://www.brendangregg.com/flamegraphs.html) 是一种有效的可视化工具，可以回答以下问题： + +- 目前哪些方法正在消耗CPU资源？ +- 一个方法的消耗与其他方法相比如何？ +- 堆栈中的一系列调用导致执行特定方法？ {{< img src="/fig/flame_graph_on_cpu.png" class="img-fluid" width="90%" >}} {{% center %}} Flame Graph {{% /center %}} -Flame Graphs are constructed by sampling stack traces a number of times. Each method call is presented by a bar, where the length of the bar is proportional to the number of times it is present in the samples. +Flame Graphs是通过多次采样堆栈跟踪来构建的。每个方法调用都以一个条形图表示，其中条形图的长度与其在采样中出现的次数成比例。 Review Comment: ```suggestion Flame Graphs是通过多次采样堆栈跟踪来构建的。每个方法调用都由一个条形图表示，其中条形图的长度与其在样本中出现的次数成比例。 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
