summaryrefslogtreecommitdiffstats
path: root/database
diff options
context:
space:
mode:
authorJoel Hans <joel@netdata.cloud>2020-05-18 13:10:19 -0700
committerGitHub <noreply@github.com>2020-05-18 13:10:19 -0700
commit223724f2186f51ea464be04df997ff2e934c8352 (patch)
tree0eb5816f615b2e053da48dad5c61ff026cb908f5 /database
parent06ffc8f9f5c3f71aa39b4cef516773bca736859d (diff)
Add links to promote database engine calculator (#9067)
* Add links and calculator .md * Refactor to Learn * Remove erroneous paragraph
Diffstat (limited to 'database')
-rw-r--r--database/engine/README.md10
1 files changed, 8 insertions, 2 deletions
diff --git a/database/engine/README.md b/database/engine/README.md
index f4995744ad..fe3ad3b3f7 100644
--- a/database/engine/README.md
+++ b/database/engine/README.md
@@ -1,8 +1,7 @@
<!--
----
title: "Database engine"
+description: "The highly-efficient database engine stores per-second metrics in RAM and then spills historical metrics to disk long-term storage."
custom_edit_url: https://github.com/netdata/netdata/edit/master/database/engine/README.md
----
-->
# Database engine
@@ -63,6 +62,10 @@ All DB engine instances, for localhost and all other streaming recipient nodes i
The above values are the default and minimum values for Page Cache size and DB engine disk space quota. Both numbers are
in **MiB**. All DB engine instances will allocate the configured resources separately.
+[**See our database engine calculator**](https://learn.netdata.cloud/docs/agent/database/calculator) to help you
+correctly set `dbengine disk space` based on your needs. The calculator gives an accurate estimate based on how many
+slave nodes you have, how many metrics your Agent collects, and more.
+
The `page cache size` option determines the amount of RAM in **MiB** that is dedicated to caching Netdata metric values
themselves as far as queries are concerned. The total page cache size will be greater since data collection itself will
consume additional memory as is described in the [Memory requirements](#memory-requirements) section.
@@ -108,6 +111,9 @@ and streaming recipient nodes):
An important observation is that RAM usage depends on both the `page cache size` and the `dbengine disk space` options.
+You can use our [database engine calculator](https://learn.netdata.cloud/docs/agent/database/calculator) to
+validate the memory requirements for your particular system(s) and configuration.
+
## File descriptor requirements
The Database Engine may keep a **significant** amount of files open per instance (e.g. per streaming slave or master