Memory is stable. Also, I am running on a 16 GB machine with 10 GB free.
On Thursday, June 4, 2015 at 8:42:55 AM UTC-5, zladuric wrote: > > Well, for one, IIRC setImmediate will not put this step on the next loop - > it will just append the function to the end of the current loop - thus > never giving Node.js a chance to go off. > > Another thing - did you try to use a debugger or something? Even a simple > strace/dtrace would tell you what the node process is doing. Also, did the > first program exit? Maybe it didn't and you're leaking more and more > memory, thus swapping more and more? > > On Thursday, June 4, 2015 at 5:06:38 AM UTC+2, Blake McBride wrote: >> >> Greetings, >> >> I have a large, very recursive process that (at best) takes 6 minutes to >> run. This process does a lot of IO, and a lot of directory recursion. In >> order to play nicely in a single threading event oriented system, I: >> >> 1. use non-blocking function whenever available >> >> 2. rather than perform recursion directly, I call the next step with >> nextTick or setImmediate and exit >> >> This has worked well in my smaller databases, and the first time through >> the large one (6 minutes). But when trying to run the large one a second >> time, it gets slower and slower until it kind of never ends. I don't know >> what is causing the slowdown. >> >> One thing I thought of is that perhaps I am filling the event queue in >> such a way so that the IO never gets a chance and it has to go through >> many, many events before any real IO can occur. Don't know. >> >> Sure appreciate any ideas. >> >> Thanks. >> >> Blake McBride >> >> -- 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/7bda3d4d-9a28-4b63-8530-ae315abb90f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
