Does the number of records per partition in Kudu have a significant impact on performance? -


does number of records per partition in kudu have significant impact on performance?

i hoping performance testing of impala / apache kudu vs impala parquet formats, , wondering if there optimal number of records include per partition? there way set dynamically table may change in size on time?

i see in docs create 8 partitions ~800k records. 100k per partition reasonable when have millions or billions of records?


Comments

Popular posts from this blog

php - Vagrant up error - Uncaught Reflection Exception: Class DOMDocument does not exist -

vue.js - Create hooks for automated testing -

Add new key value to json node in java -