[
https://issues.apache.org/jira/browse/IOTDB-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309884#comment-17309884
]
Chao Wang commented on IOTDB-1260:
----------------------------------
only alter syncMetaLeader:
# The syncMetaLeader in CMManager.getAllpath accounts for 10 percent of the
performance of the query.
# The syncMetaLeader has been invoked in
ClusterPhysicalGenerator.transformToPhysicalPlan.
# The possibility of metadata change is small and cannot be the bottleneck of
query.
Solution:
remove syncMetaLeader in CMManager.getAllpath.
test result:
Time_Range AVG before optimization: 139.38
Time_Ranger AVG after optimization: 110.19
> optimize time_range query
> -------------------------
>
> Key: IOTDB-1260
> URL: https://issues.apache.org/jira/browse/IOTDB-1260
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Cluster
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
>
> According to the analysis of the flame diagram, there are three bottlenecks:
> 1. Pagereader read
> 2.CMMnager.getMatchedPaths 17%
> 3. syncMetaLeader 10%
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
