Why doesn't anyone use G instead of M?

[d4rkstr1d3r]

More of a curiosity than anything else. When assigning java heap size why does everyone always right out 8192M instead of simply writing 8G? Does anyone know why it's such common practice?

 

[Nanakisan]

More of a curiosity than anything else. When assigning java heap size why does everyone always right out 8192M instead of simply writing 8G? Does anyone know why it's such common practice?

to my understanding i don't think java understands G only M.

 

[d4rkstr1d3r]

It does understand it. Oracle's own documentation shows that. I was just curious why almost no one uses it.

http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionX.html

-Xms
 
The -Xms option sets the initial and minimum Java heap size. The Java heap (the “heap”) is the part of the memory where blocks of memory are allocated to objects and freed during garbage collection.
 
Note:    -Xms does not limit the total amount of memory that the JVM can use.
Operation
 
Format: -Xms<size>[g|G|m|M|k|K]
 
Combine -Xms with a memory value and add a unit.
 
For Example:
 
java -Xms:64m myApp
 
sets the initial and minimum java heap to 64 MB.
 
If you do not add a unit, you will get the exact value you state; for example, 64 will be interpreted as 64 bytes, not 64 megabytes or 64 kilobytes.
 
For best performance, set -Xms to the same size as the maximum heap size, for example:
 
java -Xgcprio:throughput -Xmx:64m -Xms:64m myApp

 

[Nanakisan]

Perhaps its just out of lazy and refusal to change.

 

[Nessiroj]

I'm using G instead of M, just easier to explain in tickets (2G or 2048M) if you know what i mean