Concurrent Features vs Other Optimizations
You'll learn when to reach for concurrent React features versus simpler performance fixes.
The Right Tool for the Job
Concurrent features like useTransition and useDeferredValue are powerful, but they're not magic performance bullets. Often, other optimization strategies solve the problem more directly and efficiently.
Think of it like fixing a slow website: you could upgrade to a faster server (concurrent features), or you could just optimize the images that are slowing everything down (traditional optimizations). The second approach is usually smarter.
When Concurrent Features Are Overkill
Virtualization wins for long lists: If you're rendering 10,000 items and it's slow, useTransition won't help—you're still rendering 10,000 items, just in a lower priority. Instead, use virtualization (like react-window) to only render what's visible.
Memoization stops unnecessary work: If a component re-renders expensively because of new object references, useMemo or React.memo prevents the computation entirely. Concurrent features still do the work—they just interrupt it.
Moving work outside render is best: If you're doing heavy calculations during render, move them to useMemo, web workers, or even the server. Concurrent features can't make inefficient code fast.
When Concurrent Features Shine
Use useTransition or useDeferredValue when:
- The computation is necessary and can't be avoided
- You've already memoized appropriately
- The issue is UI responsiveness during inevitable heavy renders
- You want to keep input feeling instant while background updates catch up
The Hierarchy
- First: Fix inefficient code (unnecessary renders, bad algorithms)
- Second: Apply memoization and virtualization
- Third: Use concurrent features for remaining responsiveness issues
Key Takeaway: Concurrent features prioritize work smartly, but other optimizations eliminate or reduce work entirely—always optimize the work itself before changing how React schedules it.