This feels like a memory leak problem. Try adding -XX:-HeapDumpOnOutOfMemoryError. You might try lowering the max heap to try and force an OOM earlier. Heap dumps can be analyzed using a variety of tools. My favorite is eclipse.org/mat
On Saturday, October 13, 2012 8:16:54 AM UTC-7, Jim foo.bar wrote: > > On 13/10/12 12:55, Jim - FooBar(); wrote: > > On 13/10/12 12:50, Tassilo Horn wrote: > >> pmap might not be as perfect for you use-case as you think. Because it > >> is lazy and chunked, it won't keep you cores busy. Some time ago, > there > >> was a detailed thread about this on this list. > > > > But it does keep my cores fully busy (99-100%) for the first 40 min > > roughly...IT is only after that that things go downhill... garbage > > collection issues sound more plausible to me...I'm about to try the > > new G1 collector and also since I'm doing string processing I'll try > > "-XX:+OptimizeStringConcat" and potentially > > "-XX:+UseCompressedStrings" (as long as the speed penalty is not that > > big)... > > > > > > Jim > > I switched from pmap to > > (r/fold n (r/monoid into vector) conj coll)) > > and the same thing happened again! > after approximately 50 minutes cpu utilisation dropped from 4/4 to > 1/4...I don't understand! > > Jim > -- 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
