This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/skywalking-go.git
The following commit(s) were added to refs/heads/main by this push:
new 834b8ff Add explanation for extra payload (#24)
834b8ff is described below
commit 834b8ff1dbd0265bb417d1af014b7f0e991766af
Author: 吴晟 Wu Sheng <[email protected]>
AuthorDate: Thu May 4 20:37:08 2023 +0800
Add explanation for extra payload (#24)
---
docs/en/agent/performance-tests.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/docs/en/agent/performance-tests.md
b/docs/en/agent/performance-tests.md
index c8a4618..ab6e5c9 100644
--- a/docs/en/agent/performance-tests.md
+++ b/docs/en/agent/performance-tests.md
@@ -92,4 +92,6 @@ In the tests, we used **1000 QPS** as a benchmark to stress
test both the Consum
* In the **non-Agent version**, the CPU usage was around **74%**, memory usage
was **2.53%**, and the average response time for a single request was
**4.18ms**.
* In the **Agent-compiled version**, the CPU usage was around **81%**, memory
usage was **2.61%**, and the average response time for a single request was
**4.32ms**.
-From these results, we can conclude that after adding the Agent, **the CPU
usage increased by about 9%, memory usage experienced almost no growth, and the
average response time for requests increased by approximately 0.15ms**.
\ No newline at end of file
+From these results, we can conclude that after adding the Agent, **the CPU
usage increased by about 9%, memory usage experienced almost no growth, and the
average response time for requests increased by approximately 0.15ms**.
+
+Explanation, `approximately 0.15ms` is the in-band cost. The most of
CPU(`extra 9%`) cost are due to the amount of out of band data being sent to
the collectors from the application(consumer), which is 4000 spans/s in our
test case.
