You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ch...@apache.org on 2021/05/03 15:19:37 UTC

[flink-web] branch asf-site updated: [hotfix] fix bullet points list formatting

This is an automated email from the ASF dual-hosted git repository.

chesnay 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 621d6b2  [hotfix] fix bullet points list formatting
621d6b2 is described below

commit 621d6b257a29174c052ce08dd7179ed0bd310493
Author: Alexander Fedulov <14...@users.noreply.github.com>
AuthorDate: Mon May 3 16:42:31 2021 +0200

    [hotfix] fix bullet points list formatting
---
 _posts/2021-05-03-release-1.13.0.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/_posts/2021-05-03-release-1.13.0.md b/_posts/2021-05-03-release-1.13.0.md
index db01dc3..4e917b1 100644
--- a/_posts/2021-05-03-release-1.13.0.md
+++ b/_posts/2021-05-03-release-1.13.0.md
@@ -110,8 +110,11 @@ The next question during performance analysis is typically: What part of work in
 operator is expensive?
 
 One visually effective means to investigate that is *Flame Graphs*. 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?
   
 Flame Graphs are constructed by repeatedly sampling the thread stack traces. Every method call is