Skip to content

⚡ Bolt: Eliminate LINQ and debug log allocations in hot path#34

Open
lordhippo wants to merge 3 commits into
mainfrom
bolt-optimize-linq-allocations-10326074954020290042
Open

⚡ Bolt: Eliminate LINQ and debug log allocations in hot path#34
lordhippo wants to merge 3 commits into
mainfrom
bolt-optimize-linq-allocations-10326074954020290042

Conversation

@lordhippo

Copy link
Copy Markdown
Member

💡 What:

  • Removed LINQ .Where() and .ToList() usage in the per-frame loops of TeamRunner, Ai, and Knowledge.AttackerDecision.
  • Gated expensive debug logging inside TeamRunner behind if (Log.IsEnabled(LogLevel.Debug)).
  • Documented findings regarding ZLogDebug parameter evaluation in .jules/bolt.md.

🎯 Why:

  • LINQ operations create enumerators and closure allocations (when capturing class state or local variables). Doing this in a 100Hz loop creates immense, steady garbage generation, resulting in GC pauses which must be avoided for real-time robotic operations.
  • Using string interpolations with .Select() or string.Join inside a log call results in heap allocations that happen before the logger's internal log level is evaluated. When Debug logs are disabled, these thousands of allocations are purely wasted compute and garbage.

📊 Impact:

  • Eliminates 3 primary per-frame LINQ closure/enumerator allocations.
  • Eliminates thousands of per-second string array and closure allocations when debug logging is disabled in TeamRunner.

🔬 Measurement:
dotnet-counters monitor -p <PID> --counters System.Runtime[gen-0-gc-count,alloc-rate]


PR created automatically by Jules for task 10326074954020290042 started by @lordhippo

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

Copy link
Copy Markdown

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

google-labs-jules Bot and others added 2 commits May 28, 2026 02:11
Co-authored-by: lordhippo <5122916+lordhippo@users.noreply.github.com>
Co-authored-by: lordhippo <5122916+lordhippo@users.noreply.github.com>
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