How does JVM calculate the committed heap memory?
up vote
5
down vote
favorite
Based on the documentation : https://docs.oracle.com/javase/7/docs/api/java/lang/management/MemoryUsage.html
committed - represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.
but the question is how JVM calculate the committed memory?
java heap-memory
add a comment |
up vote
5
down vote
favorite
Based on the documentation : https://docs.oracle.com/javase/7/docs/api/java/lang/management/MemoryUsage.html
committed - represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.
but the question is how JVM calculate the committed memory?
java heap-memory
Closely related to stackoverflow.com/questions/41468670/…
– Raedwald
Nov 14 at 9:40
The strategy heavily relies on the JVM and the GC versions. Different versions give different strategies.
– Sofo Gial
Nov 14 at 9:41
Do you want to know how the JVM calculates the amount of memory that it requests from the OS or the amount that is currently comitted?
– dpr
Nov 14 at 9:42
@dpr, i am aware that amount of committed memory may change over time (increase or decrease). I want to know the basis of increase/decrease of committed memory.
– Andrew
Nov 14 at 10:27
@Andrew You can find some relevant info here: docs.oracle.com/javase/9/gctuning/…
– Sofo Gial
Nov 14 at 11:54
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
Based on the documentation : https://docs.oracle.com/javase/7/docs/api/java/lang/management/MemoryUsage.html
committed - represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.
but the question is how JVM calculate the committed memory?
java heap-memory
Based on the documentation : https://docs.oracle.com/javase/7/docs/api/java/lang/management/MemoryUsage.html
committed - represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used.
but the question is how JVM calculate the committed memory?
java heap-memory
java heap-memory
edited Nov 14 at 9:12
Sofo Gial
15813
15813
asked Nov 14 at 9:08
Andrew
55041025
55041025
Closely related to stackoverflow.com/questions/41468670/…
– Raedwald
Nov 14 at 9:40
The strategy heavily relies on the JVM and the GC versions. Different versions give different strategies.
– Sofo Gial
Nov 14 at 9:41
Do you want to know how the JVM calculates the amount of memory that it requests from the OS or the amount that is currently comitted?
– dpr
Nov 14 at 9:42
@dpr, i am aware that amount of committed memory may change over time (increase or decrease). I want to know the basis of increase/decrease of committed memory.
– Andrew
Nov 14 at 10:27
@Andrew You can find some relevant info here: docs.oracle.com/javase/9/gctuning/…
– Sofo Gial
Nov 14 at 11:54
add a comment |
Closely related to stackoverflow.com/questions/41468670/…
– Raedwald
Nov 14 at 9:40
The strategy heavily relies on the JVM and the GC versions. Different versions give different strategies.
– Sofo Gial
Nov 14 at 9:41
Do you want to know how the JVM calculates the amount of memory that it requests from the OS or the amount that is currently comitted?
– dpr
Nov 14 at 9:42
@dpr, i am aware that amount of committed memory may change over time (increase or decrease). I want to know the basis of increase/decrease of committed memory.
– Andrew
Nov 14 at 10:27
@Andrew You can find some relevant info here: docs.oracle.com/javase/9/gctuning/…
– Sofo Gial
Nov 14 at 11:54
Closely related to stackoverflow.com/questions/41468670/…
– Raedwald
Nov 14 at 9:40
Closely related to stackoverflow.com/questions/41468670/…
– Raedwald
Nov 14 at 9:40
The strategy heavily relies on the JVM and the GC versions. Different versions give different strategies.
– Sofo Gial
Nov 14 at 9:41
The strategy heavily relies on the JVM and the GC versions. Different versions give different strategies.
– Sofo Gial
Nov 14 at 9:41
Do you want to know how the JVM calculates the amount of memory that it requests from the OS or the amount that is currently comitted?
– dpr
Nov 14 at 9:42
Do you want to know how the JVM calculates the amount of memory that it requests from the OS or the amount that is currently comitted?
– dpr
Nov 14 at 9:42
@dpr, i am aware that amount of committed memory may change over time (increase or decrease). I want to know the basis of increase/decrease of committed memory.
– Andrew
Nov 14 at 10:27
@dpr, i am aware that amount of committed memory may change over time (increase or decrease). I want to know the basis of increase/decrease of committed memory.
– Andrew
Nov 14 at 10:27
@Andrew You can find some relevant info here: docs.oracle.com/javase/9/gctuning/…
– Sofo Gial
Nov 14 at 11:54
@Andrew You can find some relevant info here: docs.oracle.com/javase/9/gctuning/…
– Sofo Gial
Nov 14 at 11:54
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Here you can find a little bit more detail, but it does not explain the exact way how committed heap space is increased:
There is also a committed heap size which acts as a "high water
mark", moving up once the JVM cannot free up space even on old
collection / young collection to make room. In this case, the
committed heap size is increased. This cycle repeats until the
committed heap size matches the maximum heap size, the maximum space
allocatable.
https://support.mulesoft.com/s/article/Java-JVM-memory-allocation-pattern-explained
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Here you can find a little bit more detail, but it does not explain the exact way how committed heap space is increased:
There is also a committed heap size which acts as a "high water
mark", moving up once the JVM cannot free up space even on old
collection / young collection to make room. In this case, the
committed heap size is increased. This cycle repeats until the
committed heap size matches the maximum heap size, the maximum space
allocatable.
https://support.mulesoft.com/s/article/Java-JVM-memory-allocation-pattern-explained
add a comment |
up vote
1
down vote
Here you can find a little bit more detail, but it does not explain the exact way how committed heap space is increased:
There is also a committed heap size which acts as a "high water
mark", moving up once the JVM cannot free up space even on old
collection / young collection to make room. In this case, the
committed heap size is increased. This cycle repeats until the
committed heap size matches the maximum heap size, the maximum space
allocatable.
https://support.mulesoft.com/s/article/Java-JVM-memory-allocation-pattern-explained
add a comment |
up vote
1
down vote
up vote
1
down vote
Here you can find a little bit more detail, but it does not explain the exact way how committed heap space is increased:
There is also a committed heap size which acts as a "high water
mark", moving up once the JVM cannot free up space even on old
collection / young collection to make room. In this case, the
committed heap size is increased. This cycle repeats until the
committed heap size matches the maximum heap size, the maximum space
allocatable.
https://support.mulesoft.com/s/article/Java-JVM-memory-allocation-pattern-explained
Here you can find a little bit more detail, but it does not explain the exact way how committed heap space is increased:
There is also a committed heap size which acts as a "high water
mark", moving up once the JVM cannot free up space even on old
collection / young collection to make room. In this case, the
committed heap size is increased. This cycle repeats until the
committed heap size matches the maximum heap size, the maximum space
allocatable.
https://support.mulesoft.com/s/article/Java-JVM-memory-allocation-pattern-explained
answered Nov 14 at 12:38
josmaf
666
666
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53296481%2fhow-does-jvm-calculate-the-committed-heap-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Closely related to stackoverflow.com/questions/41468670/…
– Raedwald
Nov 14 at 9:40
The strategy heavily relies on the JVM and the GC versions. Different versions give different strategies.
– Sofo Gial
Nov 14 at 9:41
Do you want to know how the JVM calculates the amount of memory that it requests from the OS or the amount that is currently comitted?
– dpr
Nov 14 at 9:42
@dpr, i am aware that amount of committed memory may change over time (increase or decrease). I want to know the basis of increase/decrease of committed memory.
– Andrew
Nov 14 at 10:27
@Andrew You can find some relevant info here: docs.oracle.com/javase/9/gctuning/…
– Sofo Gial
Nov 14 at 11:54