I am running Sonarqube on a monolithic application on our CI server and the scanner (not the Sonarqube server) is taking over 60GB of memory.

Is this normal?

What can I do so the scanner will not use so much memory during the Sonarqube scan?

1 Answer 1


Please refer to the following article on the SonarQube - SonarScanner setup best practices. It will be good if the following hardware recommendations are considered for the SonarQube installations. Following are some of the important considerations.

  • SonarQube server should be on a real DB not on H2.
  • The analysis should occur very close to the SonarQube DB.
  • I made sure to clarify. It is the scanner that is taking all the memory.
    – David West
    Commented Feb 3, 2021 at 22:34
  • We made absolutely sure that it is using a real database instead of H2. It is using ?MS SQL Server. We also checked to see if the database is located in the same datacenter as the jenkins node that runs the scan. They are both in the same datacenter.
    – David West
    Commented Feb 4, 2021 at 17:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.