[IOTDB-6310] Optimize for query resource init #12160
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
we use timefilter to filter useless timepartition instead of getting all of them and then filter tsfile in them one by one.
We insert
0~9999
points whose timestamp is also0~9999
and executeflush
after each point insert and then insert one point with timestamp now(). As so, we will get two partitions, one contains 10,000 tsfiles, another one contains only one tsfile.execute the following sql: (only the last tsfile satisfies)
before opt, the time for query init tsfile list are:(about 2.5ms)
after opt, the time for query init tsfile list are:(about 0.047 ms)