⚡ Bolt: Concurrent email sending via Promise.all - #82
Conversation
Replaced sequential await calls for Resend emails with Promise.all to reduce accumulated network latency in the 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. |
1 participant
What: Modified the Resend email sending logic in the Cloudflare Worker to use Promise.all for sending the notification and auto-reply emails concurrently instead of sequentially.
Why: Sequential network requests in a Cloudflare Worker accumulate latency and increase the overall execution time of the worker.
Impact: Reduces the worker execution time by performing independent network requests in parallel.
Measurement: Compare the execution time of the worker before and after the change using the Cloudflare dashboard or Wrangler tail.
PR created automatically by Jules for task 17773400357878648787 started by @Snigdh41