Solution : https://service.sap.com/sap/support/notes/1005457 (SAP Service marketplace login required)
Summary :
To optimize JVM memory settings according to application needs, it is essential to understand the Java Heap's division into Young and Old Generations. Improper settings can lead to performance issues, particularly if Java Heap or generation sizes are misconfigured. The Young Generation is where new objects are allocated, and its size should be meticulously adjusted to manage frequent, minor garbage collections efficiently without premature promotions to the Old Generation, where full garbage collections occur less frequently but are more resource-intensive. For detailed analysis and parameter tuning, transaction STAD in the VM Container offers vital statistics on garbage collection (GC) operations, helping in the evaluation of JVM behavior and adjustment of memory allocations to optimize performance.
Key words :
profile parameter vmcj/option/maxjavaheap, profile parameter vmcj/option/percentageyounggen, profile parameter vmcj/option/percentageminoldgen, profile parameter vmcj/option/freefactor, vmcj/option/maxjavaheap = 200m, garbage collection takes place, single statistical records - details, small garbage collector works, shared garbage collector cycle, vmcj/option/percentageyounggen = 30
Related Notes :
| 1269480 | Collective Note about Performance of the IPC Configurator |
| 1170313 | Zero administration memory management in VMC |
| 1083358 | VMC: Empfehlungen für Parameter-Einstellungen |
| 990115 | Configuring the shared pool |