Is there a significant difference in performance when using Netbeans IDE with JDK 9 instead of JDK 8?

Question

There is some significant difference in performance that justifies using Netbeans with JDK 9 instead of JDK 8?

Briefly, I’d like to know if Netbeans performs better (lower memory consumption, cpu...) with JDK9 or if version 8 does better at this point?

Answer 1

JDK 9 update

Project Jigsaw was promised long ago as a way to allow programmers to write code that included independent modules. Jigsaw’s goal is to define a standard module system for the Java platform and use it to modularize the platform itself and applications. Jigsaw was designed to be included in Java 8, but lost this, so it is now proposed for Java 9.

In a post on the Openjdk mailing list, Mark Reinhold, chief architect of Oracle’s Java platform group, said that the current build implements all the changes described in this JEP, except that the jrt provider: file system has not yet been implemented and the extension mechanism has not yet been removed.

These packages are intended to allow developers to try Project Jigsaw without having to compile it from sources. The builds are available on the JDK 9 project website.

Changes have also been made in some of the Sgps. Jeps, Java Enhancement Proposals, are being used to allow new features to be discussed and developed without going through a full formal specification (JSR). PEC that are popular and successful will be presented as part of the next full formal specification.

Updated Jeps provide unified JVM registry and more build controls.

Unified JVM Logging (JEP 158) will provide a common logging system for all JVM components. This will change the current way the JVM reports events in its subsystems and add common command line options. This JEP was heavily influenced by what exists in Oracle’s JVM Jrockit, according to the proposal.

The second JEP to be updated, JEP 165, proposes to improve the control of JVM compilers by encapsulating control in a set of options. This would allow different sets of options to be applied depending on the method being compiled and opens the possibility to change sets of options during runtime.

Suggestions were made as Jeps (Java Enhancement Proposals). The Pecs provide a path for new features to be discussed and developed without going through a complete formal specification (JSR). The less formal approach makes it possible to make proposals that overcome a specific problem.

The idea is that if a JEP is popular and successful, it will be presented as part of the next complete formal specification. This approach makes it possible to have incremental Jeps, rather than a large group of changes at the same time. This is the first time Jeps have been used and the list that Oracle has come up with is relatively small.

The proposed JEP for JDK 9 starts with improvements to the process API used to control and manage operating system processes. Java SE offers limited support for native operating system processes, with a basic API for setting up the environment and starting a process. The suggestion is that this should be extended so that developers no longer have to resort to native code.

The improvements to the conflict lock are the next suggestion, aiming to improve the performance of the disputed Java object monitors, as measured by a set of benchmarks and tests. This would result in better performance in situations where multiple segments compete for access to objects. Another JEP is the provision of a segmented code cache that will divide the cache code into distinct segments, each of which contains compiled code of a specific type, to improve performance and allow future extensions. This would be particularly applicable to large applications.

The development of a lightweight JSON API to consume and generate JSON documents and data streams has also been suggested. This would aim to meet the needs of Java developers using JSON.

A better version of Smart Java Compiler (sjavac) is another proposal, Smart Java Compilation Phase 2. The idea is that sjavac should be improved so that it can be used by default in JDK compilation and that it should be generalized so that it can be used to build large projects beyond JDK.

The final JEP is for modular source code. This is an internal exercise to reorganize the JDK source code into modules, improve the build system to compile modules and impose module limits at build time.

The full list of Jeps can be viewed on the Openjdk website.

Answer 2

No, absolutely no difference in PHP development.

That’s because the JDK (Java Development Kit) is, as the name says, a set of tools that serves to java programming.

Netbeans is an IDE that, say, has a good relationship with Java, it is common to see Java programmers using it and even read in the Oracle blogs indication to download it.

For this reason you might have seen something talking about Netbeans and the new JDK, but this does not interfere with programming other languages, as in the case of PHP.

Answer 3

Netbeans is a full-fledged, slow, heavy IDE that consumes a lot of PC resources, not to escape it.

Netbeans does not use SDK for it, it uses the SDK when using it to program JAVA.

The version of the JDK you put up will define what you will previously want to do, an example that changes are slight differences in the JRE profile to be chosen ( again, only changes in JAVA projects, for PHP does not change anything).

Maybe lambda support will change from one version to another and other things like that, but it’s internal changes, pro programmer won’t change, and netbeans performance by itself won’t change, but since I don’t program JAVA I can’t say exactly if something changes in project writing.

It already has a good answer, I won’t go into it, but a remark, the Netbeans IDE is very thorough, but it doesn’t compensate for use if you don’t use its biggest tool, which is customization, for example, the version I use is all changed, which even complicates me when I need/want to upgrade to a newer version.

Another remark, Netbeans with JDK9 does not believe it is recommended, as the official website itself indicates that it has support only, there is no official documentation on its use as there is for JDK8 or earlier.