🇮🇳 React India 2022

ℹ️ Deep diving on Concurrent React

Writing fluid user interfaces become more and more challenging as the application complexity increases. In this talk, we’ll explore how proper scheduling improves your app’s experience by diving into some concurrent React features, understanding their rationales, and how they work under the hood.

Transcript

1. Hello, React India 🙋 🇮🇳 🌏 DEEP DIVING ON CONCURRENT REACT • THE 23RD OF SEPTEMBER, 2022.
2. DEEP DIVING ON CONCURRENT REACT MATHEUS ALBUQUERQUE
3. Å I’M MATHEUS 🙋 ↝ @YTHECOMBINATOR ON THE WEB ↝ SR. SOFTWARE ENGINEER @MEDALLIA ↝ MENTOR @TECHLABS
4. Disclaimers DEEP DIVING ON CONCURRENT REACT
5. #1 REACT SOURCE CODE IS CONSTANTLY CHANGING, AND SOME THOUGHTS ARE SPECULATIVE DEEP DIVING ON CONCURRENT REACT
6. #2 🤯 = FURTHER DISCUSSIONS AFTER THE SESSION DEEP DIVING ON CONCURRENT REACT
7. Prologue DEEP DIVING ON CONCURRENT REACT
8. DEEP DIVING ON CONCURRENT REACT
9. WE TALKED ABOUT… ↝ FIBERS ↝ COROUTINES ↝ GENERATORS ↝ ALGEBRAIC EFFECTS
10. WE TALKED ABOUT… ↝ VIRTUAL DOM ↝ CONCURRENCY/PARALLELISM ↝ CONCURRENT REACT ↝ MEASUREMENT
11. DATA-DRIVEN UI LIBS DOM RECONCILIATION E.G. ANGULAR, POLYMER, LIT-HTML VIRTUAL DOM E.G. REACT, VUE, INFERNO REACTIVE E.G. KNOCKOUT, SVELTE, SOLID
12. DOM RECONCILIATION E.G. ANGULAR, POLYMER, LIT-HTML VIRTUAL DOM E.G. REACT, VUE, INFERNO REACTIVE E.G. KNOCKOUT, SVELTE, SOLID DATA-DRIVEN UI LIBS
13. DEEP DIVING ON CONCURRENT REACT
14. #QUOTE 💬 “[…] With React you can build applications without even thinking about performance and the default state is fast.” — Rethinking Best Practices by Pete Hunt, 2013
15. ↝ GENERATE A VIRTUAL TREE AND THEN DIFF AGAINST THE PREVIOUS ITERATION ↝ PATCH THE DOM UPDATES ↝ USE IMMUTABILITY AND REFERENTIAL EQUALITY TO OPTIMIZE THE PROCESS WHICH RESULTS IN SIGNIFICANT CLONING AND MEMORY ALLOCATION VIRTUAL DOM
16. ↝ shouldComponentUpdate, React.PureComponent ↝ React.memo ↝ useMemo, useCallback ↝ useTransition, useDeferredValue, React.Suspense & others PERF MITIGATORS
17. #PROTIP 💡 React doesn’t have any understanding of the values running through your app. It’s not reactive.
20. VIRTUAL DOM ↝ IT HAS BEEN OPTIMIZED WELL ENOUGH IN MOST SCENARIOS ↝ WE DON’T COMPLAIN ABOUT PERF IN INFERNO OR BUNDLE SIZE IN PREACT ↝ THERE ARE LIBRARIES THAT CAN PRODUCE EQUIVALENT/SMALLER BUNDLES (E.G. HyperApp)
21. VIRTUAL DOM ↝ IT'S JUST ONE OF THE APPROACHES WE HAVE AND IT'S NEVER A TRUE/FALSE QUESTION ↝ UNDERSTANDING ITS KEY TAKEAWAYS HELPS US UNDERSTAND WHERE CONCURRENT REACT FITS
22. #QUESTION 🤔 Why do we even bother discussing Concurrent React?
23. PERFOMANCE
24. PERFOMANCE PERCEIVED LOAD SPEED HOW QUICKLY A PAGE CAN LOAD AND RENDER ALL OF ITS VISUAL ELEMENTS TO THE SCREEN SMOOTHNESS DO TRANSITIONS & ANIMATIONS RENDER AT A CONSISTENT FRAME RATE AND FLOW FLUIDLY? LOAD RESPONSIVENESS HOW QUICKLY A PAGE CAN LOAD/RUN ANY REQUIRED JS IN ORDER FOR COMPONENTS TO RESPOND TO USER INTERACTION RUNTIME RESPONSIVENESS AFTER THE PAGE LOAD, HOW QUICKLY CAN THE PAGE RESPOND TO USER INTERACTION?
25. PERFOMANCE PERCEIVED LOAD SPEED HOW QUICKLY A PAGE CAN LOAD AND RENDER ALL OF ITS VISUAL ELEMENTS TO THE SCREEN LOAD RESPONSIVENESS HOW QUICKLY A PAGE CAN LOAD/RUN ANY REQUIRED JS IN ORDER FOR COMPONENTS TO RESPOND TO USER INTERACTION RUNTIME RESPONSIVENESS AFTER THE PAGE LOAD, HOW QUICKLY CAN THE PAGE RESPOND TO USER INTERACTION? SMOOTHNESS DO TRANSITIONS & ANIMATIONS RENDER AT A CONSISTENT FRAME RATE AND FLOW FLUIDLY?
27. LONG TASKS
29. PHONE USERS EXPERIENCE SLOW FIRST INPUT DELAY ON 7X MORE WEBSITES. — Web Almanac By HTTP Archive, 2021
30. DESKTOP PHONE 0 25 50 75 100 SLOW ( > = 250MS) AVERAGE FAST (<50 MS) FIRST INPUT DELAY
31. BUSINESS OUTCOMES ↝ LONG TASKS DELAYED TTI ↝ AS FIRST-PAGE LONG TASK TIME INCREASED, OVERALL CONVERSION RATES DECREASED ↝ MOBILE HAD UP TO ˜12X LONGER LONG TASKS ↝ OLDER DEVICES COULD BE SPENDING HALF OF THEIR LOAD-TIME ON LONG TASKS — AKAMAI AND CHROME RESEARCH, 2017
32. — AKAMAI AND CHROME RESEARCH, 2017 BUSINESS OUTCOMES
33. #ANSWER 💡 That’s why we do bother discussing Concurrent React!
34. #QUESTION 🤔 If you were to summarize Concurrent React in one word/expression, what’d be your pick?
35. #QUESTION 🤔 If you were to summarize Concurrent React in one word/expression, what’d be your pick? e.g. fibers ↝ units of work Concurrent React ↝ ???
36. DEEP DIVING ON CONCURRENT REACT If you were to summarize Concurrent React in one word/expression, what’d be your pick?
37. DEEP DIVING ON CONCURRENT REACT If you were to summarize Concurrent React in one word/expression, what’d be your pick? 1st/2nd/3rd ANSWERS ↝ REACT BRUSSELS DISCOUNT CODE 🇧🇪 OTHERS ↝ STICKERS 💅
38. The Main Thread DEEP DIVING ON CONCURRENT REACT
39. TASKS JAVASCRIPT STYLES LAYOUT PAINT COMPOSITE A UNIT OF WORK THAT THE BROWSER DOES TO RENDER A FRAME
40. TASKS JAVASCRIPT STYLES LAYOUT PAINT COMPOSITE
41. LONG TASKS ↝ IF A TASK TAKES MORE THAN 50 MS, USER INPUT FEELS DELAYED ↝ BASED ON THE USER-CENTRIC PERFORMANCE MODEL CALLED RAIL ↝ THEY TAKE TOO LONG AND BLOCK OTHER TASKS
42. #QUESTION 🤔 How to avoid blocking the main thread?
43. PARALLELISM ↝ MULTIPLE THREADS = MULTIPLE TASKS AT THE SAME TIME ON SEPARATE CPU CORES CONCURRENCY ↝ SINGLE THREAD + QUICKLY SWITCHING BETWEEN TASKS SCHEDULING ↝ CONCURRENCY + TASK PRIORITIZATION TASK RUNNING STRATEGIES
44. TASK RUNNING STRATEGIES A B C D
45. TASK RUNNING STRATEGIES PARALLELISM CONCURRENCY SCHEDULING
46. TASK RUNNING STRATEGIES PARALLELISM CONCURRENCY SCHEDULING
47. WORKERS ↝ VERY DIFFERENT FROM THE THREADS IN C++, JAVA, ETC. ↝ NO ACCESS TO ANY VARIABLES/CODE FROM THE PAGE THAT CREATED THEM OR VICE VERSA ↝ DATA EXCHANGE IS THROUGH MESSAGE-PASSING
48. WORKERS ↝ NO ACCESS TO THE DOM, MAKING UI UPDATES FROM A WORKER BARELY IMPOSSIBLE ↝ APPS THAT INTEND TO USE THEM HAVE TO ADAPT THEIR ARCHITECTURE TO ACCOMMODATE THESE REQUIREMENTS ↝ TWO MODELS: ACTORS & SHARED MEMORY 🤯
49. ACTORS ↝ EACH ACTOR MAY OR MAY NOT RUN ON A SEPARATE THREAD ↝ EACH ACTOR FULLY OWNS THE DATA IT IS OPERATING ON ↝ ACTORS CAN ONLY SEND/REACT TO MESSAGES ↝ MAIN THREAD = ACTOR THAT OWNS THE DOM/UI 🤯
50. ACTORS ↝ EVERY MESSAGE WE SEND NEEDS TO BE COPIED ↝ BALANCE: MOVING CODE TO A WORKER VS COMMUNICATION OVERHEAD/WORKER BEING BUSY ↝ postMessage IS A FIRE-AND-FORGET MESSAGING MECHANISM WITH NO BUILT-IN UNDERSTANDING OF REQUEST AND RESPONSE 🤯
51. SHARED MEMORY ↝ ONE DEDICATED TYPE: SharedArrayBuffer ↝ A LINEAR CHUNK OF MEMORY THAT CAN BE MANIPULATED USING TypedArrays OR DataViews ↝ IF SENT VIA postMessage, THE OTHER END GETS A HANDLE TO THE EXACT SAME MEMORY CHUNK 🤯
52. SHARED MEMORY ↝ MOST OF THE APIS ARE BUILT NO CONCURRENT ACCESS TO OBJECTS IN MIND ↝ YOU BUILD YOUR OWN MUTEXES AND OTHER CONCURRENT DATA STRUCTURES ↝ NO DIRECT WAY OF WORKING ON FAMILIAR OBJECTS/ARRAYS; JUST A SERIES OF BYTES 🤯
53. WEB ASSEMBLY ↝ WORKERS + SharedArrayBuffers TO SUPPORT THE THREADING MODEL OF C++ AND OTHERS ↝ BEST EXPERIENCE FOR SHARED-MEMORY MODEL ↝ FASTER THAN JS WHEN YOU STAY WITHIN WASM, BUT THE MORE YOU HAVE TO CROSS OVER TO JS APIS THE SLOWER IT IS
54. WEB ASSEMBLY ↝ JAVASCRIPT IS OFTEN FASTER AT DOING DOM RENDERING ↝ HIGH-LEVEL LIBRARIES CAN BE MORE PERFORMANT THAN LOW-LEVEL WASM IMPLEMENTATIONS ↝ DOESN’T OFFER LOT OF THE BENEFITS (AND COMFORT) OF JAVASCRIPT
55. ↝ Atomics ↝ BuffferBackedObject ↝ Comlink ↝ WorkerDOM
56. WORKERS ↝ GOOD FOR DATA PROCESSING AND CRUNCHING NUMBERS ↝ HARD TO USE FOR UI-RELATED STUFF ↝ HARDER THAN ADJUSTING IT FOR A SCHEDULER
57. TASK RUNNING STRATEGIES PARALLELISM CONCURRENCY SCHEDULING
58. #QUESTION 🤔 If you were to summarize Concurrent React in one word/expression, what’d be your pick?
59. DEEP DIVING ON CONCURRENT REACT If you were to summarize Concurrent React in one word/expression, what’d be your pick?
60. Scheduling in React DEEP DIVING ON CONCURRENT REACT
61. function resourcefulOperation(value: number) { let newValue = String(value); for (let i = 0; i < 1000000; i++) { newValue = `${value} + ${i} = ${value + i}`; } return newValue; } function ResourcefulComponent(props: { value: number }) { const { value } = props; const result = resourcefulOperation(value); return <p>{result}</p>; }
62. DEEP DIVING ON CONCURRENT REACT
63. #QUESTION 🤔 How could we improve that?
64. DEEP DIVING ON CONCURRENT REACT
66. function resourcefulOperation(value: number) { let newValue = String(value); for (let i = 0; i < 1000000; i++) { newValue = `${value} + ${i} = ${value + i}`; } return newValue; } function ResourcefulComponent(props: { value: number }) { const { value } = props; const result = resourcefulOperation(value); return <p>{result}</p>; }
67. function* resourcefulOperation(value: number) { let newValue = String(value); while (true) { yield; for (let i = 0; i < 1000000; i++) { newValue = `${value} + ${i} = ${value + i}`; } return newValue; } } const initialValue = 0; const scheduler = new Scheduler(resourcefulOperation, initialValue); function ResourcefulComponent(props: { value: number }) { const { value } = props; const result = scheduler.performUnitOfWork(value); return <p>{result}</p>; }
68. function* resourcefulOperation(value: number) { let newValue = String(value); while (true) { yield; for (let i = 0; i < 1000000; i++) { newValue = `${value} + ${i} = ${value + i}`; } return newValue; } } const initialValue = 0; const scheduler = new Scheduler(resourcefulOperation, initialValue); function ResourcefulComponent(props: { value: number }) { const { value } = props; const result = scheduler.performUnitOfWork(value); return <p>{result}</p>; } PROMOTED TO A GENERATOR YIELDING EXECUTION DOING CONCURRENT TASKS
69. DEEP DIVING ON CONCURRENT REACT
70. enum SchedulerState { IDLE = "IDLE", PENDING = "PENDING", DONE = "DONE", } class Scheduler<T> { state: SchedulerState; result: T; worker: (data: T) = > Generator; iterator: Generator; constructor(worker: (data: T) = > Generator, initialResult: T) { this.state = SchedulerState.IDLE; this.worker = worker; this.result = initialResult; } performUnitOfWork(data: T) { switch (this.state) { case "IDLE": this.state = SchedulerState.PENDING; this.iterator = this.worker(data); throw Promise.resolve(); case "PENDING": const { value, done } = this.iterator.next(); if (done) { this.result = value; this.state = SchedulerState.DONE; return value; } throw Promise.resolve(); case "DONE": this.state = SchedulerState.IDLE; return this.result; } } }
71. performUnitOfWork(data: T) { switch (this.state) { case "IDLE": this.state = SchedulerState.PENDING; this.iterator = this.worker(data); throw Promise.resolve(); case "PENDING": const { value, done } = this.iterator.next(); if (done) { this.result = value; this.state = SchedulerState.DONE; return value; } throw Promise.resolve(); case "DONE": this.state = SchedulerState.IDLE; return this.result; } }
72. DID WE JUST useTransition’ED? 🤔
73. function resourcefulOperation(value: number) { let newValue = String(value); for (let i = 0; i < 1000000; i++) { newValue = `${value} + ${i} = ${value + i}`; } return newValue; } function ResourcefulComponent(props: { value: number }) { const { value } = props; const result = resourcefulOperation(value); return <p>{result}</p>; }
74. function resourcefulOperation(value: number) { let newValue = String(value); for (let i = 0; i < 1000000; i++) { newValue = `${value} + ${i} = ${value + i}`; } return newValue; } function ResourcefulComponent(props: { value: number }) { const [_, startTransition] = useTransition(); const [result, setResult] = useState(""); useEffect(() = > { startTransition(() = > { const newResult = resourcefulOperation(props.value); setResult(newResult); }); }, [props.value]); return <p>{result}</p>; }
75. YES, WE DID 🤓 WITH OUR OWN SCHEDULER
76. ↝ A COOPERATIVE MULTITASKING MODEL ↝ A SINGLE INTERRUPTIBLE RENDERING THREAD ↝ RENDERING CAN BE INTERLEAVED WITH OTHER MAIN THREAD TASKS AND OTHER REACT RENDERS ↝ AN UPDATE CAN HAPPEN IN THE BACKGROUND WITHOUT BLOCKING THE RESPONSE TO NEW INPUT SCHEDULING
77. ↓ ORIGINAL RENDER TASK USER INPUT → ↑ HIGHER PRIORITY RENDER TASK ↓ RESUME ORIGINAL RENDER TASK
78. ↝ IT YIELDS EXECUTION IS BACK TO THE MAIN THREAD EVERY 5MS ↝ IT'S SMALLER THAN A SINGLE FRAME EVEN ON 120FPS, SO IT WON'T BLOCK ANIMATIONS ↝ IN PRACTICE, RENDERING IS INTERRUPTIBLE SCHEDULING
79. PRIORITY LEVELS
80. PRIORITY LEVELS
81. PRIORITY TIMEOUT WHEN I m m ediate SYNCHRONOUSLY TASKS THAT NEED TO RUN SYNCHRONOUSLY UserBlocking 250MS RESULTS OF A USER INTERACTION (E.G. A BUTTON CLICK) Normal 5S UPDATES THAT DON’T HAVE TO FEEL INSTANTANEOUS Low 10S TASKS THAT CAN BE DEFERRED BUT MUST STILL COMPLETE EVENTUALLY (E.G. AN ANALYTICS NOTIFICATION) Idle NO TIMEOUT TASKS THAT DO NOT HAVE TO RUN AT ALL (E.G. HIDDEN OFFSCREEN CONTENT)
82. ↝ ONE LANE = ONE BIT IN A BITMASK ↝ ONE UPDATE IN REACT = ONE LANE ↝ ONE RENDER IN REACT = ONE OR MORE LANES ↝ UPDATES IN THE SAME LANE RENDER IN THE SAME BATCH. DIFFERENT LANES, SEPARATE BATCHES. RENDER LANES 🤯
83. ↝ 31 LEVELS OF GRANULARITY (= ONE BITMASK) ↝ ALLOWS TO CHOOSE WHETHER TO RENDER MULTIPLE TRANSITIONS IN A SINGLE BATCH OR RENDER THEM INDEPENDENTLY ↝ REDUCES OVERHEAD OF MULTIPLE LAYOUT PASSES, STYLE RECALCULATIONS, AND MULTIPLE PAINTS RENDER LANES 🤯
85. DEEP DIVING ON CONCURRENT REACT
86. #QUESTION 🤔 How do we benefit from these in our everyday projects?
87. Scheduling in React [for the rest of us] DEEP DIVING ON CONCURRENT REACT
88. #1 HANDLING LARGE SETS OF DATA DEEP DIVING ON CONCURRENT REACT
89. 😔 NON-PRACTICAL… ↝ FINDING PRIMES ↝ CRACKING PASSWORDS ↝ SIERPINSKI TRIANGLE
90. 😔 NON-PRACTICAL… ↝ RENDERING MANY DATA-POINTS ↝ RENDERING ON A <canvas> ↝ PROCESSING DATA
91. DAILY VISITORS (BEFORE)
92. DAILY VISITORS (BEFORE) const DailyVisitors = () = > { const [data, setData] = useState(initialData); useEffect(() = > { setData(initialData); }, []); const onChange = (newData) = > { setData(newData); }; return ( <Dashboard data={data} initialData={initialData} onChange={onChange} /> ); }; export default DailyVisitors;
93. DAILY VISITORS (AFTER) const DailyVisitors = () = > { const [data, setData] = useState(initialData); const [, startTransition] = useTransition(); useEffect(() = > { setData(initialData); }, []); const onChange = (newData) = > { startTransition(() = > { setData(newData); }); }; return ( <Dashboard data={data} initialData={initialData} onChange={onChange} /> ); }; export default DailyVisitors;
94. DAILY VISITORS (AFTER)
95. ↝ ˜100K + POINTS PLOTTED ↝ SUPPORT FOR SEARCHING AND FILTERING ↝ USED WORKERS + REDUX-SAGA UTILITIES + DEBOUNCING ↝ COULD'VE USED TRANSITIONS CASE #1: MAPS
96. CASE #2: GAME ADMIN ↝ THOUSANDS OF REAL-TIME PLAYERS MESSAGING ↝ SUPPORT FOR SEARCHING AND FILTERING ↝ USED VIRTUALIZATION AND MEMOIZATION ↝ COULD'VE USED TRANSITIONS
97. #2 TACKLING WASTED RENDERS DEEP DIVING ON CONCURRENT REACT
98. useSyncExternalStore() function useSyncExternalStore<Snapshot>( subscribe: (onStoreChange: () = > void) = > () = > void, getSnapshot: () = > Snapshot, getServerSnapshot?: () = > Snapshot ): Snapshot;
99. DEEP DIVING ON CONCURRENT REACT
100. DEEP DIVING ON CONCURRENT REACT
103. #QUESTION 🤔 How do we benefit from these in our everyday projects?
104. useLocation() function Pathname() { const { pathname } = useLocation(); return <Badge title={pathname} subtitle="pathname" />; } function Hash() { const { hash } = useLocation(); return <Badge title={hash} subtitle="hash" />; }
105. useLocation() function Pathname() { const { pathname } = useLocation(); return <Badge title={pathname} subtitle="pathname" />; } function Hash() { const { hash } = useLocation(); return <Badge title={hash} subtitle="hash" />; } OVER-RETURNING HOOK
107. useHistory() + useSyncExternalStore() function useHistorySelector(selector) { const history = useHistory(); return useSyncExternalStore(history.listen, () = > selector(history)); } function Pathname() { const pathname = useHistorySelector((history) = > history.location.pathname); return <Badge title={pathname} subtitle="pathname" />; } function Hash() { const hash = useHistorySelector((history) = > history.location.hash); return <Badge title={hash} subtitle="hash" />; }
108. function useHistorySelector(selector) { const history = useHistory(); return useSyncExternalStore(history.listen, () = > selector(history)); } function Pathname() { const pathname = useHistorySelector((history) = > history.location.pathname); return <Badge title={pathname} subtitle="pathname" />; } function Hash() { const hash = useHistorySelector((history) = > history.location.hash); return <Badge title={hash} subtitle="hash" />; } useHistory() + useSyncExternalStore()
110. #3 HYDRATION IMPROVEMENTS DEEP DIVING ON CONCURRENT REACT
111. ↝ BEFORE, HYDRATION COULD ONLY BEGIN AFTER THE ENTIRE DATA WAS FETCHED AND RENDERED ↝ USERS COULDN’T INTERACT WITH THE PAGE UNTIL HYDRATION WAS COMPLETE FOR THE WHOLE PAGE ↝ PARTS OF YOUR APP THAT LOAD FAST WOULD ALWAYS HAVE TO WAIT FOR THE SLOW ONES HYDRATION
112. SELECTIVE HYDRATION <Layout> <Article /> <Suspense fallback={<Spinner />}> <Co m m ents /> </Suspense> </Layout>
113. ↝ REACT WON'T WAIT FOR THAT COMPONENT TO LOAD TO CONTINUE STREAMING HTML FOR THE REST OF THE PAGE ↝ WHEN THE HTML BECOMES AVAILABLE ON THE SERVER, IT WILL BE ADDED TO THE SAME STREAM ALONG WITH A SCRIPT TAG AND INSERTED IN THE RIGHT PLACE SELECTIVE HYDRATION
114. ↝ REACT PRIORITIZES HYDRATING THE PARTS THAT THE USER INTERACTED WITH BEFORE THE REST ↝ COMPONENTS CAN BECOME INTERACTIVE FASTER BY ALLOWING THE BROWSER TO DO OTHER WORK AT THE SAME TIME AS HYDRATION ↝ RESULTS IN LOWER FID AND INP SELECTIVE HYDRATION
115. DEEP DIVING ON CONCURRENT REACT
116. #4 PROFILER ENHANCEMENTS DEEP DIVING ON CONCURRENT REACT
117. TRANSITIONS — INTRODUCING A NEW REACT PROFILER, BY BRIAN VAUGHN
118. — INTRODUCING A NEW REACT PROFILER, BY BRIAN VAUGHN BLOCKED RENDER
119. — INTRODUCING A NEW REACT PROFILER, BY BRIAN VAUGHN WARNS
120. Scheduling on the Web DEEP DIVING ON CONCURRENT REACT
121. WE HAVE A FEW SCHEDULING PRIMITIVES: ↝ setTimeout ↝ requestAnimationFrame ↝ requestIdleCallback ↝ postMessage SCHEDULING ON THE WEB
122. ↝ EVERYONE SHOULD USE THE SAME SCHEDULER ↝ HAVING MORE THAN ONE SCHEDULER CAUSES RESOURCE FIGHTING ↝ INTERLEAVING TASKS WITH BROWSER WORK (RENDERING, GARBAGE COLLECTION) SCHEDULING ON THE WEB
123. #RANT 😡 We need better and uniform scheduling primitives for the web!
124. DEEP DIVING ON CONCURRENT REACT
125. SCHEDULING API ↝ A MORE ROBUST SOLUTION FOR SCHEDULING TASKS ↝ INTEGRATED DIRECTLY INTO THE EVENT LOOP ↝ CONTROL AND SCHEDULE PRIORITIZED TASKS IN A UNITED AND FLEXIBLE WAY ↝ ALIGNED WITH THE WORK OF THE REACT TEAM AND IN COOPERATION WITH GOOGLE, W3C AND OTHERS
126. DEEP DIVING ON CONCURRENT REACT
127. scheduler.postTask() SCHEDULE AND CONTROL PRIORITIZING TASKS. scheduler.wait() YIELD AND RESUME AFTER SOME AMOUNT OF TIME OR PERHAPS AFTER AN EVENT HAS OCCURRED. scheduler.yield() BREAK UP LONG TASKS BY YIELDING TO THE BROWSER AND CONTINUING AFTER BEING RESCHEDULED. isInputPending() DETERMINE IF THE CURRENT TASK IS BLOCKING INPUT EVENTS. SCHEDULING API
128. scheduler.postTask() scheduler.postTask(() = > { console.log('React Brussels'); }, { delay: 10 }); scheduler.postTask(() = > { console.log('React India'); }); scheduler.postTask(() = > { console.log('React Alicante'); }); / / 'React India' 'React Alicante' 'React Brussels'
129. scheduler.postTask() const controller = new TaskController({ priority: "user-blocking" }); const signal = controller.signal; console.log(signal.priority); / / 'user-blocking' console.log(signal.aborted); / / 'false' scheduler.postTask(doWork, { signal }); controller.setPriority("background"); controller.abort();
130. isInputPending() while (workQueue.length > 0) { if (navigator.scheduling.isInputPending()) { / / Stop doing work to handle any input event break; } let job = workQueue.shift(); job.execute(); }
131. scheduler.yield() async function doWork() { while (true) { let hasMoreWork = doSomeWork(); if (!hasMoreWork) { return; } if (!navigator.scheduling.isInputPending()) { continue; } await scheduler.yield(); } } 🤯
132. SCHEDULING API
133. ↝ SCHEDULING IS AN ALTERNATIVE FOR RESPONSIVE USER INTERFACES ↝ A WEB STANDARDS PROPOSAL THAT BRINGS A UA SCHEDULER TO THE BROWSER IS BEING COOKED ↝ WE CAN SOLVE A LOT AT THE FRAMEWORK LEVEL WITH CONCURRENT REACT AND ITS SCHEDULER SCHEDULING (RECAP)
134. #NOSILVERBULLET 🔫 Code that yields too often can cause the overhead of scheduling tasks to become a negative influence on your app’s overall performance.
135. ↝ DETECTION AND SCHEDULING HAVE AN OVERHEAD ↝ NO CORRECT CHUNK SIZE THAT FITS ALL DEVICES ↝ PARTIALLY COMPLETE INTERFACES CAN INCREASE THE TOTAL COST OF LAYOUT AND PAINT ↝ HARD TO FIND THE RIGHT SPOT BETWEEN PERF AND AMOUNT OF BLOCKING SCHEDULING (BAD PARTS) 🤯
136. Measure DEEP DIVING ON CONCURRENT REACT
137. MEASURE IN THE LAB
138. MEASURE IN THE FIELD
139. #PROTIP 💡 Start with observability services or libraries like web-vitals. Then create your own abstractions on top of the web + React (e.g. custom hooks).
140. TIMING USER TIMING ALLOWS YOU TO MARK POINTS IN TIME AND THEN MEASURE THE DURATION BETWEEN THOSE MARKS. EVENT TIMING EVENT PROCESSING TIME + TIME UNTIL THE NEXT FRAME CAN BE RENDERED. THE BASIS FOR THE FID METRIC. ELEMENT TIMING MEASURE THE RENDER TIME OF SPECIFIC ELEMENTS. THE BASIS FOR THE LCP METRIC.
141. PROFILING LONG TASKS API REPORTS TASKS THAT TAKES LONGER THAN 50 MS AND IT'S THE BASIS FOR TTI AND TBT METRICS JS SELF-PROFILING API PROFILE SPECIFIC COMPLEX OPERATIONS AND IDENTIFY HOT SPOTS USING A SAMPLING PROFILER UserAgentSpecificMemory DETECT MEMORY LEAKS IN APPS THAT HANDLE A HUGE VOLUME OF DATA
142. { name: "same-origin-descendant", entryType: "longtask", startTime: 1023.40999995591, duration: 187.19000002602115, attribution: [ { name: "unknown", entryType: "taskattribution", startTime: 0, duration: 0, containerType: "iframe", containerSrc: "child.html", containerId: "", containerName: "child1" } ] } { bytes: 1000000, breakdown: [ { bytes: 1000000, attribution: [ { url: "https://example.com", scope: "Window", }, ], types: ["JS", "DOM"], }, { bytes: 0, attribution: [], types: [], }, ], } { "frames": [ { "name": "Profiler" }, { "column": 0, "line": 100, "name": "", "resourceId": 0 }, { "name": "set innerHTML" }, { "column": 10, "line": 10, "name": "A", "resourceId": 1 } { "column": 20, "line": 20, "name": "B", "resourceId": 1 } ], "resources": [ "https://example.com/page", "https://example.com/app.js", ], "samples": [ { "stackId": 0, "timestamp": 161.99500000476837 }, { "stackId": 2, "timestamp": 182.43499994277954 }, { "timestamp": 197.43499994277954 }, { "timestamp": 213.32999992370605 }, { "stackId": 3, "timestamp": 228.59999990463257 }, ], "stacks": [ { "frameId": 0 }, { "frameId": 2 }, { "frameId": 3 }, { "frameId": 4, "parentId": 2 } ] } LONG TASKS SELF-PROFILING USERAGENT MEMORY 🤯
143. The Future DEEP DIVING ON CONCURRENT REACT
144. ↝ I/O LIBRARIES LIKE react-fetch ↝ BUILT-IN <Cache> FOR DATA FETCHING LIBRARIES TO INTEGRATE WITH <Suspense> ↝ <Suspense> FOR CPU-BOUND TREES TO IMMEDIATELY FALLBACK WITHOUT EVEN TRYING TO RENDER THE FUTURE 🤯
145. ↝ useInsertionEffect FOR STYLESHEET LIBRARIES ↝ THE <Offscreen> COMPONENT ↝ SERVER COMPONENTS ↝ NATIVE SCHEDULING PRIMITIVES ON THE BROWSER ↝ AND MUCH MORE! THE FUTURE 🤯
146. Closing Notes DEEP DIVING ON CONCURRENT REACT
147. #1 DEEP DIVING ON CONCURRENT REACT REACT HAS BEEN PUSHING WEB APIS TO THE FUTURE E.G. THE SCHEDULER API AND DISCUSSIONS AROUND EFFECT HANDLERS
148. #2 DEEP DIVING ON CONCURRENT REACT REACT TRIES TO ADDRESS THE LACK OF SOME JS/WEB PLATFORM RESOURCES E.G. EFFECT HANDLERS, CONTINUATIONS & THE SCHEDULER API
149. #3 DEEP DIVING ON CONCURRENT REACT UNDERSTANDING THESE INTERNALS AND THEIR RATIONALES HELPS US IMPLEMENT OUR OWN ABSTRACTIONS E.G. THE GENERATOR-BASED SCHEDULER
150. #4 DEEP DIVING ON CONCURRENT REACT SCHEDULING DOES NOT NECESSARILY MEAN BETTER PERFORMANCE
151. #4 DEEP DIVING ON CONCURRENT REACT THERE'S NO SILVER BULLET. IDENTIFY YOUR CORE METRICS.
152. #5 DEEP DIVING ON CONCURRENT REACT THERE’S A LOT OF INFORMATION OUT THERE
154. #6 DEEP DIVING ON CONCURRENT REACT TRY TO CORRELATE BUSINESS METRICS WITH PERFORMANCE
155. We’re hiring! 🗺 Mostly in… 🇺🇸🇲🇽🇦🇷🇺🇾🇪🇸🇨🇿🇮🇱🇮🇳
156. 🤗 🇮🇳
157. DEEP DIVING ON CONCURRENT REACT
158. DEEP DIVING ON CONCURRENT REACT
159. THAT’S ALL, FOLKS! THANKS! QUESTIONS? MATHEUS ALBUQUERQUE