You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/setup/backend/backend-storage.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,26 +7,27 @@ storage:
7
7
selector: ${SW_STORAGE:banyandb}
8
8
```
9
9
10
-
Natively supported storage:
11
-
12
10
## BanyanDB - Native APM Database
13
11
- [BanyanDB](storages/banyandb.md)
14
12
15
-
It has demonstrated significant potential in performance improvement. It indicates 5x less memory usage,
13
+
BanyanDB is a native-built SkyWalking database, which can completely focus on SkyWalking use cases.
14
+
It has demonstrated significant potential for performance improvement and reduced resource usage requirements. It indicates 5x less memory usage,
16
15
1/5 disk IOPS, 1/4 disk throughput, and 30% less disk space, albeit with a slightly higher CPU trade-off, compared to Elasticsearch.
17
-
It is designed and implemented natively for SkyWalking use cases.
18
16
19
17
## SQL database
20
18
- [MySQL and its compatible databases](storages/mysql.md)
21
19
- [PostgreSQL and its compatible databases](storages/postgresql.md)
22
20
23
-
MySQL and PostgreSQL are recommended for production environments for medium scale deployments, especially for low trace
24
-
and log sampling rate. Some of their compatible databases may support larger scale better, such as TiDB and AWS Aurora.
21
+
MySQL and PostgreSQL are recommended for production environments for medium-scale deployments, especially for low trace
22
+
and log sampling rates. Some of their compatible databases may support larger scale better, such as TiDB and AWS Aurora.
23
+
But the logs and traces performance could be significantly lower than BanyanDB and Elasticsearch, even more, their performance can't be improved linearly
0 commit comments