This is an automated email from the ASF dual-hosted git repository.
lhotari pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 633017d6d4de Add missing space
633017d6d4de is described below
commit 633017d6d4de40bb7f450ec58fd63fd560eeb2ae
Author: Lari Hotari <[email protected]>
AuthorDate: Fri Oct 25 23:19:00 2024 +0300
Add missing space
---
blog/2024-10-24-announcing-apache-pulsar-4-0.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/blog/2024-10-24-announcing-apache-pulsar-4-0.md
b/blog/2024-10-24-announcing-apache-pulsar-4-0.md
index ebc919afa8c6..b0b2c55be700 100644
--- a/blog/2024-10-24-announcing-apache-pulsar-4-0.md
+++ b/blog/2024-10-24-announcing-apache-pulsar-4-0.md
@@ -43,7 +43,7 @@ Multi-tenancy in messaging systems presents unique
architectural challenges, par
The core advancement in Pulsar 4.0 comes through [PIP-322 Pulsar Rate Limiting
Refactoring](https://github.com/apache/pulsar/blob/master/pip/pip-322.md). At
its foundation is a token bucket algorithm implementation that unifies rate
limiting across broker, topic, and resource group levels. This eliminates the
previous split between "default" and "precise" rate limiters—a design choice
that had introduced unnecessary CPU overhead and lock contention in IO threads.
-The practical impact is straightforward: more predictable performance in
multi-tenant deployments, especially when multiple rate limiting conditions
intersect. While Pulsar already supports producer rate limiting, the community
is building on this foundation with
[PIP-385](https://lists.apache.org/thread/9wddmj4o5mrdst427r40rr7phqb05y6s) to
improve producer flow control —a key piece in completing Pulsar's end-to-end
QoS capabilities.
+The practical impact is straightforward: more predictable performance in
multi-tenant deployments, especially when multiple rate limiting conditions
intersect. While Pulsar already supports producer rate limiting, the community
is building on this foundation with
[PIP-385](https://lists.apache.org/thread/9wddmj4o5mrdst427r40rr7phqb05y6s) to
improve producer flow control — a key piece in completing Pulsar's end-to-end
QoS capabilities.
#### Rate Limiting and Capacity Management in Modern Messaging Platforms