You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by te...@apache.org on 2022/06/02 17:32:21 UTC
[druid] branch master updated: Addition to Multitenancy considerations doc (#12567)
This is an automated email from the ASF dual-hosted git repository.
techdocsmith 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 9c8e6bb000 Addition to Multitenancy considerations doc (#12567)
9c8e6bb000 is described below
commit 9c8e6bb0000cffb4c904e94f0baf03fb9bd23af9
Author: Jill Osborne <ji...@imply.io>
AuthorDate: Thu Jun 2 18:32:14 2022 +0100
Addition to Multitenancy considerations doc (#12567)
* Small addition to Multitenancy considerations doc
* Update docs/querying/multitenancy.md
Co-authored-by: Charles Smith <te...@gmail.com>
* Update multitenancy.md
Edit suggested by @kfaraz
Co-authored-by: Charles Smith <te...@gmail.com>
---
docs/querying/multitenancy.md | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/docs/querying/multitenancy.md b/docs/querying/multitenancy.md
index ed07770ddd..6fc484c241 100644
--- a/docs/querying/multitenancy.md
+++ b/docs/querying/multitenancy.md
@@ -75,10 +75,7 @@ stored on this tier.
## Supporting high query concurrency
-Druid's fundamental unit of computation is a [segment](../design/segments.md). Processes scan segments in parallel and a
-given process can scan `druid.processing.numThreads` concurrently. To
-process more data in parallel and increase performance, more cores can be added to a cluster. Druid segments
-should be sized such that any computation over any given segment should complete in at most 500ms.
+Druid uses a [segment](../design/segments.md) as its fundamental unit of computation. Processes scan segments in parallel and a given process can scan `druid.processing.numThreads` concurrently. You can add more cores to a cluster to process more data in parallel and increase performance. Size your Druid segments such that any computation over any given segment should complete in at most 500ms. Use the the [`query/segment/time`](../operations/metrics.md#historical) metric to monitor com [...]
Druid internally stores requests to scan segments in a priority queue. If a given query requires scanning
more segments than the total number of available processors in a cluster, and many similarly expensive queries are concurrently
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org