Daniel,
I cannot access your flame graph on imgur, but what is happening in your code
that leads to the jar scanning? All of my apps have run on Linux since
forever, so I don’t know what might be different with Windows, but I’ve found
that anything that uses the Java service loader should be t
Your heap is big enough when your GC performance is good enough.
Garbage collectors have improved tremendously over the years. My rule of thumb
used to be that I wanted the app to spend less than 1% of time in GC, but
that’s actually easy to achieve these days as long as your heap is big enough
be 240 in JAVA8 but this is what I
have found
I know there is no tomcat.service provided by tomcat: I was just
explaining the way we launch tomcat and where we specify java options,
like memory size..and there no options for the code cache is specified.
Il 25-Jul-24 15:56, Gregg, Jo
Ivano
48MB was the default in the olden days. It is 240MB now. I believe the change
came in Java 8 to accommodate the fact that the HotSpot compiler now compiles
all methods when they are hit for the first time.
Thanks
From: Ivano Luberti
Sent: Thursday, July 25, 2024 8:43 AM
To: users@tom
I don’t know about your most recent stack trace, but the first one had this
frame:
at javax.xml.parsers.FactoryFinder$1.run(FactoryFinder.java:293)
What’s the rest of the stack trace? I suspect you’re recreating a SAX parser
or parser factory over and over. The intent of those factories is t
