Hongten commented on issue #18506: URL: https://github.com/apache/pulsar/issues/18506#issuecomment-1333320663
I think [this document](https://pulsar.apache.org/docs/2.10.x/admin-api-namespaces/#configure-dispatch-throttling-for-topics) is very SIMPLE. The document doesn't show us how to verify the throttle, just call the `get-...` API to show the values which come from the ZK(We can tell users we save these throttling values with the exact path in ZK, right?). So there are some suggestions you can refer to - How to set the publish rate? How to verify it(e.g. we can refer to some metrics `pulsar_throughput_in`)? Based on my test, it seems not to work when I set the publish rate(both bytes and message). - How to set the dispatch rate? How to verify it(e.g. we can refer to some metrics `pulsar_throughput_out`)? - What's the difference when we set broker, topic publish/dispatch rate? - What's the difference between setting publish/dispatch rate and setting a sourcegroup(Please refer to `[PIP-82](https://github.com/apache/pulsar/wiki/PIP-82:-Tenant-and-namespace-level-rate-limiting)`)? For the sourcegroup. I have some test results, which show the sourcegroup throttling does not work exactly. A: Only set the message publish rate = 100. One message size = 1024. However, the result is 14.7MB/s. The excepted result is 1MB/s. `bin/pulsar-admin resourcegroups create rs_name --msg-publish-rate 100`  B: Only set the byte publish rate = 10000(1MB). One message size = 1024. However, the result is 11MB/s. The excepted result is 1MB/s. `bin/pulsar-admin resourcegroups create rs_name --byte-publish-rate 10000`  Thanks Hongten -- 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]
