⚡ Bolt: Cache parsed verdicts in aggregation loops - #643
Conversation
…e overhead 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 | ad99b24 | Commit Preview URL Branch Preview URL |
Jul 23 2026, 05:23 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
agentic-inbox | ad99b24 | Jul 23 2026, 05:24 AM |
💡 What: Implemented a bounded
Mapcache forparseVerdictinworkers/lib/dashboard-aggregation.ts, and reused it insideparseVerdictAction.🎯 Why:
parseVerdictis called repeatedly inside loop iterations during threat data aggregation. Caching the parsed result significantly reduces CPU time and object allocation overhead. We freeze the parsed result to prevent shared object reference mutation bugs downstream.📊 Impact: Reduces CPU time spent in aggregation loops doing redundant JSON parsing, accelerating org and domain-wide dashboard loading.
🔬 Measurement: Verify dashboard loads correctly and review CPU usage/time profiling on the DO during heavy aggregations.
PR created automatically by Jules for task 2900388801002033628 started by @schmug