Re:Parallel Roguelike Lev-Gen Benchmarks: Rust, Go, D, Scala...
by AlisdairO on Saturday August 24, 2013 @02:30AM
(#6267883)
This is a big issue for me too. IIRC the next version of the JVM will allow you to specify a target memory usage as well as a max, which will encourage it to GC more after memory spikes. You should be able to return some of this to the system without too much penalty (as long as the spikes aren't too frequent...).
Re:Parallel Roguelike Lev-Gen Benchmarks: Rust, Go, D, Scala...
by levosmetalo on Tuesday August 27, 2013 @05:49AM
(#6282444)
No need to wait for the "next gen" GC. Right now you can specify min percentage of free space in a heap that triggers giving back memory to the OS. Yes, you need to specify a few more GC parameters, but it's certainly doable to force JVM to behave this way.
I used this approach in the past to keep memory usage lean. I had some spikes in application that required a lot of memory, so had to keep Xmx high, but configured the app to trigger deallocation to the OS when there's more that 20% of free memory. Worked like a charm even on and old ere 1.5 Sun JVM.
Re:Parallel Roguelike Lev-Gen Benchmarks: Rust, Go, D, Scala...
by AlisdairO on Thursday August 29, 2013 @02:27AM
(#6294561)
That mostly works, but you do still run into the issue of the memory hanging around until collection - so if your JVM doesn't choose to collect (because it has a high Xmx set), it keeps a bunch of ram.
If you're building a piece of software that needs to co-exist with other memory intensive processes, the JVM's policy of taking memory and rarely giving it back can cause unnecessary swapping. Heaven forbid you need to run multiple JVMs on the same machine (like with hadoop).
Then you start having to do silly things like specifying how much memory your app is allowed to use which makes me feel like I'm on classic MacOS.