[
https://issues.apache.org/jira/browse/IMPALA-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036425#comment-17036425
]
Vihang Karajgaonkar commented on IMPALA-7541:
---------------------------------------------
This is interesting. I think this may be a low-hanging fruit and not take a lot
of effort to fix this.
[~Xiaomeng Zhang] [~anuragmantri] Would one of you like to take this up? I will
put it on my plate for now. Feel free to assign it yourself if you are
interested.
> 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-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
