[ https://issues.apache.org/jira/browse/DRILL-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812807#comment-16812807 ]
Aman Sinha commented on DRILL-3846: ----------------------------------- Let's try this after DRILL-7064 is fixed. > Metadata Caching : A count(*) query took more time with the cache in place > -------------------------------------------------------------------------- > > Key: DRILL-3846 > URL: https://issues.apache.org/jira/browse/DRILL-3846 > Project: Apache Drill > Issue Type: Bug > Components: Metadata > Reporter: Rahul Challapalli > Assignee: Aman Sinha > Priority: Critical > Fix For: 1.16.0 > > > git.commit.id.abbrev=3c89b30 > I have a folder with 10k complex files. The generated cache file is around > 486 MB. The below numbers indicate that we regressed in terms of performance > when we generated the metadata cache > {code} > 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from > `complex_sparse_50000files`; > +----------+ > | EXPR$0 | > +----------+ > | 1000000 | > +----------+ > 1 row selected (30.835 seconds) > 0: jdbc:drill:zk=10.10.100.190:5181> refresh table metadata > `complex_sparse_50000files`; > +-------+---------------------------------------------------------------------+ > | ok | summary > | > +-------+---------------------------------------------------------------------+ > | true | Successfully updated metadata for table complex_sparse_50000files. > | > +-------+---------------------------------------------------------------------+ > 1 row selected (10.69 seconds) > 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from > `complex_sparse_50000files`; > +----------+ > | EXPR$0 | > +----------+ > | 1000000 | > +----------+ > 1 row selected (47.614 seconds) > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)