JEP proposed to target JDK 11: 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector
benjamin.john.evans at gmail.com
Thu Jan 18 09:51:10 UTC 2018
How about -XX:+LeakMemoryOnAllAllocations - which is fully descriptive
of what’s going on & won’t suggest to even the most unwary developer
that this is an alternative production collector?
On Thu, Jan 18, 2018 at 9:39 AM, Aleksey Shipilev <shade at redhat.com> wrote:
> On 01/18/2018 10:26 AM, Erik Österlund wrote:
>> This is not a garbage collector, because it does not collect garbage. It is an allocator.
> Well, it also does the memory reclamation "ultimate garbage collection"-style  ;)
>> Therefore, I also think the -XX:+UseNoGC name is more descriptive.
> Noted. Would you then agree that -XX:+UseNoGC is descriptive enough that users know they risk sudden
> OOMEs? The option name itself obviously comes with that caveat that user has to accept, and so we
> don't need to protect it with experimental/diagnostic flag?
>  https://groups.google.com/forum/message/raw?msg=comp.lang.ada/E9bNCvDQ12k/1tezW24ZxdAJ
More information about the jdk-dev