Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add resource consumption testing result #67

Merged
merged 7 commits into from
Oct 28, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
address comments
Signed-off-by: shiqi wang <[email protected]>
wangshiqi308 committed Oct 22, 2024
commit 81c4ba0dde749a5569bde965f78443281d62a208
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
6 changes: 3 additions & 3 deletions content/en/docs/performance/resource_consumption.md
Original file line number Diff line number Diff line change
@@ -10,9 +10,9 @@
type: docs
---
# 1. Background Information
eBPF programs consume a certain amount of CPU and memory resources during their execution, which may affect the performance of other applications. To gain a deeper understanding of Kmesh’s resource consumption under different loads, we conducted several CPU and memory stress tests. These tests aim to evaluate the limits of CPU and memory consumption of Kmesh in real-world usage scenarios.
eBPF programs consume a certain amount of CPU and memory resources during their execution. To gain a deeper understanding of Kmesh’s resource consumption under different loads, we conducted several CPU and memory stress tests. These tests aim to evaluate the limits of CPU and memory consumption of Kmesh in real-world usage scenarios.

**This documentation is based on Kmesh 0.4 ads mode**
**This documentation is based on Kmesh 0.4 kernel-native mode**
# 2. Environment setup
![resource_env](/docs/performance/resource_test_env.png)

@@ -25,7 +25,7 @@


PerforMance308 marked this conversation as resolved.
Show resolved Hide resolved
# 3. Test case 1 - POD with CPU limit scenario,collect Kmesh eBPF CPU usage
## 3.1 Deploy 1 App A and set App A POD's CPU limit,then generage load and collect Kmesh eBPF CPU usage

Check failure on line 28 in content/en/docs/performance/resource_consumption.md

GitHub Actions / Check for spelling errors

generage ==> generate
![resource_test1](/docs/performance/resource_test1.png)
PerforMance308 marked this conversation as resolved.
Show resolved Hide resolved

Set the CPU limit for App A to 1 (1 CPU), and collect corresponding Kmesh eBPF CPU consumption.
@@ -53,7 +53,7 @@
**Results and Conclusion: When APP A fully utilizes one CPU core, the eBPF program consumes 1.73%(totally 13.9% usage of one CPU core == 1.73% of 8 CPU cores) of the CPU, which is less than the POD CPU limit of 12.5%. There are two possible reasons.**

- APP A and Kmesh eBPF share the POD CPU limit, with Kmesh eBPF CPU being restricted by the POD CPU limit.
PerforMance308 marked this conversation as resolved.
Show resolved Hide resolved
- It is possible that due to the high performance of eBPF, APP A is not generating enough load to cause eBPF to exceed the CPU limit, further experiments in section 3.2 are needed.
- This indicates eBPF CPU cost is fairly small compared to application itself, APP A is not generating enough load to cause eBPF to exceed the CPU limit, further experiments in section 3.2 are needed.

## 3.2 Deploy multiple instances of App A, set a fixed CPU limit, generate load, and collect the corresponding Kmesh eBPF CPU consumption.
![resource_test2](/docs/performance/resource_test2.png)
4 changes: 2 additions & 2 deletions content/zh/docs/performance/resource_consumption.md
Original file line number Diff line number Diff line change
@@ -10,9 +10,9 @@ toc: true
type: docs
---
# 1. 背景信息
eBPF程序在运行过程中会消耗一定的CPU和内存资源,这可能会影响到其他应用程序的性能。为了深入了解Kmesh在不同负载下的资源消耗情况,我们进行了多项CPU与内存摸高测试。这些测试旨在评估Kmesh在实际使用场景中的CPU和内存消耗极限。
eBPF程序在运行过程中会消耗一定的CPU和内存资源。为了深入了解Kmesh在不同负载下的资源消耗情况,我们进行了多项CPU与内存摸高测试。这些测试旨在评估Kmesh在实际使用场景中的CPU和内存消耗极限。

**本测试基于Kmesh 0.4版本的ads模式进行。**
**本测试基于Kmesh 0.4版本的kernel-native模式进行。**
# 2. 测试环境
![resource_env](/docs/performance/resource_test_env.png)