@RunLLM How does

dispatchThrottlingOnBatchMessageEnabled

work?

When

dispatchThrottlingOnBatchMessageEnabled

is set to true, Pulsar applies dispatch throttling based on the number of entries (batches) rather than the number of individual messages within each batch. This can maximize throughput but may result in an inaccurate approximation of the total message count delivered to consumers, as each batch is counted as a single message regardless of how many messages it contains. Only one of

preciseDispatcherFlowControl

or

dispatchThrottlingOnBatchMessageEnabled

should be enabled at a time, as they are mutually exclusive. This setting is useful for high-throughput scenarios but may lead to over-delivery if batches contain many messages. For more details, see Pulsar throttling configurations. Would you like a deeper technical breakdown or configuration examples? Sources: - Pulsar throttling configurations 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

I believe this is incorrect

When dispatchThrottlingOnBatchMessageEnabled is set to true, Pulsar applies dispatch throttling based on the number of entries (batches) rather than the number of individual messages within each batch.

I'd expect the dispatch work based on the number of messages in the batch rather that just counting the batch as one "message" when the field is

true