Skip to content

Commit 6fbd9e7

Browse files
authored
Polish words in storage docs. (#12911)
1 parent 5be35ba commit 6fbd9e7

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

docs/en/setup/backend/backend-storage.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,26 +7,27 @@ storage:
77
selector: ${SW_STORAGE:banyandb}
88
```
99
10-
Natively supported storage:
11-
1210
## BanyanDB - Native APM Database
1311
- [BanyanDB](storages/banyandb.md)
1412
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,
1615
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.
1816
1917
## SQL database
2018
- [MySQL and its compatible databases](storages/mysql.md)
2119
- [PostgreSQL and its compatible databases](storages/postgresql.md)
2220
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
24+
through scaling out nodes.
2525
2626
## Elasticsearch+
2727
2828
- [OpenSearch](storages/elasticsearch.md#opensearch)
2929
- [ElasticSearch 7 and 8](storages/elasticsearch.md#elasticsearch)
3030
31-
Elasticsearch and OpenSearch are recommended for production environments, specially for large scale deployments.
32-
OpenSearch derived from Elasticsearch 7.10.2 and iterate by its own roadmap.
31+
Elasticsearch and OpenSearch are recommended for production environments, especially for large-scale deployments.
32+
OpenSearch derived from Elasticsearch 7.10.2 and iterates by its own roadmap. But notice, Elasticsearch cluster resource costs are high,
33+
due to its high requirement for memory and replication requirement to keep cluster robustness.

0 commit comments

Comments
 (0)