Base Information:
-
SonarQube Server Version: 10.8.1
-
Deployment Method: Helm
-
Cluster: EKS (v1.30)
-
Goal: Achieve stability and fast Web UI response without delays
-
Actions Taken: Tested various CPU/Memory configurations and adjusted SonarCE/SonarWEB parameters
Description of issue:
Hi,
I have a SonarQube setup running in an EKS cluster (v1.30), deployed using Helm with custom resource configurations. Recently, I upgraded SonarQube from 10.7.0 to 10.8.1 and noticed a significant increase in resource demands.
In SonarQube 10.7.0, the following resource parameters provided stable performance:
resources:
limits:
cpu: 2000m
memory: 8Gi
requests:
cpu: 1000m
memory: 6Gi
sonarProperties:
sonar.web.javaOpts: -Xmx1024m
sonar.ce.javaOpts: -Xmx4096m
However, after upgrading to 10.8.1, I had to extend these parameters to maintain some level of stability:
resources:
limits:
cpu: 8000m
memory: 26Gi
requests:
cpu: 6000m
memory: 24Gi
sonarProperties:
sonar.ce.javaOpts: "-Xms6g -Xmx10g"
sonar.web.javaOpts: "-Xms8g -Xmx10g"
sonar.search.javaOpts: "-Xms4g -Xmx4g"
sonar.web.javaAdditionalOpts: "-XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:+HeapDumpOnOutOfMemoryError -XX:InitiatingHeapOccupancyPercent=35"
Despite these changes, I’m still experiencing delays in the SonarQube Web UI — especially when accessing Merge Request dashboards via URLs like:
https://<our-domain-name-for-sonar>/dashboard?id=<our-project-id>&pullRequest=310
Questions:
Resource Configuration:
- Are the current resource parameters aligned with the recommended settings for deploying SonarQube 10.8.1 on an EKS cluster?
- Given the apparent over-provisioning, is there a more optimal configuration that balances stability and performance?
Web UI Delay:
- What could be causing the response delay in the SonarQube Web UI — especially for Merge Request dashboards?
- Is this a known bug in version 10.8.1, or are there specific configurations or fixes I should apply?
Thanks