You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that came recently into my mind is, that constructing and analyzing of jars is quite expensive (e.g. open file, Zip headers must be read, iterate of the content and so on).
On the other hand, it is usual that many projects share the same jar at their classpath.... I therefore wonder if it would be possible to have a (maybe configurable/caller-supplied) ClasspathJar cache? There is already a JRT_CLASSPATH_CACHE but none for user-classpath entries.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
One thing that came recently into my mind is, that constructing and analyzing of jars is quite expensive (e.g. open file, Zip headers must be read, iterate of the content and so on).
On the other hand, it is usual that many projects share the same jar at their classpath.... I therefore wonder if it would be possible to have a (maybe configurable/caller-supplied)
ClasspathJarcache? There is already aJRT_CLASSPATH_CACHEbut none for user-classpath entries.Beta Was this translation helpful? Give feedback.
All reactions