-
Query performance optimization of Vertica
- Don't fetch any data that you don't need,or don't fetch any columns that you don't need. Because retrieving more data or more columns, which can increase network,I/O,memory and CPU overhead for the server. For example, if you need several columns you can use
AT EPOCH LATEST
SELECT fi.name, fi.InvestmentKey,id.VendorId,id.CUSIP,id.ISIN,id.DomicileCountryId,id.CurrencyId
FROM dbo.FixedIncome fi
INNER JOIN dbo.InvestmentIdDimension id ON id.InvestmentKey = fi.InvestmentKey
WHERE id.InvestmentId = 'B000023K1X'
But do not use:
AT EPOCH LATEST
SELECT fi.*, id.*
FROM dbo.FixedIncome fi
INNER JOIN dbo.InvestmentIdDimension id ON id.InvestmentKey = fi.InvestmentKey
WHERE id.InvestmentId = 'B000023K1X'
- To avoid blocking Vertica write process, we alway add the "AT EPOCH
LATEST" for query,which is snapshot read. for example, You can use
AT EPOCH LATEST SELECT ... FROM ...,
But do not use:
SELECT ... FROM ...
- Chop up a complex query to many simpler queries.
- Join decomposition, if posible, Sometimes, Using "In" clause or sub
query clause instead of a complex "JOIN" clause. like this, we can use
AT EPOCH LATEST
SELECT s1.CompanyId, id.InvestmentId, s1.InvestmentKey,id.VendorId,id.CUSIP,id.ISIN,id.DomicileCountryId,id.CurrencyId
FROM ( SELECT CompanyId,InvestmentKey FROM dbo.FixedIncome WHERE CompanyId = '0C00000BDL') s1
INNER JOIN dbo.InvestmentIdDimension id ON id.InvestmentKey = s1.InvestmentKey
WHERE id.VendorId = 101 OR id.VendorId = 102;
But do not use:
AT EPOCH LATEST
SELECT s1.CompanyId, id.InvestmentId, s1.InvestmentKey,id.VendorId,id.CUSIP,id.ISIN,id.DomicileCountryId,id.CurrencyId
FROM dbo.FixedIncome fi
INNER JOIN dbo.InvestmentIdDimension id ON id.InvestmentKey = s1.InvestmentKey
WHERE fi.CompanyId = '0C00000BDL' AND( id.VendorId = 101 OR id.VendorId = 102 );
- Try to use the temporary table to cache data, which can avoid scan an physical table for times.
- Try to push the outer predicate into the inner subquery clause, so that it is evaluated before the analytic computation
- For Top-K query, if posible, we'd better omit the order by clause, Or we'd better adding a filter condition for it.
- For sort operation, We can create Pre-sorted projections, so the
vertica can choose the faster Group By Pipeline over Group By Hash
- Please refer to the "Optimizing Query Performance" chapter in
reference manual of vertica, which doc's name is "Communiti Vertica
Community Edition 6.0"
[https://my.vertica.com/docs/CE/6.0.1/HTML/index.htm#12525.htm ]
-
相关阅读:
Atitit. C#.net clr 2.0 4.0 4.5新特性 v2 s22 1. CLR内部结构 1 2. CLR 版本发展史 3 3. CLR 2.0新特性 4 4. CLR 4 新特性
Hbase基本命令 悟寰轩
mvn常用命令 悟寰轩
linux添加tomcat服务 悟寰轩
hadoop基本命令 悟寰轩
Tomcat启动 悟寰轩
Eclipse自动部署项目到Tomcat的webapps下的有效方法 悟寰轩
MySQL改变默认编码为utf8 悟寰轩
myeclipse关闭自动更新 悟寰轩
Linux命令大全 悟寰轩
-
原文地址:https://www.cnblogs.com/s021368/p/3208679.html
Copyright © 2020-2023
润新知