You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by fj...@apache.org on 2019/05/24 18:52:48 UTC
[incubator-druid] branch master updated: Fix references to removed
performance FAQ page (#7755)
This is an automated email from the ASF dual-hosted git repository.
fjy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git
The following commit(s) were added to refs/heads/master by this push:
new cfb7756 Fix references to removed performance FAQ page (#7755)
cfb7756 is described below
commit cfb7756c9bf0c9d4ef2c207f9fefb69c8ae1c374
Author: Jonathan Wei <jo...@users.noreply.github.com>
AuthorDate: Fri May 24 11:52:40 2019 -0700
Fix references to removed performance FAQ page (#7755)
---
docs/content/operations/recommendations.md | 8 +++-----
docs/content/querying/groupbyquery.md | 3 ++-
docs/content/toc.md | 1 -
3 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/docs/content/operations/recommendations.md b/docs/content/operations/recommendations.md
index 311b46d..61cb871 100644
--- a/docs/content/operations/recommendations.md
+++ b/docs/content/operations/recommendations.md
@@ -84,10 +84,8 @@ Timeseries and TopN queries are much more optimized and significantly faster tha
Segments should generally be between 300MB-700MB in size. Too many small segments results in inefficient CPU utilizations and
too many large segments impacts query performance, most notably with TopN queries.
-# Read FAQs
+# FAQs and Guides
-You should read common problems people have here:
+1) The [Ingestion FAQ](../ingestion/faq.html) provides help with common ingestion problems.
-1) [Ingestion-FAQ](../ingestion/faq.html)
-
-2) [Performance-FAQ](../operations/performance-faq.html)
+2) The [Basic Cluster Tuning Guide](../operations/basic-cluster-tuning.html) offers introductory guidelines for tuning your Druid cluster.
diff --git a/docs/content/querying/groupbyquery.md b/docs/content/querying/groupbyquery.md
index 125d793..e6451a2 100644
--- a/docs/content/querying/groupbyquery.md
+++ b/docs/content/querying/groupbyquery.md
@@ -288,7 +288,8 @@ disk space.
With groupBy v2, cluster operators should make sure that the off-heap hash tables and on-heap merging dictionaries
will not exceed available memory for the maximum possible concurrent query load (given by
-druid.processing.numMergeBuffers). See [How much direct memory does Druid use?](../operations/performance-faq.html) for more details.
+druid.processing.numMergeBuffers). See the [Basic Cluster Tuning Guide](../operations/basic-tuning-guide.html)
+for more details about direct memory usage, organized by Druid process type.
Brokers do not need merge buffers for basic groupBy queries. Queries with subqueries (using a "query" [dataSource](datasource.html#query-data-source)) require one merge buffer if there is a single subquery, or two merge buffers if there is more than one layer of nested subqueries. Queries with [subtotals](groupbyquery.html#more-on-subtotalsspec) need one merge buffer. These can stack on top of each other: a groupBy query with multiple layers of nested subqueries, and that also uses subto [...]
diff --git a/docs/content/toc.md b/docs/content/toc.md
index e707ad0..6ee4908 100644
--- a/docs/content/toc.md
+++ b/docs/content/toc.md
@@ -143,7 +143,6 @@ layout: toc
* Tuning and Recommendations
* [Basic Cluster Tuning](/docs/VERSION/operations/basic-cluster-tuning.html)
* [General Recommendations](/docs/VERSION/operations/recommendations.html)
- * [Performance FAQ](/docs/VERSION/operations/performance-faq.html)
* [JVM Best Practices](/docs/VERSION/configuration/index.html#jvm-configuration-best-practices)
* Tools
* [Dump Segment Tool](/docs/VERSION/operations/dump-segment.html)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org