RFC: Epsilon GC JEP

[Micha Berger]

On Thu, Dec 14, 2017 at 09:42:53PM +0100, Roman Kennke wrote:
>Am 14.12.2017 um 21:18 schrieb Aleksey Shipilev:
>>On 12/14/2017 01:15 AM, mberger wrote:
>>>I think Epsilon supporting System.gc() / Runtime.getRuntime().gc() would be very useful. And if the
>>>behavior isn't wanted, well there is always -XX:+DisableExplicitGC.

>>And that will do what? System.gc() requests are ignored by Epsilon, because there is nothing to do.

>I believe he wanted to say that it'd be useful if it *did* something
>(i.e. collect garbage). I presume the idea is to never do GC, except
>when explicitely requested.

Yes, I was saying that in contrast to doing no GC, I would find it useful
to have a GC system that only collects on demand.

For example, a server that collects garbage when the number of
connected clients goes to zero. It could tolerate a small amount of
object accumulation, possibly stay up indefinitely. (Depending upon
usage patterns.) And yet it would only delay a socket connection if
there is a new client vary shortly after.

-Micha