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 2020/02/12 23:48:00 UTC

[jira] [Commented] (IMPALA-7541) Avoid instantiating metrics for IncompleteTables

    [ https://issues.apache.org/jira/browse/IMPALA-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035805#comment-17035805 ] 

Tim Armstrong commented on IMPALA-7541:
---------------------------------------

[~vihangk1][~stigahuang] might be of interest to you

> Avoid instantiating metrics for IncompleteTables
> ------------------------------------------------
>
>                 Key: IMPALA-7541
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7541
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Todd Lipcon
>            Priority: Major
>
> Currently we instantiate a Metrics object for every table. However in many cases, users have hundreds of thousands or millions of tables and only a small subset are loaded. This is even more likely after the new automatic invalidation work in progress. So, we should try to minimize memory footprint of IncompleteTable. The largest culprit there seems to be the new Metrics object added by IMPALA-4886. We should lazily init this only on *loaded* tables.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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