On Thu, Dec 3, 2009 at 9:13 AM, Johann Hibschman <joha...@gmail.com> wrote: > On Dec 2, 9:59 pm, Johann Hibschman <joha...@gmail.com> wrote: >> On Dec 2, 9:09 pm, David Brown <cloj...@davidb.org> wrote: >> >> > You can tune the max with -Xmx1G for example, to limit it to one GB. >> >> That's a good idea; then I'll know for sure if it's keeping a handle >> to the entire file. > > Ok, that's a relief. > > First of all, -Xmx1G isn't legal, at least for java 1.6; I had to > specify -Xmx1024m. Second, once I did that, the memory use of the > obvious parallel version, (reduce + (pmap ...)), remained within > reason. Clojure is good, everything is happy, fuzzy bunnies and > kittens frolic with abandon. > > So, all of this is a lot of hot air over nothing. Thanks for pointing > me in the right direction. > > Cheers, > Johann >
Another magic command line flag you could try playing with is -XX:+DoEscapeAnalysis It's hard to say whether it will help you or not because Sun has been switching its default from on and off seemingly randomly across the recent JVM updates. If it is not on by default on the JVM you're running though, I've found it to make a pretty hefty difference to a lot of clojure code, it's quite good at reducing the number of "useless" allocations clojure needs to do. --Aaron -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
