VM memory management on Win32 with G1

Jon Masamitsu Jon.Masamitsu at Sun.COM
Mon Apr 28 06:58:40 PDT 2008


None of the hotspot collectors (including G1) are implemented
to use a non-contiguous heap.  We're aware of the problem of
not being able to allocate a contiguous address space for
the Java heap, but are not currently working on that issue
for JDK 7.  The design of G1 may make it more amenable to
a non-contiguous heap in the future, but G1 is a new
collector and we have our hands full right now
getting it to product quality in its current configuration.

Heiko Wagner wrote:
> Hi! I am evangelizing my company to use Java. I started using Java, in
> combination with our legacy system, via the invocation api and call methods
> using JNI. The platform is 32bit Windows. One problem is that the legacy
> software allocates pretty much of the address space using a VirtualAlloc api
> call, so there is no large contiguous space left for Java. As far as I know
> the 2nd edition of the Java VM spec removes the need to have the heap in one
> contiguous segment. As far as my understanding goes the G1 collector should
> make a non contiguous heap allocation possible. I am right with my
> assumption? It it possible to enable such a memory layout in Java 7?
> 
> 
> Regards
> Heiko
> 
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
_______________________________________________
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use



More information about the hotspot-gc-dev mailing list