Skip to content

⚡ Bolt: Remove LINQ ToDictionary allocations on hot paths#310

Open
google-labs-jules[bot] wants to merge 1 commit into
masterfrom
perf/remove-to-dictionary-allocations-6166298327440255012
Open

⚡ Bolt: Remove LINQ ToDictionary allocations on hot paths#310
google-labs-jules[bot] wants to merge 1 commit into
masterfrom
perf/remove-to-dictionary-allocations-6166298327440255012

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor

💡 What: Replaced numerous high-overhead LINQ allocations (.ToDictionary(), .GroupBy(), .Where(), etc.) with manual looping and pre-sized dictionaries in NetworkSimulationEngine.cs, TemporalNetworkSimulationEngine.cs, and MixedRouting.cs.

🎯 Why: In high-frequency hot paths like routing simulations, chaining LINQ .ToDictionary() forces the CLR to allocate delegates, closures, intermediate sequences, and dictionary wrappers. This generates massive garbage collection pressure. Pre-sizing and manually populating standard loops entirely eliminates this overhead.

📊 Impact: Reduces memory allocations during network simulation iterations and improves overall throughput.

🔬 Measurement: Verified functionality is identical by successfully running the MedWNetworkSim test suite. Tests pass without regressions.


PR created automatically by Jules for task 6166298327440255012 started by @wnj00524

@google-labs-jules

Copy link
Copy Markdown
Contributor Author

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

0 participants