Callback functions for state updates in React - Performance & Optimization

Performance: Callback functions for state updates

MEDIUM IMPACT

This affects how React batches and schedules state updates, impacting interaction responsiveness and rendering efficiency.

Updating state based on previous state in React

React

const [count, setCount] = useState(0);

// Good: use callback to get latest state
function increment() {
  setCount(prevCount => prevCount + 1);
}

Callback ensures the latest state is used, preventing stale updates and reducing unnecessary renders.

📈 Performance GainReduces re-renders and improves input responsiveness (INP).

Updating state based on previous state in React

React

const [count, setCount] = useState(0);

// Bad: directly using state variable in setState
function increment() {
  setCount(count + 1);
}

This can cause stale state updates when multiple updates happen quickly, leading to extra renders or incorrect state.

📉 Performance CostTriggers multiple re-renders and can cause layout thrashing if updates are frequent.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct state update (setCount(count + 1))	Multiple updates may cause repeated DOM changes	Multiple reflows if updates trigger layout changes	Higher paint cost due to extra renders	[X] Bad
Callback state update (setCount(prev => prev + 1))	Batched updates reduce DOM changes	Single reflow for batched updates	Lower paint cost with fewer renders	[OK] Good

Rendering Pipeline

React schedules state updates and batches them before triggering a re-render. Using callback functions ensures updates are based on the latest state, minimizing redundant renders and layout recalculations.

→State Update Scheduling

→Reconciliation

→Render

→Commit

⚠️ BottleneckReconciliation and Render stages due to unnecessary or stale updates causing extra work.

Core Web Vital Affected

INP

This affects how React batches and schedules state updates, impacting interaction responsiveness and rendering efficiency.

Optimization Tips

1Always use callback functions when new state depends on previous state.

2Avoid direct state updates that rely on current state variables to prevent stale values.

3Batch state updates to minimize re-renders and layout recalculations.

Performance Quiz - 3 Questions

Why is using a callback function in setState better for performance?

A It prevents any re-render from happening.

B It always uses the latest state value, preventing stale updates.

C It delays the update until the next page load.

D It increases the bundle size slightly.

DevTools: React DevTools and Chrome Performance panel

How to check: Use React DevTools Profiler to record interactions and see how many renders occur per update. Use Chrome Performance to check layout and paint events during state changes.

What to look for: Look for fewer renders and less layout thrashing when using callback state updates compared to direct state updates.

Practice

1. Why should you use a callback function when updating state in React with useState?

easy

A. Because it safely uses the previous state value to calculate the new state.

B. Because it makes the component render twice automatically.

C. Because it prevents the component from updating.

D. Because it allows you to update multiple states at once.

Solution

1. Step 1: Understand state updates in React

   State updates can be asynchronous, so relying on the current state value directly can cause bugs.

2. Step 2: Use callback function to access previous state

   The callback function receives the previous state safely and returns the new state, ensuring correct updates.

3. Final Answer:

   Because it safely uses the previous state value to calculate the new state. -> Option A

4. Quick Check:

   Callback uses previous state = safe update [OK]

Hint: Use callback to get previous state safely for updates [OK]

Common Mistakes:

• Updating state directly without callback causes stale values
• Thinking callback triggers extra renders
• Believing callback merges multiple states automatically

2. Which of the following is the correct syntax to update state using a callback function with useState?

easy

A. setCount(count + 1);

B. setCount(prevCount => prevCount + 1);

C. setCount(() => count + 1);

D. setCount(prevCount + 1);

Solution

1. Step 1: Identify correct callback syntax

   The callback function receives previous state as an argument and returns the new state.

2. Step 2: Check each option

   setCount(prevCount => prevCount + 1); uses prevCount => prevCount + 1, which is the correct callback form.

3. Final Answer:

   setCount(prevCount => prevCount + 1); -> Option B

4. Quick Check:

   Callback syntax = setState(prev => new) [OK]

Hint: Callback syntax always uses previous state parameter [OK]

Common Mistakes:

• Passing new state directly without function
• Using arrow function without parameter
• Trying to add number outside callback

3. What will be the output after clicking the button twice in this React component?

function Counter() {
  const [count, setCount] = React.useState(0);
  function increment() {
    setCount(prev => prev + 1);
  }
  return (
    <button onClick={increment}>Count: {count}</button>
  );
}

medium

A. Count: 2

B. Count: NaN

C. Count: 0

D. Count: 1

Solution

1. Step 1: Understand initial state and increment function

   Initial count is 0. Each click calls increment which updates state by adding 1 to previous count.

2. Step 2: Calculate state after two clicks

   First click: 0 + 1 = 1. Second click: 1 + 1 = 2.

3. Final Answer:

   Count: 2 -> Option A

4. Quick Check:

   Two increments = count 2 [OK]

Hint: Each click adds 1 to previous count using callback [OK]

Common Mistakes:

• Assuming state updates are batched incorrectly
• Using stale count value without callback
• Expecting count to reset after each click

4. Identify the error in this React state update code:

const [value, setValue] = React.useState(0);
function update() {
  setValue(value + 1);
  setValue(value + 1);
}

medium

A. setValue cannot be called twice in one function.

B. Syntax error: missing callback function.

C. State updates will be batched and only increase by 1, not 2.

D. State will reset to 0 after update.

Solution

1. Step 1: Analyze multiple state updates with direct value

   Both calls use the same stale value (0), so both set to 1.

2. Step 2: Understand batching behavior

   React batches updates, so final state is 1, not 2.

3. Final Answer:

   State updates will be batched and only increase by 1, not 2. -> Option C

4. Quick Check:

   Direct state updates = stale value, batched result [OK]

Hint: Multiple direct updates use stale state, use callback instead [OK]

Common Mistakes:

• Thinking setValue calls add up automatically
• Believing syntax error occurs without callback
• Assuming state resets unexpectedly

5. You want to toggle a boolean state isOpen in React. Which is the best way to update it safely when the new state depends on the old state?

hard

A. setIsOpen(false);

B. setIsOpen(!isOpen);

C. setIsOpen(true);

D. setIsOpen(prev => !prev);

Solution

1. Step 1: Understand toggling boolean state

   Toggling means switching from true to false or false to true based on previous state.

2. Step 2: Choose callback to avoid stale state

   Using prev => !prev ensures the toggle uses the latest state safely.

3. Final Answer:

   setIsOpen(prev => !prev); -> Option D

4. Quick Check:

   Toggle boolean safely = callback with previous state [OK]

Hint: Toggle booleans with callback using previous state [OK]

Common Mistakes:

• Using direct negation causes stale state bugs
• Setting fixed true or false instead of toggling
• Not using callback for dependent state updates