Shlomi Schwartz Shlomi Schwartz - 11 days ago 4
Javascript Question

NodeJS - setTimeout(fn,0) vs setImmediate(fn)

What is the difference between those two, and when will I use one over the other?


setTimeout is simply like calling the function after delay has finished. Whenever a function is called it is not executed immediately, but queued so that it is executed after all the executing and currently queued eventhandlers finish first. setTimeout(,0) essentially means execute after all current functions in the present queue get executed. No guarantees can be made about how long it could take.

setImmediate is similar in this regard except that it doesn't use queue of functions. It checks queue of I/O eventhandlers. If all I/O events in the current snapshot are processed, it executes the callback. It queues them immedieately after the last I/O handler somewhat like process.nextTick. So it is faster.

Also (setTimeout,0) will be slow because it will check the timer at least once before executing. At times it can be twice as slow. Here is a benchmark.

var Suite = require('benchmark').Suite
var fs = require('fs')

var suite = new Suite

suite.add('deffered.resolve()', function(deferred) {
}, {defer: true})

suite.add('setImmediate()', function(deferred) {
  setImmediate(function() {
}, {defer: true})

suite.add('setTimeout(,0)', function(deferred) {
  setTimeout(function() {
}, {defer: true})

.on('cycle', function(event) {
.on('complete', function() {
  console.log('Fastest is ' + this.filter('fastest').pluck('name'));
.run({async: true})


deffered.resolve() x 993 ops/sec ±0.67% (22 runs sampled)
setImmediate() x 914 ops/sec ±2.48% (57 runs sampled)
setTimeout(,0) x 445 ops/sec ±2.79% (82 runs sampled)

First one gives idea of fastest possible calls. You can check yourself if setTimeout gets called half as many times as other. Also remember setImmediate will adjust to your filesystem calls. So under load it will perform less. I don't think setTimeout can do better.

setTimeout is un-intrusive way of calling functions after some time. Its just like its in the browser. It may not be suited for server-side (think why I used benchmark.js not setTimeout).