[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR: 8287135: Calculation of jmm_GetMemoryUsage is wrong
From:       Ioi Lam <iklam () openjdk ! java ! net>
Date:       2022-05-27 21:45:42
Message-ID: oP7AilQrqdY2_PRNwVsw4FtcrH0WlaKo4-f81V4jeyc=.a4333a66-177a-48f0-8817-5689de583b8f () github ! com
[Download RAW message or body]

On Fri, 27 May 2022 07:22:11 GMT, Thomas Stuefe <stuefe@openjdk.org> wrote:

> > If we remove `CompressedClassSpace`, we can only `getMemoryPool("Metaspace")`. \
> > Although metaspace is not baked in the specification, IMHO it's easier for \
> > developers to understand what is `metaspace` compared to the concepts of `Non \
> > Class Space` and `Compressed Class Space`.
> 
> I personally think that would be totally fine.

I also vote for removing `CompressedClassSpacePool`

-------------

PR: https://git.openjdk.java.net/jdk/pull/8831


[prev in list] [next in list] [prev in thread] [next in thread]