Skip to content

⚡ Bolt: Optimize N+1 query overhead in thread context fetching - #646

Open
schmug wants to merge 1 commit into
mainfrom
bolt/optimize-agent-thread-fetch-10846597497934220950
Open

⚡ Bolt: Optimize N+1 query overhead in thread context fetching#646
schmug wants to merge 1 commit into
mainfrom
bolt/optimize-agent-thread-fetch-10846597497934220950

Conversation

@schmug

@schmug schmug commented Jul 24, 2026

Copy link
Copy Markdown
Owner

💡 What: Replaced the Promise.all(map(...)) N+1 querying approach in workers/agent/index.ts with a direct call to getFullThread, which fetches all messages for a thread in a single D1 roundtrip.

🎯 Why: To significantly reduce processing latency when validating long context threads for agent AI prompts (like prompt injection checks and context assembly).

📊 Impact: N+1 queries replaced with a single DO trip. Reduces compute cycles and latency overhead relative to thread size length.

🔬 Measurement: Code execution verification over threads. All tests passing.


PR created automatically by Jules for task 10846597497934220950 started by @schmug

Replaced the sequential loop using `Promise.all(threadEmails.map(...))` to fetch each thread message individually via `stub.getEmail` with a single DO batch call to `getFullThread(stub, emailData.threadId)`. This eliminates N+1 query latency for large threads checked against prompt injections.

Co-authored-by: schmug <38227427+schmug@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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 24, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
agentic-inbox beee702 Jul 24 2026, 05:28 AM

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 24, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ais-hub beee702 Commit Preview URL

Branch Preview URL
Jul 24 2026, 05:27 AM

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