Course contentsShow
← React
Lesson 835 of 2,39622. Context PerformanceFree lesson

When Context Re-renders Hurt

Recognizing problematic patterns: large component trees, frequent updates, or expensive render logic in consumers.

When Context Re-renders Hurt

You'll learn: How to spot situations where context re-renders seriously damage your app's performance.

The Problem Patterns

You already know that context causes unavoidable re-renders in all consumers. Sometimes that's totally fine—but sometimes it cripples your app. Here are the red flags:

Large Component Trees

When a single context provider wraps hundreds of components, and many of them consume that context, a single value change triggers a cascade of re-renders. Imagine a tree with 50 consumer components—they all re-render on every context update, even if most don't care about what changed.

Frequent Updates

Context values that change rapidly (like mouse position, scroll offset, or form inputs being typed) create a re-render storm. If your context updates 60 times per second, every consumer re-renders 60 times per second. That's expensive.

Expensive Render Logic

Even if individual components are fast, consumers with heavy render work amplify the problem. A context update that triggers 20 components, each taking 10ms to render, freezes your UI for 200ms. Users notice anything over 16ms.

The Compound Effect

These patterns multiply each other's damage. A large tree + frequent updates + expensive consumers = a laggy, unusable application. The profiler will show time spent in React's reconciliation process dominating your performance budget.

Key Takeaway: Context re-renders hurt when you have deep component trees with many consumers, frequent value changes, or render-heavy consumer components—especially when these factors combine.