blocks|key|1452102|text|64位操作系统上32位JVM的限制与32位操作系统上32位JVM的限制完全相同。毕竟，32位JVM将在32位虚拟机上运行(在虚拟化意义上)，因此它不会知道它正在64位操作系统/机器上运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452103|与在32位操作系统上运行32位JVM相比，在64位操作系统上运行32位JVM的一个优点是您可以拥有更多的物理内存，因此不会经常遇到交换/分页。然而，只有当您有多个进程时，这一优势才能真正充分实现。|1452104|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The limitations of a 32-bit JVM on a 64-bit OS will be exactly the same as the limitations of a 32-bit JVM on a 32-bit OS. After all, the 32-bit JVM will be running In a 32-bit virtual machine (in the virtualization sense) so it won't know that it's running on a 64-bit OS/machine.

The one advantage to running a 32-bit JVM on a 64-bit OS versus a 32-bit OS is that you can have more physical memory, and therefore will encounter swapping/paging less frequently. This advantage is only really fully realized when you have multiple processes, however.

blocks|key|1237330|text|我尝试在32位Linux机器上将堆大小设置为2200M，JVM工作得很好。当我将JVM设置为2300M时，它没有启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1237331|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have tried setting the heap size upto 2200M on 32bit Linux machine and JVM worked fine. The JVM didnt start when I set it to 2300M.

blocks|key|1452138|text|在Solaris上，从Solaris+2.5开始，该限制大约为3.5+GB。(大约10年前)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452139|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

On Solaris the limit has been about 3.5 GB since Solaris 2.5. (about 10 years ago)

blocks|key|1452187|text|Oracle当前拥有的JROCKIT+JVM支持非连续堆使用，因此当JVM在64位windows操作系统上运行时，允许32位JVM访问超过3.8+GB的内存。(在32位操作系统上运行时为2.8+GB+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452188|http://blogs.oracle.com/jrockit/entry/how_to_get_almost_3_gb_heap_on_windows|offset|length|1452189|JVM可以在以下地址免费下载(需要注册)|1452190|http://www.oracle.com/technetwork/middleware/jrockit/downloads/index.html|1452191|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|24|0|0|0|0|21|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]|Q|$5|M|N|O|A|$P|I]]]]

The JROCKIT JVM currently owned by Oracle supports non-contiguous heap usage, thus allowing the 32 bit JVM to access more then 3.8 GB of memory when the JVM is running on a 64 bit windows OS. (2.8 GB when running on a 32 bit OS).

<a href="http://blogs.oracle.com/jrockit/entry/how_to_get_almost_3_gb_heap_on_windows" rel="nofollow">http://blogs.oracle.com/jrockit/entry/how_to_get_almost_3_gb_heap_on_windows</a>

The JVM can be freely downloaded (registration required) at

<a href="http://www.oracle.com/technetwork/middleware/jrockit/downloads/index.html" rel="nofollow">http://www.oracle.com/technetwork/middleware/jrockit/downloads/index.html</a>

blocks|key|1237442|text|这是一项繁重的调整，但您可以获得3+3gb的堆。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1237443|http://www.microsofttranslator.com/bv.aspx?from=&to=en&a=http://forall.ru-board.com/egor23/online/FAQ/Virtual_Memory/Limits_Virtual_Memory.html|offset|length|1237444|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|3Z|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

This is heavy tunning, but you can get a 3gb heap.

<a href="http://www.microsofttranslator.com/bv.aspx?from=&amp;to=en&amp;a=http://forall.ru-board.com/egor23/online/FAQ/Virtual_Memory/Limits_Virtual_Memory.html" rel="nofollow">http://www.microsofttranslator.com/bv.aspx?from=&amp;to=en&amp;a=http://forall.ru-board.com/egor23/online/FAQ/Virtual_Memory/Limits_Virtual_Memory.html</a>

blocks|key|1452297|text|以下是在Solaris和Linux+64位环境下的一些测试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452298|Solaris10-+SPARC+-+T5220机器，内存32+GB+(空闲约9+GB+)|1452299|$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3750m+MaxMemory
Error+occurred+during+initialization+of+VM
Could+not+reserve+space+for+ObjectStartArray
$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3700m+MaxMemory
Total+Memory:+518520832+(494.5+MiB)
Max+Memory:+++3451912192+(3292.0+MiB)
Free+Memory:++515815488+(491.91998291015625+MiB)
Current+PID+is:+28274
Waiting+for+user+to+press+Enter+to+finish+...

$+java+-version
java+version+"1.6.0_30"
Java(TM)+SE+Runtime+Environment+(build+1.6.0_30-b12)
Java+HotSpot(TM)+Server+VM+(build+20.5-b03,+mixed+mode)

$+which+java
/usr/bin/java
$+file+/usr/bin/java
/usr/bin/java:+ELF+32-bit+MSB+executable+SPARC+Version+1,+dynamically+linked,+not+stripped,+no+debugging+information+available

$+prstat+-p+28274
+++PID+USERNAME++SIZE+++RSS+STATE++PRI+NICE++++++TIME++CPU+PROCESS/NLWP
28274+user1+++++670M+++32M+sleep+++59++++0+++0:00:00+0.0%25+java/35|code-block|syntax|javascript|1452300|顺便说一句:显然Java在启动时并没有分配太多的实际内存。似乎每个启动的实例只需要大约100MB(我启动了10个)|1452301|Solaris10-+x86+-+VMWare虚拟机，8+GB内存(约3+GB可用*)|1452302|3+GB的空闲内存并不是真的。ZFS缓存使用了大量的RAM，但是我没有root访问权限来检查到底有多少|1452303|$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3650m+MaxMemory
Error+occurred+during+initialization+of+VM
Could+not+reserve+enough+space+for+object+heap
Could+not+create+the+Java+virtual+machine.

$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3600m+MaxMemory
Total+Memory:+516423680+(492.5+MiB)
Max+Memory:+++3355443200+(3200.0+MiB)
Free+Memory:++513718336+(489.91998291015625+MiB)
Current+PID+is:+26841
Waiting+for+user+to+press+Enter+to+finish+...

$+java+-version
java+version+"1.6.0_41"
Java(TM)+SE+Runtime+Environment+(build+1.6.0_41-b02)
Java+HotSpot(TM)+Server+VM+(build+20.14-b01,+mixed+mode)

$+which+java
/usr/bin/java

$+file+/usr/bin/java
/usr/bin/java:++ELF+32-bit+LSB+executable+80386+Version+1+[FPU],+dynamically+linked,+not+stripped,+no+debugging+information+available

$+prstat+-p+26841
+++PID+USERNAME++SIZE+++RSS+STATE++PRI+NICE++++++TIME++CPU+PROCESS/NLWP
26841+user1+++++665M+++22M+sleep+++59++++0+++0:00:00+0.0%25+java/12|1452304|具有4+GB内存的RedHat+5.5+-+x86+-+VMWare+VM+(使用了约3.8+GB内存-+200+MB的缓冲区和3.1+GB的缓存，因此约3+GB可用)|1452305|$+alias+java='$HOME/jre/jre1.6.0_34/bin/java'

$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3500m+MaxMemory
Error+occurred+during+initialization+of+VM
Could+not+reserve+enough+space+for+object+heap
Could+not+create+the+Java+virtual+machine.

$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3450m+MaxMemory
Total+Memory:+514523136+(490.6875+MiB)
Max+Memory:+++3215654912+(3066.6875+MiB)
Free+Memory:++511838768+(488.1274871826172+MiB)
Current+PID+is:+21879
Waiting+for+user+to+press+Enter+to+finish+...

$+java+-version
java+version+"1.6.0_34"
Java(TM)+SE+Runtime+Environment+(build+1.6.0_34-b04)
Java+HotSpot(TM)+Server+VM+(build+20.9-b04,+mixed+mode)

$+file+$HOME/jre/jre1.6.0_34/bin/java
/home/user1/jre/jre1.6.0_34/bin/java:+ELF+32-bit+LSB+executable,+Intel+80386,+version+1+(SYSV),+for+GNU/Linux+2.2.5,+dynamically+linked+(uses+shared+libs),+for+GNU/Linux+2.2.5,+not+stripped

$+cat+/proc/21879/status+%7C+grep+%5EVm
VmPeak:++3882796+kB
VmSize:++3882796+kB
VmLck:+++++++++0+kB
VmHWM:+++++12520+kB
VmRSS:+++++12520+kB
VmData:++3867424+kB
VmStk:++++++++88+kB
VmExe:++++++++40+kB
VmLib:+++++14804+kB
VmPTE:++++++++96+kB|1452306|同一台机器使用JRE7|1452307|$+alias+java='$HOME/jre/jre1.7.0_21/bin/java'

$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3500m+MaxMemory
Error+occurred+during+initialization+of+VM
Could+not+reserve+enough+space+for+object+heap
Error:+Could+not+create+the+Java+Virtual+Machine.
Error:+A+fatal+exception+has+occurred.+Program+will+exit.

$+java+-XX:PermSize=128M+-XX:MaxPermSize=256M+-Xms512m+-Xmx3450m+MaxMemory
Total+Memory:+514523136+(490.6875+MiB)
Max+Memory:+++3215654912+(3066.6875+MiB)
Free+Memory:++511838672+(488.1273956298828+MiB)
Current+PID+is:+23026
Waiting+for+user+to+press+Enter+to+finish+...

$+java+-version
java+version+"1.7.0_21"
Java(TM)+SE+Runtime+Environment+(build+1.7.0_21-b11)
Java+HotSpot(TM)+Server+VM+(build+23.21-b01,+mixed+mode)

$+file+$HOME/jre/jre1.7.0_21/bin/java
/home/user1/jre/jre1.7.0_21/bin/java:+ELF+32-bit+LSB+executable,+Intel+80386,+version+1+(SYSV),+for+GNU/Linux+2.6.9,+dynamically+linked+(uses+shared+libs),+for+GNU/Linux+2.6.9,+not+stripped

$+cat+/proc/23026/status+%7C+grep+%5EVm
VmPeak:++4040288+kB
VmSize:++4040288+kB
VmLck:+++++++++0+kB
VmHWM:+++++13468+kB
VmRSS:+++++13468+kB
VmData:++4024800+kB
VmStk:++++++++88+kB
VmExe:+++++++++4+kB
VmLib:+++++10044+kB
VmPTE:+++++++112+kB|1452308|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

Here is some testing under Solaris and Linux 64-bit

<h2>Solaris 10 - SPARC - T5220 machine with 32 GB RAM (and about 9 GB free)</h2>

<pre><code>$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3750m MaxMemory
Error occurred during initialization of VM
Could not reserve space for ObjectStartArray
$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3700m MaxMemory
Total Memory: 518520832 (494.5 MiB)
Max Memory: 3451912192 (3292.0 MiB)
Free Memory: 515815488 (491.91998291015625 MiB)
Current PID is: 28274
Waiting for user to press Enter to finish ...

$ java -version
java version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) Server VM (build 20.5-b03, mixed mode)

$ which java
/usr/bin/java
$ file /usr/bin/java
/usr/bin/java: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, not stripped, no debugging information available

$ prstat -p 28274
 PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
28274 user1 670M 32M sleep 59 0 0:00:00 0.0% java/35
</code></pre>

BTW: Apparently Java does not allocate much actual memory with the startup. It seemed to take only about 100 MB per instance started (I started 10)

<h2>Solaris 10 - x86 - VMWare VM with 8 GB RAM (about 3 GB free*)</h2>

The 3 GB free RAM is not really true. There is a large chunk of RAM that ZFS caches use, but I don't have root access to check how much exactly

<pre><code>$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3650m MaxMemory
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3600m MaxMemory
Total Memory: 516423680 (492.5 MiB)
Max Memory: 3355443200 (3200.0 MiB)
Free Memory: 513718336 (489.91998291015625 MiB)
Current PID is: 26841
Waiting for user to press Enter to finish ...

$ java -version
java version "1.6.0_41"
Java(TM) SE Runtime Environment (build 1.6.0_41-b02)
Java HotSpot(TM) Server VM (build 20.14-b01, mixed mode)

$ which java
/usr/bin/java

$ file /usr/bin/java
/usr/bin/java: ELF 32-bit LSB executable 80386 Version 1 [FPU], dynamically linked, not stripped, no debugging information available

$ prstat -p 26841
 PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
26841 user1 665M 22M sleep 59 0 0:00:00 0.0% java/12
</code></pre>

<h2>RedHat 5.5 - x86 - VMWare VM with 4 GB RAM (about 3.8 GB used - 200 MB in buffers and 3.1 GB in caches, so about 3 GB free)</h2>

<pre><code>$ alias java='$HOME/jre/jre1.6.0_34/bin/java'

$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3500m MaxMemory
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3450m MaxMemory
Total Memory: 514523136 (490.6875 MiB)
Max Memory: 3215654912 (3066.6875 MiB)
Free Memory: 511838768 (488.1274871826172 MiB)
Current PID is: 21879
Waiting for user to press Enter to finish ...

$ java -version
java version "1.6.0_34"
Java(TM) SE Runtime Environment (build 1.6.0_34-b04)
Java HotSpot(TM) Server VM (build 20.9-b04, mixed mode)

$ file $HOME/jre/jre1.6.0_34/bin/java
/home/user1/jre/jre1.6.0_34/bin/java: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped

$ cat /proc/21879/status | grep ^Vm
VmPeak: 3882796 kB
VmSize: 3882796 kB
VmLck: 0 kB
VmHWM: 12520 kB
VmRSS: 12520 kB
VmData: 3867424 kB
VmStk: 88 kB
VmExe: 40 kB
VmLib: 14804 kB
VmPTE: 96 kB
</code></pre>

<h2>Same machine using JRE 7</h2>

<pre><code>$ alias java='$HOME/jre/jre1.7.0_21/bin/java'

$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3500m MaxMemory
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

$ java -XX:PermSize=128M -XX:MaxPermSize=256M -Xms512m -Xmx3450m MaxMemory
Total Memory: 514523136 (490.6875 MiB)
Max Memory: 3215654912 (3066.6875 MiB)
Free Memory: 511838672 (488.1273956298828 MiB)
Current PID is: 23026
Waiting for user to press Enter to finish ...

$ java -version
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) Server VM (build 23.21-b01, mixed mode)

$ file $HOME/jre/jre1.7.0_21/bin/java
/home/user1/jre/jre1.7.0_21/bin/java: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped

$ cat /proc/23026/status | grep ^Vm
VmPeak: 4040288 kB
VmSize: 4040288 kB
VmLck: 0 kB
VmHWM: 13468 kB
VmRSS: 13468 kB
VmData: 4024800 kB
VmStk: 88 kB
VmExe: 4 kB
VmLib: 10044 kB
VmPTE: 112 kB
</code></pre>

blocks|key|1452389|text|这里还有一点关于hotspot+32位JVM:-本机堆容量=4gig-+Java+heap+-+PermGen；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1452390|对于32位JVM来说，这可能会变得特别棘手，因为Java堆和本机堆是一场竞赛。Java堆越大，本机堆就越小。尝试为32位虚拟机(例如.2.5+GB%2B+)设置大堆会增加本机OutOfMemoryError的风险，这取决于您的应用程序占用空间、线程数量等。|1452391|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

one more point here for hotspot 32-bit JVM:-
the native heap capacity = 4 Gig – Java Heap - PermGen;

It can get especially tricky for 32-bit JVM since the Java Heap and native Heap are in a race. The
bigger your Java Heap, the smaller the native Heap. Attempting to setup a large Heap for a 32-bit VM
e.g .2.5 GB+ increases risk of native OutOfMemoryError depending of your application(s) footprint,
number of Threads etc.

blocks|key|1237621|text|限制还来自这样一个事实，即对于32+bit+VM，如果您想要所有这些heap，4GB本身必须从地址零开始。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1237622|想一想，如果你想通过以下方式引用一些东西：|1237623|0000....0001|code-block|syntax|javascript|1237624|即:具有这种特定位表示的引用，这意味着您正在尝试访问堆中的第一个内存。要做到这一点，堆必须从地址零开始。但这永远不会发生，它从零的某个偏移量开始：|1237625|++++%7C+....+++++++++++++++....+{heap_start+....+heap_end}+...+%7C
+-->+(this+can't+be+referenced)+<--|1237626|因为堆从不从OS中的地址0开始，所以有相当多的位从未从32位引用中使用，因此可以引用的堆更低。|1237627|entityMap^0|F|6|Y|4|13|3|0|0|0|0|0|6|2|R|2|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|T|$]]

The limitation also comes from the fact that for a <code>32 bit</code> VM, the <code>heap</code> itself has to start at address zero if you want all those <code>4GB</code>. 

Think about it, if you want to reference something via:

<pre><code>0000....0001
</code></pre>

i.e.: a reference that has this particular bits representation, it means you are trying to access the very first memory from the heap. For that to be possible, the heap has to start at address zero. But that never happens, it starts at some offset from zero:

<pre><code> | .... .... {heap_start .... heap_end} ... |
 --&gt; (this can't be referenced) &lt;--
</code></pre>

Because heap never starts from address zero in an <code>OS</code>, there are quite a few bits that are never used from a <code>32</code> bits reference, and as such the heap that can be referenced is lower.

The question is not about the maximum heap size on a 32-bit OS, given that 32-bit OSes have a maximum addressable memory size of 4GB, and that the JVM's max heap size depends on how much contiguous free memory can be reserved.

I'm more interested in knowing the maximum (both theoretical and practically achievable) heap size for a 32-bit JVM running in a 64-bit OS. Basically, I'm looking at answers similar to <a href="https://stackoverflow.com/questions/987219/max-amount-of-memory-per-java-process-in-windows/987576#987576">the figures in a related question on SO</a>.

As to why a 32-bit JVM is used instead of a 64-bit one, the reason is not technical but rather administrative/bureaucratic - it is probably too late to install a 64-bit JVM in the production environment.

Maximum Java heap size of a 32-bit JVM on a 64-bit OS

问题不在于32位操作系统上的最大堆大小，因为32位OSes的最大可寻址内存大小为4 4GB，并且JVM的最大堆大小取决于可以保留多少连续的空闲内存。我更感兴趣的是知道在64位操作系统中运行的32位JVM的最大堆大小(理论上和实际上都可以实现)。基本上，我正在寻找类似于的答案。至于为什么使用32位JVM而不是64位JVM...

问64位操作系统上32位JVM的最大Java堆大小
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问64位操作系统上32位JVM的最大Java堆大小EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问64位操作系统上32位JVM的最大Java堆大小
EN