Skip to content

⚡ Bolt: Optimize CodeBlock render performance - #318

Closed
bobdivx wants to merge 1 commit into
mainfrom
bolt-optimize-codeblock-render-11215662265803833455
Closed

bobdivx wants to merge 1 commit into
mainfrom
bolt-optimize-codeblock-render-11215662265803833455

Conversation

@bobdivx

@bobdivx bobdivx commented Nov 10, 2026

Copy link
Copy Markdown
Owner

💡 What: Optimized the derived shown state calculation in CodeBlock.tsx by replacing nested .map().join('') calls with a useMemo block containing a manual for loop string concatenation.
🎯 Why: Code snippet flatten operations were being re-computed on every render (such as hovering or clicking the "Copy" button). For large code blocks, creating intermediate arrays via map chains leads to unnecessary CPU time and memory allocation overhead.
📊 Impact: Reduces unneeded intermediate array allocations and overhead when interacting with the UI. String concatenation via standard loops scales better over numerous tokens.
🔬 Measurement: Verify tests run successfully using pnpm run test:web and interactions inside chat codebase snippets remain functionally identical with copy buttons performing normally.


PR created automatically by Jules for task 11215662265803833455 started by @bobdivx

Replaces nested .map().join() array methods with useMemo and manual string concatenation loops inside CodeBlock's `shown` state calculation to reduce unnecessary allocations on a hot path.

Co-authored-by: bobdivx <6737167+bobdivx@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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.

@bobdivx

bobdivx commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

Closing: same CodeBlock micro-optimization already proposed and closed several times (#311, #309, #306, #303, #296, #295, #287). No measurable gain on realistic code block sizes, not worth the extra code.

@bobdivx bobdivx closed this Nov 10, 2026
@google-labs-jules

Copy link
Copy Markdown
Contributor

Closing: same CodeBlock micro-optimization already proposed and closed several times (#311, #309, #306, #303, #296, #295, #287). No measurable gain on realistic code block sizes, not worth the extra code.

Understood. Acknowledging that this work is now obsolete and stopping work on this task. I have recorded this rejection in .jules/bolt.md to avoid repeating this micro-optimization attempt in the future.

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