In the context of use case to '...generate as many Kudu blocks as possible...', the 'kudu test loadgen' tool can do better job if exercising a load pattern which maximizes throughput and avoids compaction activity on tablet servers.
In short, the default behavior should change for the auto-created table case, so the tool would:
- create a table with N partitions (where n == number of generator threads)
- let each worker thread insert sequentially into its own partition
Current option of having hash-partioned auto-created table should be preserved, but turned off by default. For some test scenarios, it makes sense to exercise data load patterns which involve a lot of compaction activity on the tablet servers.