Skip to content

⚡ Bolt: [performance improvement] Optimize computeBlockSummaryStats#48

Open
Howchie wants to merge 1 commit intomainfrom
bolt-performance-block-summary-12757949840353908432
Open

⚡ Bolt: [performance improvement] Optimize computeBlockSummaryStats#48
Howchie wants to merge 1 commit intomainfrom
bolt-performance-block-summary-12757949840353908432

Conversation

@Howchie
Copy link
Owner

@Howchie Howchie commented Mar 19, 2026

💡 What: Optimized the computeBlockSummaryStats function in packages/core/src/runtime/blockSummary.ts. Replaced Array.prototype.filter and subsequent loop with a single for loop to eliminate intermediate array allocations. Also hoisted the call to Object.entries(where) outside the loop so it's only executed once per function call, instead of once per trial result.

🎯 Why: The previous implementation performed multiple O(N) array allocations and executed expensive Object/Array methods (Object.entries, Array.isArray, Array.prototype.some) on every single iteration inside the filter callback, causing unnecessary CPU and memory overhead when analyzing large trial result arrays.

📊 Impact: Achieves a ~4.5x improvement in execution speed (from ~1.89ms down to ~0.4ms for 10,000 trials in local benchmarks) and significantly reduces memory allocation overhead.

🔬 Measurement: The performance improvement was measured using a custom tinybench script simulating 10,000 trial results with a where condition, comparing the execution time of the original implementation versus the single-pass implementation. The logic has also been verified against existing unit tests in @experiments/core.


PR created automatically by Jules for task 12757949840353908432 started by @Howchie

@google-labs-jules
Copy link
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.

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