Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[improvement](statistics)Use key column id to query column statistic table. (#28885) #29293

Merged
merged 1 commit into from
Dec 29, 2023

Conversation

Jibing-Li
Copy link
Contributor

Use id as where predicate to load column statistic cache. This could improve performance, because id is the first order key in column statistics table.

backport #28885

Proposed changes

Issue Number: close #xxx

Further comments

If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...

…table. (apache#28885)

Use id as where predicate to load column statistic cache. This could improve performance, because id is the first order key in column statistics table.
@Jibing-Li Jibing-Li marked this pull request as ready for review December 29, 2023 07:41
@Jibing-Li
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.63 seconds
stream load tsv: 586 seconds loaded 74807831229 Bytes, about 121 MB/s
stream load json: 20 seconds loaded 2358488459 Bytes, about 112 MB/s
stream load orc: 66 seconds loaded 1101869774 Bytes, about 15 MB/s
stream load parquet: 32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select: 29.5 seconds inserted 10000000 Rows, about 338K ops/s
storage size: 17162987653 Bytes

@xiaokang xiaokang merged commit c60eb77 into apache:branch-2.0 Dec 29, 2023
23 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants