You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/private-cloud/private-cloud-deploy/jvm-memory-tuning.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,9 @@ For a comprehensive guide explaining how the HotSpot VM performs garbage collect
23
23
In most cases, Mendix on Kubernetes doesn't need advanced memory tuning.
24
24
Starting with Operator version 2.26, the default memory settings have been aligned with Mendix Cloud and are based on typical Mendix app usage patterns.
25
25
26
+
{{% alert color="warning" %}}
26
27
Manual adjusting JVM memory usage is only needed in some cases - when the default memory settings leave unused memory.
0 commit comments