kantianethics :
I understand the benefits of the Java Platform Module System (JPMS) for large applications, but is there any reason to make a small library or application into a (single) module? If so, are Modular Jar Files the best means of accomplishing this, or is the normal approach preferred?
Going forward, will there be performance implications for modularized v. classpath programs?
Michael Easter :
Immediate performance implications include the following:
- Modularized applications can opt to use jlink so that the distributable runtime is reduced in size: it only uses the modules you require. So if you don't need Swing, Corba, etc, it does not reside on disk. (more info here).
- Modularized applications use the module graph for classloading; the algorithm for this is much faster than the linear search of classpath (more info here).
This is by no means a guarantee that your app will be faster, but the above is undeniably attractive.
Longer term, consider this:
- Though experimental in JDK 9, there is an AOT compiler that (for Linux x64) will compile the
java.basemodule to native code. This is likely the path forward for future Java releases. Surely this will improve startup time in the future. (again, more info here)
Guess you like
Origin http://10.200.1.11:23101/article/api/json?id=464445&siteId=1