hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lei Chang <lei_ch...@apache.org>
Subject Re: hawq_rm_stmt_vseg_memory and hawq_rm_nvseg_perquery_perseg_limit
Date Sat, 21 Jan 2017 04:40:31 GMT
hawq_rm_stmt_vseg_memory and hawq_rm_stmt_nvseg need to be used together to
set the specific number of segments and the vseg memory. And
hawq_rm_stmt_nvseg should be less than hawq_rm_nvseg_perquery_perseg_limit.

set hawq_rm_stmt_vseg_memory = '2GB';set hawq_rm_stmt_nvseg = 6;

looks 16GB is somewhat small for big dedicated machines: if 16GB is per
virtual segment memory, if 8 segment is used, it only use 128GB.


On Fri, Jan 20, 2017 at 9:11 PM, Jon Roberts <jroberts@pivotal.io> wrote:

> Why is there a limit of 16GB for hawq_rm_stmt_vseg_memory?  A cluster with
> 256GB per node and dedicated for HAWQ may certainly want to utilize more
> memory per segment.  Is there something I'm missing regarding statement
> memory?
> Secondly, does the number of vsegs for a query get influenced by the
> statement memory or does it just look at the plan and
> hawq_rm_nvseg_perquery_perseg_limit?
> Jon Roberts

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message