Support Questions
Find answers, ask questions, and share your expertise
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

kudu is slower than parquet?

Re: kudu is slower than parquet?

Expert Contributor

If you are under the scale limits consider increasing # of partitions. Impala tends to use one thread per partition when scanning.

Re: kudu is slower than parquet?

This is a good suggestion, we are under the scale limits.
We may run another test in a later time, e.g. increasing # of partitions...

Re: kudu is slower than parquet?

Expert Contributor

Impala heavily relies on parallelism for throughput so if you have 60 partitions for Kudu and 1800 partitions for Parquet then due to Impala's current single-thread-per-partition limitation you have built in a huge disadvantage for Kudu in this comparison.


Please let us know if you re-run your comparison test.


Re: kudu is slower than parquet?


I have been re-run the test, and kudu perform much better this time(though it's still a little bit slower than parquet), thanks for @mpercy's suggestion.

I changed two  things by re-runing the test:

1, increase the partitions for the fact table from 60 to 768(affact all queries)

2, change the query3.sql 'or' predicate into 'in' predicate, so predicate can push down to kudu(only affact query 3)


below is the re-run result:

(column 'kudu60' is the previous result, which means the partitions of fact table is 60 ) 

(column 'kudu768' is the new result, which means the partitions of fact table is 768



Don't have an account?
Coming from Hortonworks? Activate your account here