Performance impacts on Visual Studio 2022 with SonarLint installed

Visual Studion 2022 latest version
SonarLint latest version

I use SonarLint all of the time (love it) and I typically Run Code Analysis on whole solution and then I see my hundreds of errors and I start working on them (lots of legacy code to fix).

None of the rest of my team is willing to install SonarLint due to the fact that Visual Studio seems to really slow down when it is installed. I am guessing this is due to the continuous scanning and checking it does while you are coding.

Can you add some settings options to maybe not check as often or something equivalent to increase perceived performance.

Mark

Hey @mhewitt!

Do your users face the same performance issues when analyzing the entire (full) solution is not selected?

By default, Visual Studio is configured to only run Roslyn analyzers on files that are currently open. You can customize the scope of analysis to include the current document, all opened documents, or the entire solution; it’s also possible to configure the Roslyn analysis to run in a separate process in the same options window. Note that running analyses on the entire solution is more processor-intensive.

Thanks for your helpful reply and sorry for the late response. I didn’t know about these settings so that was very helpful to know. But I did confirm that I am set to analyze current document and I do run the analysis in a separate process. I am still seeing performance slow down.