poorbarcode commented on code in PR #19012: URL: https://github.com/apache/pulsar/pull/19012#discussion_r1057779163
########## site2/docs/cookbooks-message-throttling.md: ########## @@ -0,0 +1,86 @@ +--- +id: message-throttling +title: Message throttling +sidebar_label: "Message throttling" +--- + +## Message Dispatch throttling +Message dispatch throttling is a mechanism that limits the speed at which messages are delivered to the client. + +### When should I use message dispatch throttling? +* Messages are persisted on disk, `Storage` is the component for this part of the work. If a large number of read + requests fail to match the cache, the Storage becomes too busy and cannot work properly. Use message dispatch + throttling makes Pulsar work steadily by keeping Storage's read request load stable. +* An instance of 'Broker' serves multiple topics at the same time, and if a topic is too busy, it will occupy + almost all of the IO resources, other topics will not work well. Use message dispatch throttling can balance + the allocation of resources to agents across topics. +* There have large backlog of messages to consume, clients may receive a large amount of data in a short period of time, + thus monopolizing the client computer resources. Message dispatch throttling can also be used to balance the resource + allocation of the client computer. + +### Concepts of message dispatch throttling +- `ratePeriodInSecond` The unit of the rate limiting period is second. The default is 1s. Review Comment: Yes already clarified `ratePeriodInSecond` and add an example -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
