petermarshallio commented on a change in pull request #11584:
URL: https://github.com/apache/druid/pull/11584#discussion_r722171431
##########
File path: docs/operations/basic-cluster-tuning.md
##########
@@ -90,11 +90,9 @@ Tuning the cluster so that each Historical can accept 50
queries and 10 non-quer
#### Segment Cache Size
-`druid.segmentCache.locations` specifies locations where segment data can be
stored on the Historical. The sum of available disk space across these
locations is set as the default value for property: `druid.server.maxSize`,
which controls the total size of segment data that can be assigned by the
Coordinator to a Historical.
+Avoid allocating a Historical an excessive amount of segment data. As the
value of (`free system memory` / total size of all
`druid.segmentCache.locations`) increases, a greater proportion of segments can
be kept in the [memory-mapped segment
cache](../design/historical.md#loading-and-serving-segments-from-cache),
allowing for better query performance.
Review comment:
Should `can be hold` be `be held` or `can hold` ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
