You have 2 distinct problems: - allocating many short-lived objects. It can affect performance but does not matter for long-term memory occupation - keeping too many things in memory. Then you have to resolve an algorithmic question, quite independent of the technology you use.
On Wed, Oct 3, 2012 at 8:17 PM, Thomas <th.vanderv...@gmail.com> wrote: > try and use a 32bit JVM. I found that a 64bit JVM uses almost twice as much > memory. YMMV > There is a flag for that: -XX:+UseCompressedOops It is enabled by default in Java 6u23 and more recent (including Java 7), when your max heap is less than 32Go. http://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html It uses a 32 bits representation for pointer in a 64 bits VM. -- 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
