From 709bac6c484bbd5f334e6e89e268f479ae74296e Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Thu, 25 Jun 2020 08:51:31 -0500 Subject: [PATCH] Blazor WASM perf ShouldRender updates (#18957) --- aspnetcore/blazor/webassembly-performance-best-practices.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/blazor/webassembly-performance-best-practices.md b/aspnetcore/blazor/webassembly-performance-best-practices.md index 5302b034c3..036496063a 100644 --- a/aspnetcore/blazor/webassembly-performance-best-practices.md +++ b/aspnetcore/blazor/webassembly-performance-best-practices.md @@ -5,7 +5,7 @@ description: Tips for increasing performance in ASP.NET Core Blazor WebAssembly monikerRange: '>= aspnetcore-2.1' ms.author: riande ms.custom: mvc -ms.date: 06/08/2020 +ms.date: 06/25/2020 no-loc: [Blazor, "Identity", "Let's Encrypt", Razor, SignalR] uid: blazor/webassembly-performance-best-practices --- @@ -27,7 +27,7 @@ If authoring a UI-only component that never changes after the initial render, co } ``` -Most apps don't require fine-grained control, but can also be used to selectively render a component responding to a UI event. +Most apps don't require fine-grained control, but can be used to selectively render a component responding to a UI event. Using might also be important in scenarios where a large number of components are rendered. Consider a grid, where use of in one component in one cell of the grid calls on the grid. Calling causes a re-render of every child component. If only a small number of cells require rerendering, use to avoid the performance penalty of unnecessary renders. In the following example: