Hello @lucas-loegel_wkl
Thank you for reporting the performance issues you’re experiencing with SonarQube for Visual Studio.
We have investigated this issue and identified a threading problem within the code responsible for branch matching. It appears that the matching branch is being calculated multiple times concurrently from different threads. Given that your repository contains a significant number of branches (approximately 4000), this redundant computation can indeed lead to the high CPU utilization and performance degradation you are observing.
We have created a ticket on our backlog to address this issue: Jira.
We understand the impact this is having on your workflow and have prioritized this fix for our upcoming sprint. We will keep you updated on the progress through the ticket.
In the meantime, unfortunately, there isn’t a straightforward workaround we can suggest within the SonarQube for Visual Studio extension itself to directly mitigate this specific threading issue.
Thank you for your patience and understanding as we work to resolve this.
Kind regards,