lhotari commented on issue #24816: URL: https://github.com/apache/pulsar/issues/24816#issuecomment-3380106950
> About my 2. question - because of the "OutOfDirectMemoryError" I set dbStorage_writeCacheMaxSizeMb=128 and dbStorage_readAheadCacheMaxSizeMb=256 on bk02, because it was mentioned as a workaround in another thread. > Is it safe to assume that I can use the default values for these two settings again, after the update? I'm not aware of changes in this area between 4.0.4 and 4.0.7 . The tuning of various values depends on your environment. To avoid OutOfDirectMemoryError, you should be setting `managedLedgerMaxReadsInFlightSizeInMB`. There are some details in #23466 about tuning the broker cache and it also includes tuning of `managedLedgerMaxReadsInFlightSizeInMB`. The broker cache has significantly improved in Pulsar 4.1.x and if you'd upgrade to 4.1.1, you'd get the benefits of [PIP-430: Pulsar Broker Cache Improvements](https://github.com/apache/pulsar/blob/master/pip/pip-430.md). -- 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]
