Running with the concurrent garbage collector to prevent memory bloat
Submitted by on Thursday, 12 January, 2006 - 13:11
How do you run jedit with garbage collection happening concurrently?
When jedit is starting up and loading a bunch of files from a previous session, the memory bloats up quite a bit, much of which is just waste as it is just stray objects as can be seen after the next manual collection run. I wanted to prevent that by having the garbage collector run simultaneously.
There's supposed to be a certain percentage performance hit, which is no big deal for an editor.
I tried
java -XX:+UseConcMarkSweepGC -jar "C:\Program Files\jEdit 4.2\jedit.jar"
It seems a little better, but when I click the garbage collection button, multi-megabytes of heap are still recovered, which I don't think should be the case if the collector is continuously running.
Any thoughts?
When jedit is starting up and loading a bunch of files from a previous session, the memory bloats up quite a bit, much of which is just waste as it is just stray objects as can be seen after the next manual collection run. I wanted to prevent that by having the garbage collector run simultaneously.
There's supposed to be a certain percentage performance hit, which is no big deal for an editor.
I tried
java -XX:+UseConcMarkSweepGC -jar "C:\Program Files\jEdit 4.2\jedit.jar"
It seems a little better, but when I click the garbage collection button, multi-megabytes of heap are still recovered, which I don't think should be the case if the collector is continuously running.
Any thoughts?
