mirror of https://github.com/apache/druid.git
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 <techdocsmith@gmail.com>
This commit is contained in:
parent
f07d402f48
commit
0c601bf430
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in New Issue