Skip to content

⚡ Bolt: [performance improvement] Optimize WebSocket list rendering#133

Draft
primoscope wants to merge 1 commit intomainfrom
bolt-optimize-react-renders-16733582474175324606
Draft

⚡ Bolt: [performance improvement] Optimize WebSocket list rendering#133
primoscope wants to merge 1 commit intomainfrom
bolt-optimize-react-renders-16733582474175324606

Conversation

@primoscope
Copy link
Copy Markdown
Owner

💡 What: Optimized list rendering in ProgressPanel.tsx and LogPanel.tsx by using React.memo and extracting static functions.
🎯 Why: When high-frequency WebSocket updates arrived (e.g. download_speed or progress ticks, or rapidly streaming logs), the entire list of items re-rendered. For logs, relying on array indices as keys caused full unmount/remount cycles.
📊 Impact: Reduces O(N) full-list re-renders to O(1) single-item updates. Only the specific DownloadItem whose primitive data has changed will re-render.
🔬 Measurement: Verified visually with Playwright. Can also be measured via React DevTools Profiler by observing render times during active downloading.


PR created automatically by Jules for task 16733582474175324606 started by @dzp5103

Extracted static utility functions out of component bodies in LogPanel and ProgressPanel to avoid reallocation on every render.
Wrapped LogItem and DownloadItem list elements in React.memo() to prevent O(N) re-renders during high-frequency WebSocket tick updates.
Added client-generated stable IDs to log messages to use as React keys rather than array indices.

Co-authored-by: dzp5103 <214723817+dzp5103@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant