This is an automated email from the ASF dual-hosted git repository.
dwysakowicz pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 0b4b01a Rebuild page
0b4b01a is described below
commit 0b4b01af5977fb68de73923af52d26aafe7e48cc
Author: Dawid Wysakowicz <[email protected]>
AuthorDate: Mon May 3 17:41:19 2021 +0200
Rebuild page
---
content/blog/feed.xml | 21 +++++++++++++++------
content/news/2021/05/03/release-1.13.0.html | 21 +++++++++++++++------
2 files changed, 30 insertions(+), 12 deletions(-)
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index d3a6b6c..e0eef96 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -133,10 +133,19 @@ and ratios for busyness and backpressure.</p>
<p>The next question during performance analysis is typically: What part
of work in the bottlenecked
operator is expensive?</p>
-<p>One visually effective means to investigate that is <em>Flame
Graphs</em>. They help answer question like:
- - Which methods are currently consuming CPU resources?
- - How does one method’s CPU consumption compare to other methods?
- - Which series of calls on the stack led to executing a particular
method?</p>
+<p>One visually effective means to investigate that is <em>Flame
Graphs</em>. They help answer question like:</p>
+
+<ul>
+ <li>
+ <p>Which methods are currently consuming CPU resources?</p>
+ </li>
+ <li>
+ <p>How does one method’s CPU consumption compare to other
methods?</p>
+ </li>
+ <li>
+ <p>Which series of calls on the stack led to executing a particular
method?</p>
+ </li>
+</ul>
<p>Flame Graphs are constructed by repeatedly sampling the thread stack
traces. Every method call is
represented by a bar, where the length of the bar is proportional to the
number of times it is present
@@ -146,8 +155,8 @@ in the samples. When enabled, the graphs are shown in a new
UI component for the
<img src="/img/blog/2021-05-03-release-1.13.0/7.png"
style="display: block; margin-left: auto; margin-right: auto; width:
600px" />
</figure>
-<p>Flame graphs are expensive to create: They may cause processing
overhead and can put a heavy load
-on Flink’s metric system. Because of that, users need to explicitly enable
them in the configuration.</p>
+<p>The <a
href="https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/debugging/flame_graphs">Flame
Graphs documentation</a>
+contains more details and instructions for enabling this feature.</p>
<p><strong>Access Latency Metrics for
State</strong></p>
diff --git a/content/news/2021/05/03/release-1.13.0.html
b/content/news/2021/05/03/release-1.13.0.html
index c8ddaa1..1283cbc 100644
--- a/content/news/2021/05/03/release-1.13.0.html
+++ b/content/news/2021/05/03/release-1.13.0.html
@@ -327,10 +327,19 @@ and ratios for busyness and backpressure.</p>
<p>The next question during performance analysis is typically: What part of
work in the bottlenecked
operator is expensive?</p>
-<p>One visually effective means to investigate that is <em>Flame Graphs</em>.
They help answer question like:
- - Which methods are currently consuming CPU resources?
- - How does one method’s CPU consumption compare to other methods?
- - Which series of calls on the stack led to executing a particular
method?</p>
+<p>One visually effective means to investigate that is <em>Flame Graphs</em>.
They help answer question like:</p>
+
+<ul>
+ <li>
+ <p>Which methods are currently consuming CPU resources?</p>
+ </li>
+ <li>
+ <p>How does one method’s CPU consumption compare to other methods?</p>
+ </li>
+ <li>
+ <p>Which series of calls on the stack led to executing a particular
method?</p>
+ </li>
+</ul>
<p>Flame Graphs are constructed by repeatedly sampling the thread stack
traces. Every method call is
represented by a bar, where the length of the bar is proportional to the
number of times it is present
@@ -340,8 +349,8 @@ in the samples. When enabled, the graphs are shown in a new
UI component for the
<img src="/img/blog/2021-05-03-release-1.13.0/7.png" style="display: block;
margin-left: auto; margin-right: auto; width: 600px" />
</figure>
-<p>Flame graphs are expensive to create: They may cause processing overhead
and can put a heavy load
-on Flink’s metric system. Because of that, users need to explicitly enable
them in the configuration.</p>
+<p>The <a
href="https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/debugging/flame_graphs";>Flame
Graphs documentation</a>
+contains more details and instructions for enabling this feature.</p>
<p><strong>Access Latency Metrics for State</strong></p>
