Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using Node.js to loop through what could eventually be a pretty big array of posts.
If I were doing something similar using client side JavaScript, I would use timers as explained here so as not to block the thread.
My Question is: “Is still a sound practice server side?” or “Should I approach the problem differently?”
The proper way to do that in node.js is to break up your work into chunks and use
process.nextTickto queue the next chunk once the current one has completed. That way you allow other queued callbacks to be executed between each chunk of work.UPDATE: as of Node.js 0.10,
setImmediateshould typically be used instead ofprocess.nextTickfor this purpose assetImmediateyields to the event loop to make sure I/O is not being starved, butprocess.nextTickdoesn’t.