ruthst00 commented on code in PR #16545:
URL: https://github.com/apache/grails-core/pull/16545#discussion_r4199210538


##########
grails-doc/src/en/guide/deployment/deploymentTasks.adoc:
##########
@@ -70,6 +70,58 @@ Heap is only part of total memory: allow space for 
metaspace, code cache, direct
 A container can be killed for exceeding its limit even if the Java heap has 
not run out of memory.
 Measure resident memory and GC behavior under load rather than copying a fixed 
heap percentage between applications.
 
+[[java25-memory]]
+=== Java 25 Memory Considerations

Review Comment:
   Updated in 
https://github.com/apache/grails-core/pull/16545/changes/e93080d9cd90826ff655f6ccaca02c19ca597e32



##########
grails-doc/src/en/guide/deployment/deploymentTasks.adoc:
##########
@@ -70,6 +70,58 @@ Heap is only part of total memory: allow space for 
metaspace, code cache, direct
 A container can be killed for exceeding its limit even if the Java heap has 
not run out of memory.
 Measure resident memory and GC behavior under load rather than copying a fixed 
heap percentage between applications.
 
+[[java25-memory]]
+=== Java 25 Memory Considerations
+
+Java 25 uses more off-heap memory than earlier LTS releases.
+The most significant change is that the metaspace — the native memory region 
that holds class metadata — is now **unbounded by default**.
+On earlier JDKs the initial metaspace high-water mark was approximately 12 MB; 
on Java 25 there is no upper limit unless you set one explicitly.
+A Grails application that loads many classes (plugins, Hibernate mappings, 
GSP-compiled views) can therefore consume substantially more native memory than 
the same application on Java 21.

Review Comment:
   Updated in 
https://github.com/apache/grails-core/pull/16545/changes/e93080d9cd90826ff655f6ccaca02c19ca597e32



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to