Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
8.2, 10.0, 11.0
-
Ubuntu 18.10
Linux 4.18.0
12 core Xeon E-2176M with 64Gb RAM
-Xmx2536m (2.5Gb for NB, of which it uses about 1.7G)
NetBeans 10vc2, 10vc5, 8.2
JDK 11.0.1
JDK 1.8
G1GC, CMS GC, Serial GC
Description
I used to use NetBeans 8 on JDK8, it was tolerable, but slow.
Now I have a new laptop, I've tried nb8, nb10 on jdk8, jdk11, with g1gc, cmsgc, other gc. They are all UNUSABLY slow. By which I mean, it takes over a minute just to open a file.
Mostly this is because things are waiting for things waiting for very inefficiently implemnted file I/O, editor parsing, or things like that. I've watched a 12-core Xeon chip spend over 4 hours just attempting to handle the Active Reference Queue Daemon thread.
The slowdown is somewhat incremental - I can escape it as long as I'm happy to restart NetBeans every hour or so (which I'm not happy to do).
Attached a stack dump to get you started, this took over a minute to open a 284-line Java file from idle.
Please feel free to ask all the obvious questions, although I'm fairly sure all the obvious things have been done. Mostly, I've got GC down to a negligible amount.
If there's one or more features of NetBeans I can disable to get acceptable behaviour while still being able to realistically edit Java code, please tell me and I will disable them because I am at the end of my rope after using (and developing for) NetBeans for nearly 10 years. If I can get IntelliJ to load a Java/Gradle project neatly before this gets fixed, I'm gone.
Attachments
Attachments
Issue Links
- is duplicated by
-
NETBEANS-64 NetBeans tooks minutes to open
- Closed
- is related to
-
NETBEANS-2525 Background Scanning Process for first NetBeans start took more than 15min
- Open
-
NETBEANS-2785 Make NIO2 File Watcher Implementation as Default
- Closed