⚡ Bolt: Prevent N+1 query bottlenecks when retrieving email threads - #660
⚡ Bolt: Prevent N+1 query bottlenecks when retrieving email threads#660schmug wants to merge 1 commit into
Conversation
Co-authored-by: schmug <38227427+schmug@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ais-hub | d2c7380 | Commit Preview URL Branch Preview URL |
Jul 29 2026, 05:22 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
agentic-inbox | d2c7380 | Jul 29 2026, 05:23 AM |
💡 What: Replaced sequential
stub.getEmailcalls within aPromise.allmapping with a single call togetFullThread(stub, emailData.threadId).🎯 Why:
Promise.all(stub.getEmail)resulted in an N+1 query problem, making a network/stub roundtrip for each individual email within a thread inworkers/agent/index.ts.getFullThreadleverages the Durable Object's backend database to run a batched query, fetching the entire thread much more efficiently. It also handles mappingbody_textand sorting chronologically natively.📊 Impact: Eliminates N network/RPC calls and changes thread loading from O(N) database operations to O(1) in the DO context, yielding a substantial speedup when initializing AI email agents on large threads.
🔬 Measurement: Verify by executing
npm run test -- tests/agent/to ensure agent thread fetching still functions flawlessly and by validating that the agent generates accurate thread contexts with the new implementation.PR created automatically by Jules for task 932911303028395440 started by @schmug