liangyepianzhou commented on PR #25367: URL: https://github.com/apache/pulsar/pull/25367#issuecomment-4107638242
> The flamegraph in [#25367 (comment)](https://github.com/apache/pulsar/pull/25367#issuecomment-4095828178) looks like it was from an old version of Pulsar that uses Guava Cache (before #23052 <3.0.6, <3.3.1). @liangyepianzhou What version of Pulsar are you load testing? The **flamegraph** comes from 3.0.5, I change version to 3.0.13 and make `topicNameCacheMaxCapacity ` = -1. CPU usage dropped from 90% to 9%, but the percentage of `TopicName.get()` in the flame graph is still very high. >The benchmark seems to measure the miss of 1M cache entries. That's not a very realistic scenario that there would be such amount of misses at once. In my scenario, one topic has 1 million partitions, so there are 1 million cache misses during the initial startup. Topic loading is currently very slow, and I suspect this may be one of the reasons. -- 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]
