Skip to content

⚡ Bolt: [performance improvement] CodeBlock string check useMemo - #303

Closed
bobdivx wants to merge 1 commit into
mainfrom
bolt-codeblock-usememo-optimization-3398544948507842715
Closed

bobdivx wants to merge 1 commit into
mainfrom
bolt-codeblock-usememo-optimization-3398544948507842715

Conversation

@bobdivx

@bobdivx bobdivx commented Nov 3, 2026

Copy link
Copy Markdown
Owner

💡 What: Wrapped the highlighted tokens check against the raw string code with useMemo, utilizing a manual for loop for string concatenation instead of nested .map().join().
🎯 Why: CodeBlock component derived state caused an expensive nested .map().join() execution on every render checking whether tokens matched the source code.
📊 Impact: Prevents CPU/Memory overhead incurred by allocations for intermediate arrays during frequent component renders.
🔬 Measurement: Verify via React Profiler that CodeBlock components are not recalculating string concatenations dynamically on every render round.


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

💡 What: Wrapped the highlighted tokens check against the raw string code with `useMemo`, utilizing a manual `for` loop for string concatenation instead of nested `.map().join()`.
🎯 Why: `CodeBlock` component derived state caused an expensive nested `.map().join()` execution on every render checking whether tokens matched the source code.
📊 Impact: Prevents CPU/Memory overhead incurred by allocations for intermediate arrays during frequent component renders.
🔬 Measurement: Verify via React Profiler that `CodeBlock` components are not recalculating string concatenations dynamically on every render round.

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 3, 2026

Copy link
Copy Markdown
Owner Author

Closing: wrapping the CodeBlock token comparison in useMemo and replacing .map().join() with a manual loop is a micro-optimization with no measurable gain; the same changes were already declined in #296, #295, and #287.

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

Copy link
Copy Markdown
Contributor

Closing: wrapping the CodeBlock token comparison in useMemo and replacing .map().join() with a manual loop is a micro-optimization with no measurable gain; the same changes were already declined in #296, #295, and #287.

Understood. Acknowledging that this work is now obsolete and stopping work on 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