Vertica Enterprise Edition 9.3.1 and also VMWare CE version 10.0.0
When profiling some queries I noticed that memory_allocated_bytes from v_monitor.query_plan_profiles is always NULL.
Further investigation into vs_system_views for query_plan_profiles view revealed that, counter_name being used is memory allocated (bytes).
from v_internal.dc_execution_engine_profiles
where counter_name = 'memory allocated (bytes)'
UNION
from v_internal.vs_execution_engine_profiles
where counter_name = 'memory allocated (bytes)'
Whereas neither of the tables referenced above have that value for counter_name!
with x as ( select distinct counter_name from v_monitor.execution_engine_profiles where counter_name ilike '%mem%' union select distinct counter_name from v_internal.vs_execution_engine_profiles where counter_name ilike '%mem%' ) select * from x order by 1 ;
Which of the counter_name values should really be used?
current allocated rid memory (bytes)
current memory allocations (count)
current memory capacity (bytes)
current memory overhead (bytes)
current memory padding (bytes)
current memory requested (bytes)
current unbalanced memory allocations (count)
current unbalanced memory capacity (bytes)
current unbalanced memory overhead (bytes)
current unbalanced memory padding (bytes)
current unbalanced memory requested (bytes)
memory reserved (bytes)
peak allocated rid memory (bytes)
peak memory allocations (count)
peak memory capacity (bytes)
peak memory overhead (bytes)
peak memory padding (bytes)
peak memory requested (bytes)
peak unbalanced memory allocations (count)
peak unbalanced memory capacity (bytes)
peak unbalanced memory overhead (bytes)
peak unbalanced memory padding (bytes)
peak unbalanced memory requested (bytes)
reserved rid memory (bytes)
