JEP proposed to target JDK 11: 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector (original) (raw)
Aleksey Shipilev shade at redhat.com
Thu Jan 18 09:39:00 UTC 2018
- Previous message: JEP proposed to target JDK 11: 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector
- Next message: JEP proposed to target JDK 11: 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 [1] ;)
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?
Thanks, -Aleksey
[1] https://groups.google.com/forum/message/raw?msg=comp.lang.ada/E9bNCvDQ12k/1tezW24ZxdAJ
- Previous message: JEP proposed to target JDK 11: 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector
- Next message: JEP proposed to target JDK 11: 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]