Skip to content

⚡ Bolt: Optimize ProcessMemoryScanner concurrency with sliding window#86

Open
acebytes wants to merge 1 commit intomainfrom
bolt/process-scanner-sliding-window-979445314900776575
Open

⚡ Bolt: Optimize ProcessMemoryScanner concurrency with sliding window#86
acebytes wants to merge 1 commit intomainfrom
bolt/process-scanner-sliding-window-979445314900776575

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

@acebytes acebytes commented Apr 5, 2026

💡 What:
Replaced the static array chunking in ProcessMemoryScanner.scanPIDs with an iterator-based sliding window approach inside withTaskGroup.

🎯 Why:
Static chunking limits throughput due to tail latency — the system has to wait for the slowest task in a chunk to finish before starting the next batch of tasks. A sliding window with an iterator maintains maximum concurrent execution limits continuously, keeping all worker "slots" full as long as there are PIDs left to scan.

📊 Impact:
Improves the throughput of process memory scanning by avoiding idle waiting. This reduces the overall time taken to scan all PIDs, especially when scanning hundreds of processes with varying completion times.

🔬 Measurement:
Run the app and observe the process scanning speed. The difference is most notable on systems with many running processes.


PR created automatically by Jules for task 979445314900776575 started by @acebytes

In `scanPIDs`, replace static array chunking with a continuous iterator-based
sliding window inside `withTaskGroup`.

This avoids tail-latency waiting where the system idles waiting for the slowest
task in a chunk to finish before starting the next chunk, maximizing throughput
when scanning hundreds of PIDs concurrently.

Co-authored-by: acebytes <2820910+acebytes@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