⚡ Bolt: [performance improvement] Concurrent email sending via Promise.all#87
⚡ Bolt: [performance improvement] Concurrent email sending via Promise.all#87Snigdh41 wants to merge 1 commit into
Conversation
…e.all 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 Resend email API calls in the contact worker to execute concurrently using
Promise.all()instead of sequentially.Why: Sequential external HTTP requests in Cloudflare Workers block execution and accumulate latency. Since the notification email and auto-reply email are independent, they can be sent at the same time.
Impact: Reduces the external API latency overhead by ~50%, leading to a significantly faster overall worker response time for the user submitting the form.
Measurement: Measure the total execution time of the
/contactAPI endpoint before and after the change; expect the duration of the email-sending phase to roughly halve.PR created automatically by Jules for task 16726752673921251666 started by @Snigdh41