⚡ Bolt: [performance improvement] Optimize React re-renders in LogPanel and ProgressPanel#139
⚡ Bolt: [performance improvement] Optimize React re-renders in LogPanel and ProgressPanel#139primoscope wants to merge 1 commit intomainfrom
Conversation
…el and ProgressPanel What: Extracted `LogItem` and `DownloadItem` into separate components wrapped in `React.memo()`. Implemented custom equality functions and stable client-side IDs to prevent O(N) re-renders. Moved static helper functions outside the component bodies. Why: High-frequency WebSocket events updating the logs or active downloads lists caused the entire `LogPanel` or `ProgressPanel` array to re-render continuously, which becomes a major performance bottleneck as the lists grow larger. Impact: Drastically reduces React reconciliation overhead and CPU usage during active downloads. For example, if there are 100 logs and 10 logs arrive per second, React now only renders the 10 new items instead of 1000 items per second. Measurement: Visually verify that the progress bar and log stream still function correctly while downloading a file, or profile the frontend in React DevTools to observe zero re-renders on stable child list elements. Co-authored-by: dzp5103 <214723817+dzp5103@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:
Extracted
LogItemandDownloadIteminto separate components wrapped inReact.memo(). Implemented custom equality functions and stable client-side IDs to prevent O(N) re-renders. Moved static helper functions outside the component bodies.🎯 Why:
High-frequency WebSocket events updating the logs or active downloads lists caused the entire
LogPanelorProgressPanelarray to re-render continuously, which becomes a major performance bottleneck as the lists grow larger.📊 Impact:
Drastically reduces React reconciliation overhead and CPU usage during active downloads. For example, if there are 100 logs and 10 logs arrive per second, React now only renders the 10 new items instead of 1000 items per second.
🔬 Measurement:
Visually verify that the progress bar and log stream still function correctly while downloading a file, or profile the frontend in React DevTools to observe zero re-renders on stable child list elements.
PR created automatically by Jules for task 16994686465029784139 started by @dzp5103