⚡ Bolt: Execute independent network requests concurrently#39
Conversation
In the Contact API worker, the `resend.emails.send` calls for the notification and auto-reply emails were executed sequentially. This meant the worker had to wait for the first network request to complete before starting the second, unnecessarily accumulating latency. By wrapping both requests in `Promise.all()`, they now execute concurrently. This significantly reduces the worker's overall execution time, providing a faster response to the client without modifying any underlying behavior. 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: Refactored the email sending logic in the Contact API worker (
workers/contact-api/src/index.js) to usePromise.all()for executing the notification and auto-reply email requests concurrently instead of sequentially.🎯 Why: Sequential execution of independent external API calls accumulates latency. Waiting for the first email to send before starting the second delays the worker's final response to the client.
📊 Impact: Reduces the time spent on network requests during the contact form submission by roughly half, leading to a faster response time for the user and shorter execution time for the worker.
🔬 Measurement: Can be verified by timing the response of the
/contactendpoint before and after the change; the time spent waiting for theresend.emails.sendcalls will be bound by the slowest request rather than the sum of both.PR created automatically by Jules for task 5601232288986507718 started by @Snigdh41