You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/11/28 00:38:00 UTC

[jira] [Work started] (IMPALA-6656) Metrics for time spent in BufferAllocator

     [ https://issues.apache.org/jira/browse/IMPALA-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on IMPALA-6656 started by Tim Armstrong.
---------------------------------------------
> Metrics for time spent in BufferAllocator
> -----------------------------------------
>
>                 Key: IMPALA-6656
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6656
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: observability, resource-management
>
> We should track the total time spent and the time spent in TCMalloc so we can understand where time is going globally. 
> I think we should shard them by CurrentCore() to avoid contention and get more granular metrics. We want a timer for the amount of time spent in SystemAllocator. We probably also want counters for how many times we go down each code path in BufferAllocator::AllocateInternal() (i.e. getting a hit immediately in the local area, evicting a clean page, etc down to doing a full locked scavenge).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org