paultanay commented on PR #1047:
URL:
https://github.com/apache/skywalking-banyandb/pull/1047#issuecomment-4214358994
@hanahmily
Here are the results from my latest local benchmark run on Linux + Kind,
with RF=1/2/3 executed sequentially.
Environment:
- Go 1.25.0
- kind v0.23.0
- kubectl client v1.30.0
- helm v3.13.0
- Chart: oci://registry-1.docker.io/apache/skywalking-banyandb-helm, version
0.5.3
- Workload: writers=4, entities=200, points/entity=30 (6000 writes total),
query workers=4, query iterations=200
Results:
| RF | Write throughput (points/s) | Query median (ms) | Query p95 (ms) |
Query p99 (ms) | Write CPU mean % (liaison) | Write CPU mean % (data) | Read
CPU mean % (liaison) | Read CPU mean % (data) | Write peak RSS total (MiB,
liaison+data) | Read peak RSS total (MiB, liaison+data) |
|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:|---:|
| 1 | 11240.61 | 10.54 | 19.31 | 23.77 | 16.24 | 1.25 | 15.99 | 7.30 |
207.70 | 225.44 |
| 2 | 14461.18 | 11.05 | 18.84 | 23.63 | 23.58 | 3.21 | 15.68 | 7.66 |
209.82 | 222.79 |
| 3 | 14343.65 | 12.49 | 21.82 | 28.26 | 23.14 | 2.93 | 15.77 | 7.88 |
210.02 | 228.96 |
Observed impact in this environment:
1. Write throughput improved vs RF=1 at RF=2 (+28.7%) and RF=3 (+27.6%).
2. Query latency stayed close at RF=2 (p95 -2.4%, p99 -0.6% vs RF=1), but
increased at RF=3 (p95 +13.0%, p99 +18.9%).
3. Resource usage:
- Write phase CPU increased with higher RF, mainly on liaison and data
roles.
- Read phase CPU was relatively stable.
- Peak RSS totals were close across RFs (roughly 208-210 MiB in write
phase and 223-229 MiB in read phase).
Note: resource metrics here are collected for liaison/data roles (not etcd).
Also, the write phase is short in this workload, so read-phase resource numbers
are more stable than write-phase CPU samples.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
