⚡ Bolt: [performance improvement] Concurrent admin stats queries - #108
⚡ Bolt: [performance improvement] Concurrent admin stats queries#108secrooq wants to merge 1 commit into
Conversation
Refactored the sequential `db.prepare(...).first()` database queries in the `src/app/api/admin/[[...slug]]/route.ts` `stats` endpoint to execute concurrently using `Promise.all`. This reduces the N+1 network latency bottleneck on the admin dashboard while maintaining the exact same fault tolerance using individual `catch()` handlers for each promise. Co-authored-by: secrooq <81346684+secrooq@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. |
1 participant
💡 What:
Refactored the sequential database queries (
vault_files,relay_aliases,vault_users,stealth_secrets) in thesubPath === 'stats'route of the admin dashboard to run concurrently usingPromise.all. Included code comments explaining the optimization. Removed the unintentional changes topnpm-lock.yaml.🎯 Why:
In a serverless environment like Cloudflare Pages running D1 SQLite, each database call adds network roundtrip overhead. Sequential queries cause a noticeable N+1 latency bottleneck.
📊 Impact:
Reduces total database latency on the admin stats endpoint from the sum of all 4 query times down to the duration of the single slowest query, making the dashboard feel significantly snappier. Fault tolerance is maintained by appending
.catch()to each individual promise, preventing failure cascading.🔬 Measurement:
The optimization can be verified by checking the Next.js API route execution times or network panel latency when fetching the
/api/admin/statsdashboard route. Tests pass natively.PR created automatically by Jules for task 935678895802271750 started by @secrooq