SetImmediate SetTimeout and Process.nextTick | Backend Interview Series

[@Pepcoding]

🚨 Backend Development: kzbin.info/aero/PL-Jc9J83PIiEnK1q9tuVrrORqKBexcE_J

[@parthvaishnani2205]

Preferrance order for execution- Nexttick > SetImmediate > Settimeout

[@yashbansal2526]

Whatever you. have taught about priority is wrong, please correct it, anyone watching this please don't get confuse and do a simple google search

[@shubhamsoni6013]

Checked the same on Apple Mac, 1.4 GHz Quad-Core Intel Core i5, 16 GB 2133 MHz LPDDR3, Intel Iris Plus Graphics 645 1536 MB index.ts setTimeout(function(){ console.log("Settimeout") }) setImmediate(function(){ console.log("Setimmediate") }) command: npx ts-node index.ts result: Setimmediate Settimeout & sometime reverse. So as per my opinion, you would be never knowing which callback function will be called first until you know in which phase your event loop is. Thread is open for comments. Floor is yours!!

[@dharmeast]

But we add some time say 1000 in setTimeOut , then setImmediate will be called first.

[@sachinyadav-of4wh]

what we are not using SetTimeout and setImmediate in the I/O phase it is not necessary that settimeout will call first. It all depends on system's current operations. anything setimmediate/SetTimeout can be called first.

[@sarojjangid8466]

Nice sir ♥️

[@rishu605]

Whatever you have explained related to setImmediate and setTimeout priorities is completely wrong. setImmediate has a higher priority than setTimeout when it is running in an I/O cycle. Since you are running this code outside of an I/O cycle, the order of executon is NOT guaranteed and the system can execute any callback first.

[@abbasraza7086]

absolutely