JavaOpts settings differences - Community vs Enterprise

SonarQube Server / Community Build
1

SonarQube LTS 8.9.6 Community vs Enterprise.

In preparation for upgrading from Community to Enterprise, we performed a comparison of the settings and identified the differences in sonar.properties listed below.

Question: is the different defaults based on an actual requirement of the Community vs Enterprise binaries or based on some assumptions of greater load or code size?

In other words, if the sizing worked fine using the Community Edition and we upgrade to Enterprise, all other things being equal, can we retain the existing smaller settings or must we move to the increased settings?


[sonarqube] $ diff sonarqube-8.9.6.50800/conf/sonar.properties sonarqube-8.9.6.50800-enterprise/conf/sonar.properties
81c81
< # Web server is executed in a dedicated Java process. By default heap size is 512MB.
---
> # Web server is executed in a dedicated Java process. By default heap size is 1GB.
93c93
< #sonar.web.javaOpts=-Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError
---
> #sonar.web.javaOpts=-Xmx1G -Xms128m -XX:+HeapDumpOnOutOfMemoryError
236c236
< # Compute Engine is executed in a dedicated Java process. Default heap size is 512MB.
---
> # Compute Engine is executed in a dedicated Java process. Default heap size is 2GB.
244c244
< #sonar.ce.javaOpts=-Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError
---
> #sonar.ce.javaOpts=-Xmx2G -Xms128m -XX:+HeapDumpOnOutOfMemoryError
253c253
< # It is executed in a dedicated Java process. Default maximum heap size is 512MB.
---
> # It is executed in a dedicated Java process. Default maximum heap size is 2GB.
268c268
< #sonar.search.javaOpts=-Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError
---
> #sonar.search.javaOpts=-Xmx2G -Xms2G -XX:MaxDirectMemorySize=1G -XX:+HeapDumpOnOutOfMemoryError
2

Hi @ianw :wave:

woah eagle eye here :slight_smile: The memory settings indeed differ intentionally in between the editions and are based on assumptions of greater load and code size. if you want to fine tune the memory consumption of your SonarQube instance you should monitor it closely and adjust these settings to your needs.

hope that helps