diff options
author | colin-mueller-sonarsource <colin.mueller@sonarsource.com> | 2020-03-06 16:17:09 +0100 |
---|---|---|
committer | sonartech <sonartech@sonarsource.com> | 2020-03-06 20:04:32 +0000 |
commit | 240f3d8bb56af9f162d61eb9fca4991b362198cd (patch) | |
tree | a9028d222ad91774f2e30ecb5040d7e46a5af815 /server/sonar-docs/src/pages/instance-administration/monitoring.md | |
parent | fb03a19566ef193e4860fb276824ff315ca5047d (diff) | |
download | sonarqube-240f3d8bb56af9f162d61eb9fca4991b362198cd.tar.gz sonarqube-240f3d8bb56af9f162d61eb9fca4991b362198cd.zip |
DOCS Remove true requirements from HW reccomendations
Diffstat (limited to 'server/sonar-docs/src/pages/instance-administration/monitoring.md')
-rw-r--r-- | server/sonar-docs/src/pages/instance-administration/monitoring.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/server/sonar-docs/src/pages/instance-administration/monitoring.md b/server/sonar-docs/src/pages/instance-administration/monitoring.md index fbabc6ebcde..f13cb0597fc 100644 --- a/server/sonar-docs/src/pages/instance-administration/monitoring.md +++ b/server/sonar-docs/src/pages/instance-administration/monitoring.md @@ -31,7 +31,7 @@ You may need to increase your memory settings if you see the following symptoms: You can increase the maximum memory allocated to the appropriate process by increasing the -Xmx memory setting for the corresponding Java process in your _$SONARQUBE-HOME/conf/sonar.properties_ file: * For Web: sonar.web.javaOpts -* For ElasticSearch: sonar.search.javaOpts +* For ElasticSearch: sonar.search.javaOpts (It is recommended to set the min and max memory to the same value to prevent the heap from resizing at runtime, a very costly process) * For Compute Engine: sonar.ce.javaOpts The -Xmx parameter accepts numbers in both megabytes (e.g. -Xmx2048m) and gigabytes (e.g. -Xmx2G) |