On Fri, Apr 6, 2012 at 10:25 PM, Tim Price <[email protected]> wrote: > You need to think about how the loop blocks the stack. All code "block" , > its just how you block that counts. All the threads in the world wont help > you if you don't know how to break the stack. What nextTick does is break > the stack, so it adds the function to the next run around nodes event loop. > It allows other code to run in between as the loop cycles. Why i say > mongoose/mongo is you may have a large array that you need to loop over. > 1000+ items is not something you want to do all at once. break the loop up > with nextTick. > > Does this help?
Yes, tremendously thanks! I thought it might be something like that. I think I can either break it down as by iteration of the loop or step by step interpretation of each user instruction. I'll need to create something ridiculous and use that as the test. I'll set it up on one of the small machines to see the limitations of the design. Once I get something I'll share but don't expect anything too soon. Life has a way of getting in the way :-/ . -- Neil Cherry Linux Home Automation ( http://www.linuxha.com/ ) Author: Linux Smart Homes For Dummies ( http://linuxha.com/FD/book/index.html ) -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
