Question about MemoryService class.
Y Srinivas Ramakrishna
Y.S.Ramakrishna at Sun.COM
Sat Feb 7 13:17:07 PST 2009
of course, G1 and the possibilities/flexibility it allows
probably makes something like this somewhat moot (at least as
far as my intuition goes here).
-- ramki
----- Original Message -----
From: Y Srinivas Ramakrishna <Y.S.Ramakrishna at Sun.COM>
Date: Saturday, February 7, 2009 1:09 pm
Subject: Re: Question about MemoryService class.
To: "Colin(Du Li)" <dawn2004 at gmail.com>
Cc: hotspot-dev at openjdk.java.net
> Hi Colin --
>
> If you have a use case where 3 or more generations will
> provide distinct advantages, please feel free to
> propose an OpenJDK project for this and we'll be
> happy to help you navigate around in the relevant parts of
> the source code so you can get this done. The basic
> functionality will likely be quite straightforward,
> if tedious in some of the details, and in limiting
> the performance impact upon the basic 2 generation system.
>
> -- ramki
>
> ----- Original Message -----
> From: "Colin(Du Li)" <dawn2004 at gmail.com>
> Date: Saturday, February 7, 2009 11:08 am
> Subject: Re: Question about MemoryService class.
> To: hotspot-dev at openjdk.java.net
>
>
> > Thanks a lot!
> > I have fixed it.
> > To constrain the two-generation collector makes the system less extensible.
> > I wonder this part will be improve the the future.
> >
> >
> > mandy.chung wrote:
> > >
> > > Colin(Du Li) wrote:
> > >
> > >>Hi, guys.
> > >>
> > >>Could you give me some information about MemoryService in hotspot.
> It
> > seems
> > >>like a tool to monitor the memory usage, right? But it only
> support
> > 2
> > >>generations. I wanna divide the heap into three generations, so it
> gives
> > me
> > >>error information. Can I turn it off? Will it cause problems if I
>
> > turn it
> > >>off. How can I turn it off without side effect?
> > >>
> > >>
> > > The memoryService and memory pool implementation is the VM support
>
> > for
> > > the java.lang.management API.
> > >
> > > You need to change the current implementation to support 3
> > generations.
> > > The memory pool/service implementation is not limited to 2 generations.
> > >
> > > Mandy
> > >
> > >>Thanks a lot!
> > >>
> > >>Colin(Du Li)
> > >>
> > >>
> > >
> > >
> > >
> >
> > --
> > View this message in context: http://www.nabble.com/Question-about-MemoryService-class.-tp21880830p21891770.html
> > Sent from the OpenJDK Hotspot Virtual Machine mailing list archive
> at
> > Nabble.com.
> >
More information about the hotspot-dev
mailing list