Programming language you’re coding in: .NET, JavaScript
Is connected mode used: Yes
SonarQube Cloud
And a thorough description of the problem / question:
On files with large numbers of errors the system takes a ridiculously long time to analyze and save the file. These save times can be in excess of 30 seconds per save per file. This is unworkable. We have detected in the debug logs that there are many dozens of calls out to the EU Sonar Cloud server at 300-2500 ms each. We would like to switch to the US Sonar cloud server (as described in your documentation here) to see if the reduced response time improves our performance.
As for switching to SonarQube.us, that’s not something that can be done at the developer level. It would requiring creating an entirely new organization and reimporting all your projects into the US instance.
Hi Anne. Here is a log captured from saving one of the smaller files. As you can see from the timestamps its taking almost two minutes to save due to the remote calls.
As for the US setup, we would be willing to do a test to see if that resolves the issue. It could be limited in scope rather than a copy of the entire org.
Sorry for the late response.
Thanks for report. I checked the logs, they are truncated unfortunately, but I see very long response time of the server.
Two questions:
Does it work OK if you will remove the binding/connection with SonarQube Cloud?
You mentioned files with large numbers of errors. How large the numbers are? Can you give the order of magnitude? Not only in the file you analyze, but also the whole project numbers as well.
Also regarding the truncated logs. Is it possible to provide full output from the IDE start including the analysis of at least one file. If it’s possible please remove any sensitive data, like user name and folder names.