nicoloboschi opened a new issue, #19361: URL: https://github.com/apache/pulsar/issues/19361
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version Master ### Minimal reproduce step https://github.com/apache/pulsar/pull/17153 introduces per topic or per namespace entry filters. The way it's implemented is not very efficient because every time a new topic is created in the broker, the attached entry filters are searched in the filesystem and unzipped. This operation is cpu intensive and it's a waste of resources, considering topics count order of magnitude. ### What did you expect to see? It'd be better to gather all the existing entry filters at the broker startup and create only one classloader per entry filter. When the topic is created, the related class loader is ready and the broker only needs to instance a new `EntryFilter` object, reusing the same classloader. ### What did you see instead? See Minimal reproduce step ### 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]
