Skip to content

Fix references to removed performance FAQ page #7755

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fjy merged 1 commit into from
May 24, 2019
Merged

Fix references to removed performance FAQ page #7755

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions docs/content/operations/recommendations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
3 changes: 2 additions & 1 deletion docs/content/querying/groupbyquery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Copy link
Copy Markdown
Contributor

@gianm gianm May 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be basic-cluster-tuning.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 subtotals, will need three merge buffers.

Expand Down
1 change: 0 additions & 1 deletion docs/content/toc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down