Whole project recompiles with each keystroke

[xster]

Sometime between version 0.64.1 and now, the build triggering behavior seems to have changed. Whereas changes within a file still produced a reasonably fast auto-complete, it seems like each keystroke now triggers a rebuild of the entire project including the edited file, other files in the project and all declared Java dependencies. This seems to generally make auto-complete unusable since one is likely typing around the time auto-complete is needed and if each keystroke triggers a 1 minute build, auto-complete is generally always loading.

Perhaps it's possible to restrict the rebuilding to the edited file, or cache all the symbols from the previous build until the next build is ready?

Environment

• Operating System: macOS 10.15
• JDK version: 11.0.4
• Visual Studio Code version: 1.52.1
• Java extension version: 0.64.1

Additional Informations

When I start typing, it triggers the below in the Java Build Status pane. Each build takes a few minutes.

8394ded0 Building [Done]
ba7e2d19 Validate documents [Done]
00cd587d Publish Diagnostics [Done]
c9fb754c Building [Done]
467b8d20 Building [Done]
a25e99a1 Validate documents [Done]
411b4544 Publish Diagnostics [Done]
c1bd89da Building [Done]
240f6be2 Building [Done]
a3536bca Building [Done]
6cea6ad2 Building [Done]

[testforstephen]

Duplicated with #996

The "Building" message you saw in the status panel is just a fake message, not representing a compilation operation.

[testforstephen]

Java extension version: 0.64.1

Your Java extension version is a little old, could you update all Java extensions to the latest version and try again?

AFAIK, the side Java extensions such as Java test runner pushed a bunch of performance improvement against the auto completion performance in the past few months.

BTW, do you enable file auto save? the file save is probably triggering the auto build job.

[xster]

Thanks.

File auto save is off. I'm trying now on 0.73.0 with Java 11. Same symptom. I think the "building" messages are actually doing something, since each of them breaks down (while running) into a building 123/1000 files message.

[deekshithanand]

I can confirm this issue for me. Each keystroke causes the circular arrow to rotate and I get similar messages like shared above. I had disabled java autobuild and auto save was disabled by default for me

[dbarvitsky]

The "Publish Diagnostics" takes the longest for me. I frequently see java processes (2 of them because of the hybrid mode) in the background hugging the CPU (200-300% spikes), notably after the change to a Java file is made. It slows down the intellisence, and one has to wait for good 10-30 seconds for the auto-completion hints to appear. I attempted the following:

• setting user-level "telemetry.telemetryLevel": "crash" - didn't have any effect (would be nice if Java respected that, actually).
• setting workspace-level "redhat.telemetry.enabled": null or false - seems like does not have any effect and only applies to the Kubernetes plugin.
• reloading the vscode, clearing the Java workspace cache, etc - nothing worked.

If I can make a suggestion:

• it would be nice if background compilation could be debounced somehow (i.e. start background build after a few seconds of accumulating changes and after there has been no changes for couple more seconds). This way we would not have "wasted" compilation cycles as user types.
• do not block intellisense and auto-completion on background tasks. I'd rather have it slightly out of date but immediately available rather than waiting half of minute for it to come back with a better result. For things like refactoring I don't mind waiting though.

[kkilictepe]

Same here. Intellisense performance is terrible. Any update?

[DrewCCannedy]

Same issue, would love an update.

[snjeza]

@DrewCCannedy @kkilictepe @dbarvitsky @deekshithanand @xster Could you provide a project example reproducing the issue?

[kkilictepe]

@snjeza I cant share as I am working on a commercial project.Anything else (logs etc?) that I can provide but the project codes itself?
My project is huge, with a lot of internal dependencies.

[d3milord]

I actually found out what could be the issue.
I started with the same problem as described by @xster with a cyclic Building,Validate,Publish routine at each keystroke.

After I've searched for build in the full settings page, I found that the extension "Language Support for Java(TM) by Red Hat" (ID: redhat.java) has a setting named "Java > Autobuild: Enabled" ("java.autobuild.enabled") set at True by default.
It triggers (as the name says) an automatic build after some event (code/text changes). After I disabled it the automatic fire of the build has stopped. It only keeps doing the "Validating" step at each keystroke and sometimes the "Publish" one.

Probably the Validating step is controlled by the intellisense to validate the code at each change. It could be made after a delay, but for me it's not impacting the performance a lot as the Build step.

Intellisense speeded up even in complex legacy projects and it seems the entire usability has improved.
Actually I'm still trying to find out what are the downsides of haing disabled that autobuild.

Let me know if you know something about that feature.

[snjeza]

@d3milord
If you set java.autobuild.enabled=true , Java LS will build your workspace only when you save a file.
Could you show your settings.json?

[d3milord]

{
    "java.jdt.ls.vmargs": "-XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx1G -Xms100m -javaagent:\"c:\\Users\\davidepecorari\\.vscode\\extensions\\gabrielbb.vscode-lombok-1.0.1\\server\\lombok.jar\"",
    "files.exclude": {
        "**/.classpath": true,
        "**/.project": true,
        "**/.settings": true,
        "**/.factorypath": true
    },
    "redhat.telemetry.enabled": false,
    "editor.suggestSelection": "first",
    "vsintellicode.modify.editor.suggestSelection": "automaticallyOverrodeDefaultValue",
    "git.confirmSync": false,
    "git.enableSmartCommit": true,
    "java.configuration.runtimes": [
        {
          "name": "JavaSE-1.8",
          "path": "C:\\Program Files\\Java\\jdk1.8.0_202",
        },
        {
          "name": "JavaSE-11",
          "path": "C:\\Program Files\\Java\\jdk-11.0.13",
          "default": true
        }
    ],
    "java.referencesCodeLens.enabled": true,
    "java.debug.settings.showHex": true,
    "json.schemas": [],
    "workbench.startupEditor": "none",
    "workbench.colorCustomizations": {},
    "java.inlayHints.parameterNames.enabled": "none",
    "workbench.editor.enablePreviewFromQuickOpen": true,
    "workbench.editor.enablePreview": false,
    "java.debug.settings.enableRunDebugCodeLens": false,
    "java.help.showReleaseNotes": false,
    "java.autobuild.enabled": false,
    "maven.dependency.enableConflictDiagnostics": false,
    "javascript.suggestionActions.enabled": false,
    "typescript.suggestionActions.enabled": false
}

[snjeza]

@d3milord could you remove the gabrielbb.vscode-lombok extension and update java.jdt.ls.vmargs to

 "java.jdt.ls.vmargs": "-XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx4G -Xms100m ",
   

See Lombok Support

[francescodedomenico]

I can confirm this is happening to me on a large enterprise Java Project with hundreds of classes (sometimes large ones too, 6000+ lines of code).
It's a Spring Boot Gradle Project, and I got the message that the language server got out of memory.

When I do get an Intellisense suggestion it comes with a 20 seconds delay (when lucky), often it shows no popup at all, making it hardly usable.

The curious thing here is how fast is Language Server for Java by Netbeans instead, while it doesn't have the features I need the code suggestion are almost instantly provided.

I did my tests on a brand new vscode installation with vscode-java only enabled as extension.