Recursive setTimeout vs setInterval in Node.js - Quick Revision & Key Differences

Recall & Review

beginner

What is setInterval used for in Node.js?

setInterval runs a function repeatedly at fixed time intervals until stopped.

intermediate

How does recursive setTimeout differ from setInterval?

Recursive setTimeout schedules the next call only after the current one finishes, allowing flexible timing and avoiding overlap.

intermediate

Why might recursive setTimeout be better for tasks with variable execution time?

Because it waits for the current task to finish before scheduling the next, preventing tasks from piling up if one takes longer.

beginner

What is a risk of using setInterval for long-running tasks?

Tasks can overlap if one takes longer than the interval, causing unexpected behavior or performance issues.

beginner

How do you stop a setInterval or recursive setTimeout in Node.js?

Use clearInterval(intervalId) for setInterval and clearTimeout(timeoutId) for setTimeout.

What happens if a task inside setInterval takes longer than the interval time?

A The interval stops automatically

B The next task waits until the current finishes

C The interval automatically adjusts to task time

D Tasks can overlap and run simultaneously

setInterval does not wait for the task to finish, so tasks can overlap if one takes too long.

Which method allows scheduling the next call only after the current one finishes?

A setInterval

B setTimeout

C Recursive setTimeout

D clearInterval

Recursive setTimeout schedules the next call inside the callback, after the current task completes.

How do you stop a repeating timer started with setInterval?

A clearInterval(timerId)

B stopTimeout(timerId)

C stopInterval(timerId)

D clearTimeout(timerId)

Use clearInterval with the interval ID to stop a setInterval.

Why might recursive setTimeout be preferred for network requests?

A It prevents overlapping requests if one is slow

B It runs faster than setInterval

C It uses less memory

D It automatically retries on failure

Recursive setTimeout waits for each request to finish before scheduling the next, avoiding overlaps.

Which timer method schedules a function to run once after a delay?

A setInterval

B setTimeout

C recursive setTimeout

D clearTimeout

setTimeout runs a function once after a specified delay.

Explain the difference between setInterval and recursive setTimeout in Node.js.

Think about how timing and task duration affect scheduling.

Describe a scenario where recursive setTimeout is better than setInterval.

Consider tasks that might take longer than expected.

Practice

1. What is the main difference between setInterval and recursive setTimeout in Node.js?

easy

A. setInterval can only run synchronous code, recursive setTimeout can run asynchronous code.

B. setInterval runs tasks at fixed intervals regardless of task duration, recursive setTimeout waits for the task to finish before scheduling the next.

C. setInterval runs only once, recursive setTimeout runs repeatedly.

D. setInterval automatically adjusts intervals based on task duration, recursive setTimeout does not.

Solution

1. Step 1: Understand setInterval behavior

   setInterval schedules a function to run repeatedly at fixed time intervals without waiting for the previous run to finish.

2. Step 2: Understand recursive setTimeout behavior

   Recursive setTimeout schedules the next run only after the current function completes, avoiding overlap.

3. Final Answer:

   setInterval runs tasks at fixed intervals regardless of task duration, recursive setTimeout waits for the task to finish before scheduling the next. -> Option B

4. Quick Check:

   Task overlap control [OK]

Hint: Remember: recursive waits, interval runs fixed times [OK]

Common Mistakes:

• Thinking setInterval waits for task completion
• Confusing recursive setTimeout with single timeout
• Assuming setInterval adjusts timing automatically

2. Which of the following is the correct syntax to implement a recursive setTimeout that logs "Hello" every 2 seconds?

easy

A. setTimeout(() => { console.log('Hello'); }, 2000); setTimeout(() => { console.log('Hello'); }, 2000);

B. setInterval(() => { console.log('Hello'); }, 2000);

C. function repeat() { setTimeout(() => { console.log('Hello'); repeat(); }, 2000); } repeat();

D. function repeat() { setInterval(() => { console.log('Hello'); repeat(); }, 2000); } repeat();

Solution

1. Step 1: Identify recursive setTimeout pattern

   The function calls setTimeout inside itself after logging, ensuring repeated delayed calls.

2. Step 2: Check syntax correctness

   function repeat() { setTimeout(() => { console.log('Hello'); repeat(); }, 2000); } repeat(); defines a function that calls itself inside setTimeout, then starts it by calling repeat().

3. Final Answer:

   function repeat() { setTimeout(() => { console.log('Hello'); repeat(); }, 2000); } repeat(); -> Option C

4. Quick Check:

   Recursive call inside setTimeout [OK]

Hint: Recursive setTimeout calls itself inside timeout [OK]

Common Mistakes:

• Using setInterval instead of recursive setTimeout
• Not calling the recursive function initially
• Calling setTimeout multiple times without recursion

3. Consider this code snippet:

let count = 0;
function tick() {
  console.log(count);
  count++;
  if (count < 3) {
    setTimeout(tick, 1000);
  }
}
tick();

What will be the output and timing behavior?

medium

A. Logs 0 once, then stops without further logs.

B. Logs 0, 1, 2 immediately without delay, then stops.

C. Logs 0, 1, 2 every 1 second simultaneously, overlapping.

D. Logs 0, 1, 2 each after 1 second delay sequentially, then stops.

Solution

1. Step 1: Analyze recursive setTimeout calls

   Function tick logs count, increments it, and schedules next call after 1 second if count < 3.

2. Step 2: Trace output and timing

   Logs 0 immediately, then after 1s logs 1, after another 1s logs 2, then stops because count reaches 3.

3. Final Answer:

   Logs 0, 1, 2 each after 1 second delay sequentially, then stops. -> Option D

4. Quick Check:

   Recursive timeout delays [OK]

Hint: Recursive timeout delays each call by 1 second [OK]

Common Mistakes:

• Assuming logs happen immediately without delay
• Thinking logs overlap simultaneously
• Confusing setTimeout with setInterval behavior

4. Identify the problem in this code using recursive setTimeout:

function repeat() {
  setTimeout(() => {
    console.log('Tick');
  }, 1000);
  repeat();
}
repeat();

medium

A. The function calls itself immediately causing a stack overflow.

B. The timeout delay is too short to see output.

C. The console.log is outside the timeout callback.

D. The function never calls itself, so it runs only once.

Solution

1. Step 1: Examine recursion timing

   The function repeat calls itself immediately after scheduling setTimeout, without waiting for the timeout to finish.

2. Step 2: Identify consequence

   This causes infinite immediate recursion, leading to stack overflow before any timeout callback runs.

3. Final Answer:

   The function calls itself immediately causing a stack overflow. -> Option A

4. Quick Check:

   Immediate recursion without delay [OK]

Hint: Call recursive function inside timeout callback only [OK]

Common Mistakes:

• Placing recursive call outside timeout callback
• Assuming timeout delays recursion automatically
• Ignoring stack overflow risk

5. You want to run a task every 3 seconds but ensure the task never overlaps if it takes longer than 3 seconds. Which approach is best?

hard

A. Use recursive setTimeout scheduling the next call only after task finishes.

B. Use setInterval with 3000ms delay and ignore task duration.

C. Use setTimeout once without recursion.

D. Use setInterval with 1000ms delay and check task status inside.

Solution

1. Step 1: Understand overlap risk with setInterval

   setInterval runs tasks at fixed intervals regardless of task duration, causing overlap if task takes longer than interval.

2. Step 2: Use recursive setTimeout to control timing

   Recursive setTimeout schedules the next run only after the current task finishes, preventing overlap.

3. Final Answer:

   Use recursive setTimeout scheduling the next call only after task finishes. -> Option A

4. Quick Check:

   Prevent overlap with recursive timeout [OK]

Hint: Recursive timeout waits for task end before next call [OK]

Common Mistakes:

• Using setInterval ignoring task duration
• Not scheduling next call after task completion
• Using too short intervals causing overlap