Sonarlint/sonarqube (VScode extension) takes 20 mins to connect to the sonarqube server

Setup Details:
Sonarqube Server enterprise edition: v10.8 (100206)[ACTIVE]
Hosted: On-Prem
VS code: 1.97.2 on Windows 11 platform
Sonarlint/Sonarqube for IDE : 4.17.0
Remote SSH from VS code : Rocky Linux 9

We have VS code installed on our individual laptops. We are connecting to our EL9 dev servers using Remote-ssh plugin where the code is present.
vscode settings.json file:
‘’’
{
“sonarlint.connectedMode.connections.sonarqube”: [
{
“serverUrl”: “url”,
“connectionId”: “my-conn”,
“token” : “xyz”
}
],
“sonarlint.connectedMode.project”: {
“projectKey”: “proj_key”,
“connectionId”: “my-conn”
},
“sonarlint.pathToCompileCommands”: “/home/user/compile_commands.json”
}
‘’’
Issue:
When I start the workspace, it takes 20 mins for the sonarlint to connect to the sonarqube server from the Rocky Linux 9 machine.
I see that the sonarlint process has already started on the remote Rocky Linux machine as soon as I launch vscode.
Please let us know what we are missing.

Logs on Output Terminal:
Executing /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/jre/21.0.6-linux-x86_64.tar/bin/java -jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/server/sonarlint-ls.jar -stdio -analyzers /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonargo.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarjava.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarjavasymbolicexecution.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarjs.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarphp.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarpython.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarhtml.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarxml.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonartext.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonariac.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint-vscode-4.17.0-linux-x64/analyzers/sonarlintomnisharp.jar /home/user/.vscode-server/extensions/sonarsource.sonarlint_ondemand-analyzers/sonar-cfamily-plugin/6.64.0.81013/sonarcfamily.jar
[Info - 17:16:30.478] [sonarlint : SonarLint Server RPC sequential executor] Started embedded server on port 64120

[Info - 17:37:05.001] [sonarlint : SonarLint Local Storage Synchronizer] Downloaded settings in 41ms

[Info - 17:37:05.050] [sonarlint : SonarLint Local Storage Synchronizer] Downloaded plugin list in 8ms

[Info - 17:37:05.054] [sonarlint : SonarLint Local Storage Synchronizer] [SYNC] Synchronizing analyzer configuration for project ‘proj_key’
… After this the connection process to the sonarqube server starts.

I enabled some settings for debug and collected the output terminal output.
“sonarlint.output.showAnalyzerLogs”: true,
“sonarlint.output.showVerboseLogs”: true,
“sonarlint.trace.server”: “verbose”

Attached the output file.
SonarQube for IDE.log (11.1 MB)

Below is the last line where the search events ended and this was going on for 20 mins.
[Debug - 21:59:37.762] [sonarlint : Smart Notifications Polling] GET 200 https://sonarqube.corp.aryaka.com/api/developers/search_events?projects=project_key_used&from=2025-03-06T21%3A58%3A37-0500 | response time=8ms

Please help!! We are stuck here!!

Hello @sameersondur,

It is not the synchronization with the server that takes a lot of time, it’s the listing of files from the VSCode host:

[Trace - 10:00:17 PM] Sending response ‘sonarlint/listFilesInFolder - (5)’. Processing request took 1240898ms

SonarQube for IDE tries to load all files in memory at startup, and it takes a very long time, I assume due to the usage of remote-ssh. I’m afraid we can’t support your use-case with a decent performance for now.

FYI we are considering changing this initial loading to improve performance, see this ticket. Unfortunately, it is quite a big effort, so it will take us a while to fix things.

Sorry for not being more helpful