Skip to content

⚡ Bolt: [performance improvement] Run admin stats DB queries concurrently - #105

Open
secrooq wants to merge 1 commit into
mainfrom
bolt-admin-stats-concurrent-4703027897686924692
Open

⚡ Bolt: [performance improvement] Run admin stats DB queries concurrently#105
secrooq wants to merge 1 commit into
mainfrom
bolt-admin-stats-concurrent-4703027897686924692

Conversation

@secrooq

@secrooq secrooq commented Jul 1, 2026

Copy link
Copy Markdown
Owner

💡 What:
Changed the admin/stats endpoint in /api/admin/[[...slug]]/route.ts to execute four separate database queries (fileStats, emailStats, userStats, and secretStats) concurrently using Promise.all.

🎯 Why:
In serverless environments like Cloudflare D1, making sequential db.prepare(...).first() calls creates an N+1 network latency bottleneck, as each statement requires a discrete HTTP request. Running independent queries concurrently significantly reduces the overall response time for the admin stats endpoint. Following the guidelines in .jules/bolt.md, we preserve independent query fault-tolerance by attaching .catch() handlers to each individual .first() promise before aggregating them with Promise.all().

📊 Impact:
Reduces database roundtrips from four sequential waits to one concurrent wait, decreasing total network latency by ~75% for this database-intensive endpoint.

🔬 Measurement:
Verify by observing reduced latency on the /api/admin/stats endpoint when logged in as an admin in the browser DevTools network tab, or using standard HTTP benchmarking against the admin stats route.


PR created automatically by Jules for task 4703027897686924692 started by @secrooq

Run the `fileStats`, `emailStats`, `userStats`, and `secretStats` database queries in `/api/admin/[[...slug]]/route.ts` concurrently using `Promise.all([ ... ])` instead of executing them sequentially with `try...catch` blocks.
This solves the N+1 network latency bottleneck for Cloudflare D1 and other serverless SQL environments while preserving fault tolerance for independent queries (each `.first()` catches its own error).

Co-authored-by: secrooq <81346684+secrooq@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