Hi Andrew, One example, the jvm needs to scan every java class for specific annotations. The more unneccessary files in the classpath, the longer that takes. And the cache size is not unlimited, I have seen classpaths with more than 100mb in size. If shared classloader cache is used, common storage is also not unlimited. As soon as a cache is too small, it uses more cpu time. There is plenty of more stuff. I am not talking about the java applications that have 5mb jars in the classpath, but once started the classpath usually continues to grow.
Denis. -----Original Message----- From: Andrew Rowley <and...@blackhillsoftware.com> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> Sent: Fri, Apr 28, 2017 02:08 AM Subject: Re: JZOS Java CLASSPATH On 28/04/2017 4:34 AM, Denis wrote: > as the classpath size affects performance, its definitly a good idea to limit > the jars and its contents to what is required. > I wouldn't expect the classpath size to have a significant effect on performance, since Java can read and cache the directories from the jar files. A quick google search suggests this is the consensus. The bigger problem of course is management of dependencies. -- Andrew Rowley Black Hill Software +61 413 302 386 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to <a href="mailto:lists...@listserv.ua.edu";>lists...@listserv.ua.edu</a> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
