Apache Druid

you're asking a performance question: how can you get 6 or 8 tasks to do the work of 12 tasks?

best way to tackle that is to use a profiler to see where the time is going

i suggest attaching a profiler to one of your tasks, seeing what it does and if that leads to any ideas for next steps

feel free to post a profile result here and we can take a look

<@U0344FW86DD> We added new parameters to consumer properties that were not listed by druid but were still supported by Kafka. Will the druid be able to pick them up?

eg: `max.partition.fetch.bytes` `max.poll.records` etc

Druid ignores the consumer-group-related properties and serde-related properties (since we do our own offset management and our own deserialization)

Other properties are respected. So I believe the ones you listed would indeed be respected