Dearest @Damien_Urruty,
would you be so kind to send it over in my direction as well?
Our codebase is huge and I stumbled upon files (10k+ LOC Jesus Christ with 95k Commit History) that bring the analysis to its knees.
I’d like to test it as well 
Topa 
Hey there,
Thanks for your patience. I didn’t have time to build a custom version… but instead we just released the change in the product! Could you please update and give it a try?
I downloaded the 11.17 version earlier today and did not notice any improvement so was hoping it did not include the ‘fix’. Still about a 13 minute delay with no messages be logged to the console. Was there a significant improvement on your QA/test system when running a project with about 4000 files and some of them being thousands of lines long?
@Damien_Urruty Never did see a response to my previous post. I have now downloaded 11.18 and the slowness seems to be resolved.
Hey @dandoy, I’m happy to hear that the issue is resolved on your end!
We effectively found another area of improvement, related to what you described. You should now notice a significant speed increase when analyzing multiple files in a Git repository.
Regarding your question about testing, you’re right to ask. We do have tests and monitoring to ensure the performance of SonarQube for IDE. However, it can be difficult to reproduce every unique user environment. The performance hit you experienced wasn’t simply a matter of analyzing many files or lines, which we test for. Instead, it was an issue that only appeared in a specific environment: when many files were analyzed in a single batch while working in a Git repository with a relatively large history.
I hope this answers your question.
Thank you once more for reporting it, as this discovery made our product better!