Skip to content

⚡ Bolt: Remove chained array methods before Set initialization - #152

Draft
toreleon wants to merge 1 commit into
masterfrom
bolt/optimize-set-initialization-12352175224859765482
Draft

toreleon wants to merge 1 commit into
masterfrom
bolt/optimize-set-initialization-12352175224859765482

Conversation

@toreleon

Copy link
Copy Markdown
Owner

💡 What: Replaced chained .map().filter() array operations with direct, indexed for loops when populating Set structures in normalizeTickers and getListedEquityTickers.

🎯 Why: Chaining array methods like .map() and .filter() before passing the result to new Set() creates multiple intermediate arrays. In hot paths (like scanning thousands of company profiles or normalizing tickers during discovery sweeps), this causes unnecessary memory allocation and garbage collection (GC) overhead.

📊 Impact: Reduces transient memory allocations (removes O(N) intermediate array allocations) during ticker normalization and listed equity resolution, lowering GC pauses without altering logic.

🔬 Measurement: Verify tests still pass via pnpm test. The changes are constrained strictly to internal data transformation flows and have no side-effects.


PR created automatically by Jules for task 12352175224859765482 started by @toreleon

- Replaced chained `.map().filter()` with direct `for` loops inside `normalizeTickers` (`src/tools/discover.ts`) and `getListedEquityTickers` (`src/data/sources/vndirectFinfo.ts`).
- Avoids multiple intermediate array allocations and reduces garbage collection pressure when constructing Sets in these frequently called discovery paths.

Co-authored-by: toreleon <42534763+toreleon@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.

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