3 ms·
The Java guys have spend a fair amount of time tuning and improving garbage collectors. Given that you run clojure, have you considered trying to use a concurr
by tomjen3 16y ago
The Java guys have spend a fair amount of time tuning and improving garbage collectors.
Given that you run clojure, have you considered trying to use a concurrent garbage collector?
- hga 16y agoWhile reading about their related packaged product I saw Azul claim that they have the only concurrent GC JVM. It's a hard problem and especially so on stock hardware where doing the sorts of things they do is necessary, e.g. read barriers implemented with virtual memory hardware and a fast interface to that. I've considered playing with this sort of thing (especially a Clojure tuned GC, for I suspect idiomatic Clojure behaves differently than standard imperative Java), but it's a lot of work (needs either a native Clojure implementation, which ought to wait on Clojure-in-Clojure, or working on an existing VM and the fast ones like Hotspot are messy).
- jwr 16y agoWe are using the Concurrent Mark-Sweep collector now, but this doesn't solve the problem completely. You still get pauses when Full GC occurs.