⚡ Bolt: Extract TrafficRow to memoized component to avoid unnecessary re-renders#56
⚡ Bolt: Extract TrafficRow to memoized component to avoid unnecessary re-renders#56zaydiscold wants to merge 1 commit into
Conversation
… re-renders Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: The inline row rendering for the proxy traffic log array has been extracted into a new
<TrafficRow />component, wrapped withReact.memo().🎯 Why: The traffic dashboard automatically polls for new logs every 30 seconds using
useVisibleRecurringTask. On every refresh, all 100 recent rows were re-evaluated and re-rendered entirely, running relatively expensive computations likedescribeRouteand timestamp conversion string operations again, even though 99% of the log history had not changed since the last fetch. This consumed extra CPU and janked the main thread.📊 Impact: Reduces array-item rendering overhead for historical log rows by up to ~99% on dashboard polls.
🔬 Measurement: Observe the "Traffic Console" page during polling updates using React DevTools Profiler; unchanged log rows now bypass rendering entirely.
PR created automatically by Jules for task 6517391258905262556 started by @zaydiscold