简体   繁体   中英

SonarQube with C# plugin with MSBuild Runner takes a lot of time

Currently I have an instance of SonarQube 5.1.2 with C# plugin and MSBuild runner in order to analyze a 1.200.000 LOC project, the analysis is taking between 16 and 20 hours. Digging into the logs, the building process (including the execution of test) takes about 2 hours, starting from there, SonarQube start its analysis.

SonarQube is setup as it comes out of the box, it is installed in a machine with 8Gb in RAM, 4 processors. Usually, the analysis process only uses 20% of the CPU and 1.5 GB of RAM.

What actions should I take to reduce the analysis time?

Upgrade to the latest release version of SonarQube. Before SonarQube 5.2, a database connection was established from the analysis machine to the database, and there were a lot of round-trips to upload the analysis results.

Since 5.2, the analysis machine zips the analysis results and sends it to the server, which will process it and store it in the database in a much more optimized way.

Also feel free to investigate and report what the bottleneck is once you're on the latest released versions and if you still face performance issues.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM