Hello,
I am running Sonar analysis with Maven plugin for Java software using the following setup:
OS: RHEL 8.10
Java version: 17.0.16 (Red Hat)
Maven version: 3.9.11
Maven plugin: org.sonarsource.scanner.maven:sonar-maven-plugin:5.5.0.6356:sonar
Sonar: Data Center Edition v2025.1.1
Sonar Cryptography plugin version: 1.5.0
Sonar profile rules (only two): 1) sonar-java-crypto:Inventory and 2) sonar-java-crypto:JavaNoMD5use
Analysis works fine for other than large projects. For large projects I run out of heap memory. I have had to bump up the max heap all the way to 90 GB (SONAR_SCANNER_JAVA_OPTS=-Xmx90g) to get the analysis through for the largest projects.
Is it possible for end users to bring down memory consumption somehow? I have analyzed the largest projects in parts as a workaround, but that is inconvenient. Is it possible to change the plugin/rule logic to consume less memory?
Hello,
I am running Sonar analysis with Maven plugin for Java software using the following setup:
OS: RHEL 8.10
Java version: 17.0.16 (Red Hat)
Maven version: 3.9.11
Maven plugin: org.sonarsource.scanner.maven:sonar-maven-plugin:5.5.0.6356:sonar
Sonar: Data Center Edition v2025.1.1
Sonar Cryptography plugin version: 1.5.0
Sonar profile rules (only two): 1) sonar-java-crypto:Inventory and 2) sonar-java-crypto:JavaNoMD5use
Analysis works fine for other than large projects. For large projects I run out of heap memory. I have had to bump up the max heap all the way to 90 GB (SONAR_SCANNER_JAVA_OPTS=-Xmx90g) to get the analysis through for the largest projects.
Is it possible for end users to bring down memory consumption somehow? I have analyzed the largest projects in parts as a workaround, but that is inconvenient. Is it possible to change the plugin/rule logic to consume less memory?