Hi, in my <https://bea.gazelle.rocks/> application <https://bea.gazelle.rocks> I have about 800 MB of live objects. I know this because that's the used heap I get after running System.gc().
However, in normal operation (without calling System.gc()), heap use hovers around 3 GB out of 6 GB. I'm using G1. So my question is - since the garbage collector is supposed to "race" the application threads anyway - can't it be made to "race to the end"? Meaning, until no or almost no dead objects remain? I am totally fine with this potentially lowering the overall application or GC throughput; it's supposed to happen in irelatively (though not completely!) idle phases. I really can't afford the seconds-long stop-the world pause of System.gc(). I just wish to put the regular backgruond GC on steroids for a few seconds until its job is done. Reasons? A. It just feels cleaner to have no more dead objects. (Gotta love the clean feeling!) B. We find out how much heap we are actually using - no chance of that in normal operation. Possible? Many greetings -- Stefan Reich BotCompany.de // Java-based operating systems
_______________________________________________ hotspot-gc-use mailing list hotspot-gc-use@openjdk.java.net https://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
