wangjialing218 commented on pull request #8611: URL: https://github.com/apache/pulsar/pull/8611#issuecomment-730802715
> If the rate limit is 100 msg/s, and I request 10000 msg concurrently at the same time, 10000 messages will still be read, but in the next 100 seconds, none of the messages will be read. This kind of scenario is very easy to simulate, just set the `ReceiveQueueSize` of `MultiConsumer` to be larger. Is this side effect too big? Yes，if we start concurrently read at same time, all conumser could start there first reading and make dispatch rate far over the limiter, this could be another issue and this PR does not aim to solve this. This PR make none messages read in the next 100 seconds to let the average dispatch rate return to 100 msg/s at last. In some case it is useful. Consider a topic we don't need to dispatch in real time, we could set a low dispatch rate and just keep the data in bookkeeper, left the network resource to other topics. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
