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

wwei pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-yunikorn-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 7241a2f  [YUNIKORN-464] fix the dead image links in the perf doc
7241a2f is described below

commit 7241a2f5fba53f6810205923d51c9c900b9eb3c1
Author: Weiwei Yang <[email protected]>
AuthorDate: Thu Nov 19 10:22:04 2020 -0800

    [YUNIKORN-464] fix the dead image links in the perf doc
---
 docs/performance/evaluate_perf_function_with_kubemark.md            | 6 +++---
 .../performance/evaluate_perf_function_with_kubemark.md             | 4 ++--
 .../performance/evaluate_perf_function_with_kubemark.md             | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/performance/evaluate_perf_function_with_kubemark.md 
b/docs/performance/evaluate_perf_function_with_kubemark.md
index 066596a..f2c7090 100644
--- a/docs/performance/evaluate_perf_function_with_kubemark.md
+++ b/docs/performance/evaluate_perf_function_with_kubemark.md
@@ -52,7 +52,7 @@ Each of YuniKorn queues has its guaranteed and maximum 
capacity. When we have lo
 YuniKorn ensures each of them gets its fair share. When we monitor the 
resource usage of these queues, we can clearly
 see how fairness was enforced:
 
-![Scheduler Throughput](./../assets/queue-fairness.png)
+![Queue Fairness](./../assets/queue-fairness.png)
 
 We set up 4 heterogeneous queues on this cluster, and submit different 
workloads against these queues.
 From the chart, we can see the queue resources are increasing nearly in the 
same trend, which means the resource
@@ -83,7 +83,7 @@ This means at the given time, this cluster has 100 nodes 
whose utilization is in
 it has 300 nodes whose utilization is in the range 10% - 20%, and so on… Now, 
we run lots of workloads and
 collect metrics, see the below chart:
 
-<img src="./../assets/node-fair.png" />
+![Node Fairness](./../assets/node-fair.png)
 
 We can see all nodes have 0% utilization, and then all of them move to 
bucket-1, then bucket-2 … and eventually
 all nodes moved to bucket-9, which means all capacity is used. In another 
word, nodes’ resource has been used in
@@ -93,7 +93,7 @@ a fairness manner.
 
 This is When the bin-packing policy is enabled, we can see the following 
pattern:
 
-<img src="./../assets/node-bin-packing.png" />
+![Node Bin-Packing](./../assets/node-bin-packing.png)
 
 On the contrary, all nodes are moving between 2 buckets, bucket-0 and 
bucket-9. Nodes in bucket-0 (0% - 10%)
 are decreasing in a linear manner, and nodes in bucket-9 (90% - 100%) are 
increasing with the same curve.
diff --git 
a/versioned_docs/version-0.8.0/performance/evaluate_perf_function_with_kubemark.md
 
b/versioned_docs/version-0.8.0/performance/evaluate_perf_function_with_kubemark.md
index de9184d..1ad7bee 100644
--- 
a/versioned_docs/version-0.8.0/performance/evaluate_perf_function_with_kubemark.md
+++ 
b/versioned_docs/version-0.8.0/performance/evaluate_perf_function_with_kubemark.md
@@ -82,7 +82,7 @@ This means at the given time, this cluster has 100 nodes 
whose utilization is in
 it has 300 nodes whose utilization is in the range 10% - 20%, and so on… Now, 
we run lots of workloads and
 collect metrics, see the below chart:
 
-<img src="./../assets/node-fair.png" />
+![Node Fairness](./../assets/node-fair.png)
 
 We can see all nodes have 0% utilization, and then all of them move to 
bucket-1, then bucket-2 … and eventually
 all nodes moved to bucket-9, which means all capacity is used. In another 
word, nodes’ resource has been used in
@@ -92,7 +92,7 @@ a fairness manner.
 
 This is When the bin-packing policy is enabled, we can see the following 
pattern:
 
-<img src="./../assets/node-bin-packing.png" />
+![Node Bin-Packing](./../assets/node-bin-packing.png)
 
 On the contrary, all nodes are moving between 2 buckets, bucket-0 and 
bucket-9. Nodes in bucket-0 (0% - 10%)
 are decreasing in a linear manner, and nodes in bucket-9 (90% - 100%) are 
increasing with the same curve.
diff --git 
a/versioned_docs/version-0.9.0/performance/evaluate_perf_function_with_kubemark.md
 
b/versioned_docs/version-0.9.0/performance/evaluate_perf_function_with_kubemark.md
index 066596a..2774311 100644
--- 
a/versioned_docs/version-0.9.0/performance/evaluate_perf_function_with_kubemark.md
+++ 
b/versioned_docs/version-0.9.0/performance/evaluate_perf_function_with_kubemark.md
@@ -83,7 +83,7 @@ This means at the given time, this cluster has 100 nodes 
whose utilization is in
 it has 300 nodes whose utilization is in the range 10% - 20%, and so on… Now, 
we run lots of workloads and
 collect metrics, see the below chart:
 
-<img src="./../assets/node-fair.png" />
+![Node Fairness](./../assets/node-fair.png)
 
 We can see all nodes have 0% utilization, and then all of them move to 
bucket-1, then bucket-2 … and eventually
 all nodes moved to bucket-9, which means all capacity is used. In another 
word, nodes’ resource has been used in
@@ -93,7 +93,7 @@ a fairness manner.
 
 This is When the bin-packing policy is enabled, we can see the following 
pattern:
 
-<img src="./../assets/node-bin-packing.png" />
+![Node Bin-Packing](./../assets/node-bin-packing.png)
 
 On the contrary, all nodes are moving between 2 buckets, bucket-0 and 
bucket-9. Nodes in bucket-0 (0% - 10%)
 are decreasing in a linear manner, and nodes in bucket-9 (90% - 100%) are 
increasing with the same curve.

Reply via email to