Shawyeok opened a new issue, #21442: URL: https://github.com/apache/pulsar/issues/21442
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version After enabled the `preciseTopicPublishRateLimiterEnable` configuration in `broker.conf`, if one topic on the broker exceeds the publish rate limit (for example, 1MB/s), it will cause lock contention, leading to an increase in the 99th percentile write latency for other topics that have not reached the rate limit. <img width="1728" alt="image" src="https://github.com/apache/pulsar/assets/5058708/4d2f69ab-f827-448c-92f3-5c69f7029d0b";> [pulsar-3.0.1.lock.profile.008.html.zip](https://github.com/apache/pulsar/files/13164263/pulsar-3.0.1.lock.profile.008.html.zip) ### Minimal reproduce step Noticed in a fork of `2.8.1`, reproduced in `3.0.1` on Linux CentOS 7.9 `3.10.0-1160.99.1.el7.x86_64` ```shell pulsar-admin namespaces create public/ratelimited pulsar-admin namespaces set-publish-rate -b 1048576 public/ratelimited pulsar-admin namespaces policies public/ratelimited pulsar-perf produce persistent://public/default/no-rate-limit pulsar-perf produce -r 1600 -ioThreads 4 -n 100 persistent://public/ratelimited/topic-1 ``` ### What did you expect to see? One topic exceeds publish rate limit should not effect other topics write latency. ### What did you see instead? Another topic write latency also increased. ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
