You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by GitBox <gi...@apache.org> on 2022/01/19 07:23:55 UTC

[GitHub] [drill] jnturton commented on a change in pull request #886: Update 010-performance-tuning-introduction.md

jnturton commented on a change in pull request #886:
URL: https://github.com/apache/drill/pull/886#discussion_r787409132



##########
File path: _docs/performance-tuning/010-performance-tuning-introduction.md
##########
@@ -3,9 +3,9 @@ title: "Performance Tuning Introduction"
 date:  
 parent: "Performance Tuning"
 ---
-You can apply performance tuning measures to improve how efficiently Drill queries data. To significantly improve performance in Drill, you must have knowledge about the underlying data and data sources, as well as familiarity with how Drill executes queries.
+You can change system options in Drill to improve the query performance. Before you improve performance in Drill, you must choose a layout of the data and the choose an appropriate file format specific to your use case. For example, for an analytic workload operating on historical time series data, then choosing Parquet as the file format and a partitioning scheme that uses time as a partitionining dimension would be a recommended approach. In the case you are directly querying data data sources, you need to have an understanding of the data source itself. Some familiarity with how Drill executes queries can also help. 

Review comment:
       I think it's okay for this introductory page to be vague and high-level.  Partitioning is discussed in more detail in its own child page.




-- 
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: dev-unsubscribe@drill.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org