⚡ Bolt: [performance improvement] Execute external API requests concurrently in Cloudflare Worker - #99
Conversation
…rrently in Cloudflare Worker Co-authored-by: Snigdh41 <43762408+Snigdh41@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. |
💡 What: Updated the Cloudflare Worker to execute the independent
resend.emails.sendrequests (notification and auto-reply) concurrently usingPromise.all().🎯 Why: Previously, the auto-reply email request would wait for the notification email request to finish before starting. Since these requests are independent, executing them sequentially accumulates unnecessary latency.
📊 Impact: Reduces the overall API response time for contact submissions by approximately the time it takes to execute the second API request (~50% reduction in email dispatch latency).
🔬 Measurement: Compare the overall response time of the
/contactendpoint before and after the change using network profiling or server logs. The overall duration will drop fromt(notif) + t(reply)tomax(t(notif), t(reply)).PR created automatically by Jules for task 4585680858832166439 started by @Snigdh41