lhotari commented on issue #25046: URL: https://github.com/apache/pulsar/issues/25046#issuecomment-3625852696
> 3.0.10 > jdk17 > client 3.0.10 @g0715158 Please retest with Pulsar 4.1.2 version, running on Java 21.0.9 (or newer). Pulsar 4.1.x comes with ["PIP-430: Pulsar Broker Cache Improvements: Refactoring Eviction and Adding a New Cache Strategy Based on Expected Read Count"](https://github.com/apache/pulsar/blob/master/pip/pip-430.md) which improves performance significantly in the scenario you have described. Before PIP-430, when consumers "drop off the tail", the entries are no longer retrieved from cache, but have to be retrieved all the way from BookKeeper. This adds additional load and latency to the system. In PIP-430, you would still need to ensure that the broker cache is large enough to hold the in progress entries (batch messages). For a large number of partitions, you need a large broker cache size (configured with `managedLedgerCacheSizeMB`). You should also set `managedLedgerMaxReadsInFlightSizeInMB` to a reasoa You didn't mention how many subscriptions you have. Are there a lot of consumers on a single shared subscription, so that each partition has one shared subscription? -- 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]
