ReactJS From Zero Part 7: Performance, Memoization, and React Compiler | ReactJS 從零開始之七：Performance、Memoization 同 React Compiler

Posted May 12, 2026

By Stan Li

14 min read

Series navigation: Part 7 of 10
Previous: Part 6 built reusable composition and shared context.
Next: Part 8 introduces async UI patterns: Suspense, lazy loading, transitions, optimistic updates, and Actions.
Version note: npm reported react@19.2.6 while the official docs currently document React 19.2.

English Version

Where This Part Fits

Part 6 built reusable composition and shared context. In this part we focus on render performance, memo, useMemo, useCallback, Profiler, React Compiler. The goal is not to memorize API names. The goal is to build a mental model that helps you read code written by another developer and predict what React will do next.

Performance work is not guessing which waiter is slow. You first watch the whole restaurant during rush hour, then optimize the station that actually blocks orders.

React rewards small, explicit steps. A beginner often tries to understand the whole app at once, then gets lost. A real programmer usually moves in the opposite direction: find one component, find its inputs, find its local memory, find the event that changes that memory, then follow the render.

Core Terms

Term	Beginner meaning
`measure first`	Use React DevTools Profiler before adding memo everywhere.
`memo`	Skip child re-rendering when props are unchanged.
`useMemo/useCallback`	Cache expensive values or stable function props when there is a concrete need.
`React Compiler`	A build-time optimizer that can reduce manual memoization in supported projects.

The Render Story

A React screen is a tree. The root renders App, App renders smaller components, and those components render even smaller pieces. When state changes, React does not ask you to manually patch the DOM. It calls your component again, receives the next UI description, compares it with the previous description, and updates the browser efficiently.

The beginner mistake is thinking “render” means “delete the whole page and rebuild everything.” That is not the useful mental model. A better model is: render means your component function is asked to describe what the UI should look like for the current inputs. React then decides the minimal DOM work.

For this post, keep these names in your head: measure first, memo, useMemo/useCallback, React Compiler. Every code example below is just another way of combining those same ideas.

粵語中文版

今篇喺系列入面嘅位置

Part 6 built reusable composition and shared context. 今篇集中講 render performance, memo, useMemo, useCallback, Profiler, React Compiler。目標唔係背 API 名，而係建立一個腦內地圖：當你睇到其他人寫嘅 React code，你可以估到下一步 React 會做咩。

Performance 唔係估邊個侍應慢；你要先喺繁忙時間睇全場，搵到真係卡住出餐嗰個位，先落手優化。

React 最鍾意細步、清楚、可預測。新手成日一嚟就想理解成個 app，結果就迷路。實戰 programmer 通常倒轉做：先搵一個 component，睇佢收咩 input，睇佢自己記住咩 state，睇邊個 event 會改 state，最後跟住 render 條路行。

核心 Terms

Term	新手理解
`measure first`	Use React DevTools Profiler before adding memo everywhere. 呢個 term 我哋先保留英文，因為你之後睇官方 docs、Stack Overflow、GitHub issue 都會見到同一個字。
`memo`	Skip child re-rendering when props are unchanged. 呢個 term 我哋先保留英文，因為你之後睇官方 docs、Stack Overflow、GitHub issue 都會見到同一個字。
`useMemo/useCallback`	Cache expensive values or stable function props when there is a concrete need. 呢個 term 我哋先保留英文，因為你之後睇官方 docs、Stack Overflow、GitHub issue 都會見到同一個字。
`React Compiler`	A build-time optimizer that can reduce manual memoization in supported projects. 呢個 term 我哋先保留英文，因為你之後睇官方 docs、Stack Overflow、GitHub issue 都會見到同一個字。

Render 呢件事點諗

React 畫面係一棵 tree。root render App，App render 細 component，細 component 再 render 更細嘅 UI。當 state 改變，React 唔係要你人手 patch DOM；佢會再 call 你個 component，攞到下一個 UI 描述，再同上一個描述比較，最後更新 browser 入面需要改嘅地方。

新手常見誤會係覺得 render 等於「成頁刪晒再砌過」。咁諗會令你驚。更實用嘅諗法係：render 即係 component function 根據而家嘅 inputs 描述畫面；至於 DOM 點樣最少量更新，交俾 React。

Example 1: Read the Code Slowly

Before reading the snippet, predict three things: what data enters the component, what event can happen, and what visible output should change. After reading it, explain it once in English and once in Cantonese. This habit trains you to understand React code without depending on tutorials forever.

  
import { memo, useMemo, useState } from 'react';

const ProductCard = memo(function ProductCard({
  product,
  onSelect
}: {
  product: Product;
  onSelect: (id: string) => void;
}) {
  return (
    <button className="product-card" onClick={() => onSelect(product.id)}>
      <strong>{product.name}</strong>
      <span>${product.price}</span>
    </button>
  );
});

English walkthrough: Start from the component boundary. Check the props or local variables first. Then scan for Hooks because Hooks tell you what the component remembers or synchronizes. Finally, read the returned JSX as a plain UI description. If the example has an event handler, imagine the click or typing action, then follow the state update into the next render.

粵語 walkthrough： 由 component 邊界開始睇。先睇 props 或 local variables，再掃 Hooks，因為 Hooks 會話你知 component 記住咩或者同步咩。最後將 JSX 當成普通 UI 描述咁讀。如果有 event handler，就想像自己 click 或打字，跟住 state update 行去下一次 render。

Example 2: Read the Code Slowly

  
function ProductGrid({ products }: { products: Product[] }) {
  const [query, setQuery] = useState('');
  const [sortBy, setSortBy] = useState<'name' | 'price'>('name');

  const visibleProducts = useMemo(() => {
    return products
      .filter(product => product.name.toLowerCase().includes(query.toLowerCase()))
      .toSorted((a, b) =>
        sortBy === 'name'
          ? a.name.localeCompare(b.name)
          : a.price - b.price
      );
  }, [products, query, sortBy]);

  return (
    <>
      <SearchBox value={query} onChange={setQuery} />
      <SortSelect value={sortBy} onChange={setSortBy} />
      {visibleProducts.map(product => (
        <ProductCard key={product.id} product={product} onSelect={openProduct} />
      ))}
    </>
  );
}

Example 3: Read the Code Slowly

  
// React Compiler can automatically memoize many components.
// Manual memoization still matters when you are not using the compiler,
// when profiling proves a bottleneck, or when integrating older code.

function InvoiceTotal({ lines }: { lines: InvoiceLine[] }) {
  const total = lines.reduce((sum, line) => sum + line.quantity * line.price, 0);
  return <output>${total.toFixed(2)}</output>;
}

Example 4: Read the Code Slowly

  
// Compiler directive examples for gradual adoption.
function StableReportTable({ rows }: { rows: ReportRow[] }) {
  "use memo";
  return <Table rows={rows} />;
}

function ThirdPartyWrapper() {
  "use no memo"; // Temporary opt-out while investigating library behavior.
  return <LegacyChart />;
}

Practice Lab: Build It, Break It, Fix It

This lab connects this article to the rest of the series. Do not only paste the code. Type it, rename variables, remove one line at a time, and watch the browser complain. React becomes much less scary when you learn what each error message is trying to protect.

Create a fresh Vite React TypeScript project.
Copy the smallest example from this post first.
Add one feature from the previous post so the knowledge chain stays connected.
Add one tiny feature that prepares you for the next post: Part 8 introduces async UI patterns: Suspense, lazy loading, transitions, optimistic updates, and Actions.
Open React DevTools and inspect the component tree.
Write down which values are props, which values are state, and which values are plain derived variables.

Cantonese Practice Notes

今篇唔好只係 copy code。你要試吓打錯 prop 名、刪走 dependency、用錯 key、或者將 state 直接 mutate，睇吓 React 同 browser 會點樣提醒你。新手最容易驚 error，但其實 error 係老師傅喺你後面提你：「呢度遲早會爆，依家快啲修正。」

如果畫面冇更新，先問：我係咪改咗舊 object，而唔係建立新 object？
如果 effect 不停跑，先問：dependency 係咪每次 render 都變成新 reference？
如果 list 行為怪，先問：key 係咪穩定 ID，而唔係 array index？
如果 form 打唔到字，先問：input value 有冇配返 onChange？
如果 component 好難測，先問：我係咪將太多責任塞咗入同一個 function？

flowchart TD
    A[Read the UI] --> B[Find the component]
    B --> C[Identify props]
    C --> D[Identify state]
    D --> E[Trigger event]
    E --> F[React renders again]
    F --> G[Compare expected DOM]
    G --> H{Bug?}
    H -->|Yes| B
    H -->|No| I[Add the next small feature]

Debugging Checklist for Part 7

Read the browser console before changing code randomly.
Check whether the bug happens before render, during render, or after render in an Effect.
Use descriptive component names; ProductCard teaches your future self more than Box.
Keep event handlers small. If an event needs ten steps, move the calculation into a helper function and test it separately.
Prefer boring state names: isOpen, selectedId, draftTitle, status, error.
When you feel tempted to add a library, first build the tiny version yourself so you know what problem the library solves.

Common Beginner Mistakes

Trying to learn React by memorizing syntax only. Syntax matters, but the mental model matters more.
Mixing data calculation with DOM manipulation. In React, calculate data first, then describe UI.
Keeping duplicate state. If a value can be calculated from existing props or state, calculate it during render.
Making one giant component. When a JSX block becomes hard to scan, extract a named component.
Ignoring official docs. For React 19.2, the official docs are practical and example-heavy.

新手常犯錯

只背 syntax。Syntax 要識，但 mental model 更重要。
將 data calculation 同 DOM manipulation 撈埋一齊。React 入面通常係先計 data，再描述 UI。
儲 duplicate state。如果一個 value 可以由現有 props 或 state 計出嚟，就唔好再開多個 state。
一個 component 寫到成座山咁大。JSX 一難 scan，就抽做有名 component。
唔睇官方 docs。React 19.2 docs 已經有好多實用例子，尤其係 Hooks、Effects、Server APIs 同 Compiler 部分。

References

React docs version page: https://react.dev/versions
React 19.2 release notes: https://react.dev/blog/2025/10/01/react-19-2
React Hooks reference: https://react.dev/reference/react/hooks
React Activity reference: https://react.dev/reference/react/Activity
React useEffectEvent reference: https://react.dev/reference/react/useEffectEvent
React Compiler guide: https://react.dev/learn/react-compiler

Frontend, React

This post is licensed under CC BY 4.0 by the author.