Open qiaoleiatms opened 9 months ago
Currently, the calculation of metaspace size depends on the class count of JVM, application, agent and the adjustment (static/factor)
totalClasses := float64(jvmClassCount+appClassCount+agentClassCount+staticAdjustment) * (float64(adjustmentFactor) / 100.0)
But the 3rd party libraries introduced from classpath are no included, for example, below is a screenshot from a tomcat app:
Should take the libraries from classpath into count
Not included
pack build a war project such as spring-framework-petclinic with the paketo java buildpacks
pack build
war
The metaspace size may not correct or enough for a java project which introduces libraries with a large size from classpath
Currently, the calculation of metaspace size depends on the class count of JVM, application, agent and the adjustment (static/factor)
But the 3rd party libraries introduced from classpath are no included, for example, below is a screenshot from a tomcat app:
Expected Behavior
Should take the libraries from classpath into count
Current Behavior
Not included
Steps to Reproduce
pack buildawarproject such as spring-framework-petclinic with the paketo java buildpacksMotivations
The metaspace size may not correct or enough for a java project which introduces libraries with a large size from classpath