This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 9dffe13aa9 Add benchmark selection into banyanDB storage documentation
(#13595)
9dffe13aa9 is described below
commit 9dffe13aa98b6e0a1a43306d1110154f61654d00
Author: mrproliu <[email protected]>
AuthorDate: Thu Nov 27 13:39:52 2025 +0800
Add benchmark selection into banyanDB storage documentation (#13595)
---
docs/en/changes/changes.md | 2 ++
docs/en/setup/backend/backend-storage.md | 3 +++
2 files changed, 5 insertions(+)
diff --git a/docs/en/changes/changes.md b/docs/en/changes/changes.md
index e06dad6269..f4b4ae9ba5 100644
--- a/docs/en/changes/changes.md
+++ b/docs/en/changes/changes.md
@@ -13,6 +13,8 @@
#### Documentation
+* Add benchmark selection into banyanDB storage documentation.
+
All issues and pull requests are
[here](https://github.com/apache/skywalking/issues?q=milestone:10.4.0)
diff --git a/docs/en/setup/backend/backend-storage.md
b/docs/en/setup/backend/backend-storage.md
index f878a3b789..6542770eab 100644
--- a/docs/en/setup/backend/backend-storage.md
+++ b/docs/en/setup/backend/backend-storage.md
@@ -14,6 +14,9 @@ BanyanDB is a native-built SkyWalking database, which can
completely focus on Sk
It has demonstrated significant potential for performance improvement and
reduced resource usage requirements. It indicates 5x less memory usage,
1/5 disk IOPS, 1/4 disk throughput, and 30% less disk space, albeit with a
slightly higher CPU trade-off, compared to Elasticsearch.
+In benchmark testing, a BanyanDB cluster with 2 liaison nodes and 2 data nodes
(each with 2 cores and 4GB memory) successfully handled sustained
high-throughput workloads:
+ingesting over 571,000 metric data points, 151,000 stream records, and 6,600
traces (133,200 spans) per minute. Query performance remained responsive with
median latencies of 26ms for metrics (p99: 288ms), 7ms for streams (p99: 72ms),
and 436ms for traces (p99: ~1.1s) under concurrent read/write operations.
+
## SQL database
- [MySQL and its compatible databases](storages/mysql.md)
- [PostgreSQL and its compatible databases](storages/postgresql.md)