⚡ Bolt: Concurrent API requests in Cloudflare Worker - #86
Conversation
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: Replaced sequential
resend.emails.sendAPI calls with a concurrent execution usingPromise.all().🎯 Why: Sequential external API calls accumulate latency, significantly increasing the total execution time of the Cloudflare Worker. Concurrent execution minimizes the wait time.
📊 Impact: Reduces the total latency of email sending by approximately 50%, resulting in a faster response to the client.
🔬 Measurement: Check the execution time of the
/contactendpoint before and after the change; the total time spent waiting for the Resend API will be roughly equal to the slower of the two requests, rather than the sum of both.PR created automatically by Jules for task 9386434685312891706 started by @Snigdh41