[
https://issues.apache.org/jira/browse/IMPALA-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699439#comment-16699439
]
Todd Lipcon commented on IMPALA-7541:
-------------------------------------
I took a whack at this here: https://gerrit.cloudera.org/#/c/11393/ but had
some bugs in the initial version of the patch. I dont have time to continue
working on it for a little while, but if someone picks it up they may want to
start by looking at the above patch.
> 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: Critical
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
