Just want to clarify something. process.nextTick has practically zero cost, even at the micro level. You'll only see the overhead if you're calling it 100k times/sec. Even then it's in the milliseconds. I've been doing optimizations and performance analysis on this for months. Trust me that running your callbacks in nextTick won't slow down your app.
Though if it is, you're doing it wrong. This is not a philosophical opinion. It's empirical fact. Read the section about understanding callback mechanics in this blog post: http://blog.trevnorris.com/2013/08/callbacks-what-i-said-was.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 --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
