On Jan 20, 8:36 am, Perry Trolard <trol...@gmail.com> wrote: > Yesterday I had a strange case of pmap (parallel map) eating up all of > the heap space I'd make available -- from 256M up to a Gig. I track > SVN, & I know for sure this wasn't happening last Wednesday (the > 14th). Calling map in place of pmap caused the code to run fine inside > of a 256M heap. > > I don't see anything in the SVN logs that looks like the culprit, but > the behavior is easy enough to reproduce: > > user=> (def result (map inc (range 1000000))) > #'user/result > user=> (count result) > 1000000 > user=> (def result-p (pmap inc (range 1000000))) > java.lang.OutOfMemoryError: Java heap space (NO_SOURCE_FILE:8) > > Stack trace below. Best to open an issue?
Doesn't pmap have to construct the whole sequence explicitly in order to map its execution across more than one processor? or does it take in a lazy fashion? mfh --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
