This is an automated email from the ASF dual-hosted git repository.
frankchen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/master by this push:
new 0c601bf430d Update basic-cluster-tuning.md (#14964)
0c601bf430d is described below
commit 0c601bf430d1ff7cb7c7092f376cf2bc02d56174
Author: benkrug <[email protected]>
AuthorDate: Tue Feb 27 18:48:20 2024 -0700
Update basic-cluster-tuning.md (#14964)
* Update basic-cluster-tuning.md
The sentence "When free system memory is greater than or equal to
druid.segmentCache.locations, the more segment data the Historical can be held
in the memory-mapped segment cache" didn't read well. Updated to clarify it.
* Update docs/operations/basic-cluster-tuning.md
* Update docs/operations/basic-cluster-tuning.md
---------
Co-authored-by: Charles Smith <[email protected]>
---
docs/operations/basic-cluster-tuning.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/operations/basic-cluster-tuning.md
b/docs/operations/basic-cluster-tuning.md
index e48b4b0c4f6..a9d4e973482 100644
--- a/docs/operations/basic-cluster-tuning.md
+++ b/docs/operations/basic-cluster-tuning.md
@@ -90,9 +90,10 @@ Tuning the cluster so that each Historical can accept 50
queries and 10 non-quer
#### Segment Cache Size
-For better query performance, do not allocate segment data to a Historical in
excess of the system free memory. When `free system memory` is greater than or
equal to `druid.segmentCache.locations`, the more segment data the Historical
can be held in the memory-mapped segment cache.
+For better query performance, do not allocate segment data to a Historical in
excess of the system free memory. The Historical uses free system memory to
cache segments.
+For more detail, see [Loading and serving segments from
cache](../design/historical/#loading-and-serving-segments-from-cache)
-Druid uses the `druid.segmentCache.locations` to calculate the total segment
data size assigned to a Historical. For some rarer use cases, you can override
this behavior with `druid.server.maxSize` property.
+Druid uses the `druid.segmentCache.locations` to calculate the total segment
data size assigned to a Historical. For rare use cases, you can override this
behavior with `druid.server.maxSize` property.
#### Number of Historicals
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
