⚡ Bolt: Run email sending concurrently - #102
Conversation
Updated the contact-api worker to execute the notification and auto-reply email requests concurrently using `Promise.all` to reduce overall execution time. 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 contact-api worker to send the notification email and the auto-reply email concurrently using
Promise.all.🎯 Why: The previous implementation awaited the external API requests sequentially. Since the requests are independent, running them concurrently avoids accumulating their individual latencies, reducing the total time the worker spends waiting for external services.
📊 Impact: Expected to reduce the total execution time of the email sending phase by roughly half (assuming both requests take similar time), resulting in a faster response to the client.
🔬 Measurement: Compare the latency of the
/contactAPI endpoint before and after the change; observing worker execution times in Cloudflare dashboard logs should show a reduction in total duration.PR created automatically by Jules for task 8709793144682144678 started by @Snigdh41