I started noticing this a few hours back, but a kotlin project that we were using is taking approximately 4 times the time to complete scanning for SonarCloud. To test if this was part of something we changed on our code base, I tried the scan on a branch from a few days back with the same result. W…

@geojakes A new version of the Kotlin analyzer was deployed today and it contains SONARKT-186 which should positively impact the analysis time of larger projects with a large amount of dependencies. Can you confirm you see better performance?

Hello, This is certainly linked to the fact we released a new version of the Kotlin analyzer which gives better results. We were not expecting any significant performance impact so could you share some data? Does it move from 30 to 120 seconds (which will be still acceptable) or you are talking ab…

Similar issues on one of our projects running against sonarcloud. previously it was about 60-70 seconds looking at gradle enterprise scan data today we are failing due to it seeming to lock up for over 10 minutes at which point circleci kills the job. Only a single job has gotten through today an…

Hi, Alex, Thanks for responding to this swiftly. The performance is 4 times slower than its normal, ie 600,000 lines scanned in 6 minutes went to an average of 20-23 minutes. I have noticed > 30 minutes of scan time when re-enabling sonar after a long time in the project, but this situation isn’t t…

Hello, I’m coming back to you guys with some news. I did a mistake when I announced our new Kotlin analyzer release. I should have mentioned that the analysis will take more time than before … simply because we provide a deeper analysis than before. In the past, we were just looking at the Kotlin s…

Hello, A patch has been deployed today on SonarCloud. Can you confirm it helps to get better performance? Thanks

If some of you still have performance problems while analyzing Kotlin code with Gradle, can you share with me the output (a file) of the following command: gradle clean build sonarqube --no-build-cache --info I can create a private discussion channel with whoever needs it in case you want to share…

From sending in my logs, the response was that the cumulative run time of all the compile processes were longer than the sonar scan time, eventhough those compile times are from parallel threads. The current patch here is setting the following parameters, that halved the build time (though it’s stil…

To close this thread here is a summary: scanning Kotlin code with SonarCloud takes more time today than before and this is because we improved the precision of the rules thanks to a new engine ; this accuracy is having a cost there is nothing we can do immediately to improve the situation it’s par…

I guess I hit this problem as well but I get an OutOfMemory instead. Following the build: [image] Build software better, together GitHub is where people build software. More than 65 million people use GitHub to discover, fork, and contribute to over 200 million projects. …

Kolin project scan times dramatically increased today! Why?

SonarQube Cloud

felipebz (Felipe Zorzo) June 29, 2021, 6:10pm 2

Topic		Replies	Views
Kotlin's Sonar analysis taking too long SonarQube Cloud kotlin , performance , android , sonarqube-cloud	5	2313	November 19, 2021
Sonar CLI analysis take too long SonarQube Cloud scanner , sonarqube-ide , sonarqube-cloud	10	292	January 10, 2025
Kotlin Sensor too slow SonarQube Cloud kotlin , performance	17	2211	January 4, 2022
Slow kotlin sensor SonarQube Cloud kotlin	5	192	December 5, 2025
Gradle scanner v4.3.0.3225 launches several `prepareKotlinBuildScriptModel` increasing build time SonarQube Cloud kotlin , gradle , scanner , android , bug	4	718	January 29, 2024

Kolin project scan times dramatically increased today! Why?

Related topics