Skip to content

⚡ Bolt: [performance improvement] Execute independent async operations concurrently using Promise.all in getStats#199

Draft
yeboster wants to merge 1 commit intomainfrom
bolt-performance-promise-all-getstats-10071226063095734124
Draft

⚡ Bolt: [performance improvement] Execute independent async operations concurrently using Promise.all in getStats#199
yeboster wants to merge 1 commit intomainfrom
bolt-performance-promise-all-getstats-10071226063095734124

Conversation

@yeboster
Copy link
Copy Markdown
Contributor

💡 What: Replaced sequential awaits with a concurrent Promise.all in src/lib/server/index.ts getStats method to resolve the waterfall problem.

🎯 Why: The previous implementation sequentially awaited metaNamesSdk.domainRepository.count(), getOwners(), and getRecentDomains(), artificially blocking subsequent independent network requests and adding unnecessary round trip latency.

📊 Impact: Significantly reduces the total latency and execution time for the getStats function by executing all independent blockchain and repository data retrieval calls concurrently.

🔬 Measurement: Verify locally or synthetically monitor API request latency resolving /api/stats endpoint, checking if time to resolve drops relative to sequential wait.

No architectural changes made and code readability is preserved. Tested with the project's internal commands successfully (pnpm test:unit --run and pnpm run check).


PR created automatically by Jules for task 10071226063095734124 started by @yeboster

…se.all in getStats

Co-authored-by: yeboster <23556525+yeboster@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.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Ready Ready Preview, Comment Mar 24, 2026 8:39pm

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