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/07/11 22:55:00 UTC

[jira] [Resolved] (IMPALA-7239) Mitigate ParseSmaps() overhead

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

Tim Armstrong resolved IMPALA-7239.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

> Mitigate ParseSmaps() overhead
> ------------------------------
>
>                 Key: IMPALA-7239
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7239
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.10.0, Impala 2.11.0, Impala 3.0, Impala 2.12.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Critical
>              Labels: perf, resource-management
>             Fix For: Impala 3.1.0
>
>         Attachments: mmap.c
>
>
> I've heard anecdotes of high system time spent in functions related this the smap parsing. It appears that this can be expensive on systems once the impalad virtual memory gets fragmented and there are 10s of thousands of maps.
> We can try to mitigate by reducing frequency of the parsing or disabling it entirely. I'm not sure if there are cheaper ways to get all of the same metrics.



--
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