c# allocating memory to the virtual machine -


Is Java's XMX equal to 1024m switch, which allows you to increase memory allocation in the virtual machine?

No CLR handles memory allocation in Java in this regard very differently in this regard. It will continue to increase the heap size with the upper limit (in addition to the architectural limitations).

On the 64-bit operating system, while targeting the X64, CLR will continue to allocate memory to a process, the total memory available in the system

on a 32-bit system, or When targeting X86, the practical upper limit is between 1.2 and 1.6 GB. At this point, you will start running out of memory exceptions. (Theoretically, it should use 2GB, but CLR itself takes some space, and the way it addresses the memory, due to this, memory causes this system to be out of errors.)


EDIT: Here is a good article description. I believe the main reason is that JVM requires the use of -Xmx because it does not release memory on the operating system, so a way to limit memory consumption of a program Offers.


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -