On 18/07/2025 16:04, Daniel Sheridan wrote:
I definitely think there is something happening on the Tomcat side here around caching, I've played with some resource caching settings but it didn't make any difference unfortunately.
The flame graph is showing that Tomcat is having to reload the JAR indexes that it uses to find files in JARs (so Tomcat doesn't have to search through every JAR every time it needs to load a new class).
That index gets removed (to reduce memory footprint) periodically if it isn't being used. By default this check happens every 10 seconds.
To speed things up try experimenting with the archiveIndexStrategy of the Resources element. I suspect you'll want to use "bloom". You will likely see a larger memory footprint but you should also see less (no?) delays.
Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
