⚡ Bolt: [performance improvement] Concurrent email sending - #88
Conversation
Replaced sequential Resend API calls with a concurrent `Promise.all` approach to drastically reduce the execution time of the contact API 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: Refactored the
contact-apiworker to send the notification and auto-reply emails concurrently usingPromise.all(), rather than waiting for one to finish before starting the other.🎯 Why: The worker was previously making two sequential external HTTP requests to the Resend API. External requests are the primary source of latency in a Cloudflare Worker. By making these requests sequential, we were artificially doubling the wait time and unnecessarily keeping the worker alive longer than needed.
📊 Impact: Reduces the total execution time of the email-sending portion of the worker by roughly 50% (dependent on Resend API latency).
🔬 Measurement: In the Cloudflare dashboard, the execution duration metrics for the
/contactroute will show a marked decrease. You can also visually see that the "Auto-reply result" and "Notification result" logs arrive simultaneously rather than staggered.PR created automatically by Jules for task 4417399727005526533 started by @Snigdh41