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.

Sign up for GitHub

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

Jump to bottom

Performance issue on c6a.metal vs c6a.4xlarge and chDB vs clickhouse-local #254

Open
auxten opened this issue Aug 13, 2024 · 0 comments
Open

Performance issue on c6a.metal vs c6a.4xlarge and chDB vs clickhouse-local #254

auxten opened this issue Aug 13, 2024 · 0 comments
Assignees
@auxten
Labels
Performance Performance is not as expected

Comments

@auxten
Copy link
Member

auxten commented Aug 13, 2024

Performance issue on c6a.metal vs c6a.4xlarge

chDB (Parquet, partitioned) c6a.metal is slower than c6a.4xlarge on Q0-Q7, Q36-Q42
Google Chrome 2024-08-13 10 41 13

chDB (MergeTree) c6a.metal is slower than c6a.4xlarge on Q1-Q7, Q36-Q42
Google Chrome 2024-08-13 11 19 26

Performance issue on chDB vs clickhouse-local

chDB (Parquet, partitioned) and chDB(MergeTree) is 3~4 times slower than ClickHouse (Parquet, partitioned) on c6a.metal, 500gb gp2 for Q4, Q5, Q29

Google Chrome 2024-08-13 11 12 32
@auxten auxten self-assigned this Aug 13, 2024
@auxten auxten added the Performance Performance is not as expected label Aug 13, 2024
@auxten auxten moved this to Todo in chDB 2024 Q4 Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@auxten auxten

Labels
Performance Performance is not as expected
Projects
chDB 2024 Q4
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@auxten