From f4dfb0a184a0218a8fd0927b3a80f0fb8956ba50 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Sat, 22 Aug 2015 16:08:27 -0700 Subject: [PATCH] Merge pull request #4687 from lyip1992/patch-6 Update 04-multiple-components.md (cherry picked from commit 7dbcff2df45510409288014b9bad02d345744932) --- docs/docs/04-multiple-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/04-multiple-components.md b/docs/docs/04-multiple-components.md index 22c96391d6..cf57260a96 100644 --- a/docs/docs/04-multiple-components.md +++ b/docs/docs/04-multiple-components.md @@ -181,7 +181,7 @@ In React, data flows from owner to owned component through `props` as discussed ## A Note on Performance -You may be thinking that it's expensive to change data if there are a large number of nodes under an owner. The good news is that JavaScript is fast and `render()` methods tend to be quite simple, so in most applications this is extremely fast. Additionally, the bottleneck is almost always the DOM mutation and not JS execution. React will optimize this for you using batching and change detection. +You may be thinking that it's expensive to change data if there are a large number of nodes under an owner. The good news is that JavaScript is fast and `render()` methods tend to be quite simple, so in most applications this is extremely fast. Additionally, the bottleneck is almost always the DOM mutation and not JS execution. React will optimize this for you by using batching and change detection. However, sometimes you really want to have fine-grained control over your performance. In that case, simply override `shouldComponentUpdate()` to return false when you want React to skip processing of a subtree. See [the React reference docs](/react/docs/component-specs.html) for more information.