Think I may have found the problem. When the second scan is running, until it is done, the system retains and uses the original data structure. What is happening is that holding both in memory is causing the GC to go nuts - not enough memory. Apparently, node doesn't just keep allocating more real memory as needed. There is some max set.
What is the best way to determine what my memory footprint is and how can I control it? Thanks. Blake On Thursday, June 4, 2015 at 12:25:08 PM UTC-5, Blake McBride wrote: > > I tried iojs. Same problem. > > > On Thursday, June 4, 2015 at 10:00:14 AM UTC-5, nwhite wrote: >> >> Blake, >> >> You mentioned large amount of directory recursion. I hit a similar wall >> at roughly 2000 files where the process would start to slow down >> drastically. My process was very similar to what you described. >> >> After wasting considerable time I noticed that native 'fs' module was >> complete rewritten in iojs. After switching from node to iojs the problem >> went away completely. >> > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/ff26e72a-8a52-47f0-8c0a-997b36f38e9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
