Async email sending in Flask - Performance & Optimization

Performance: Async email sending

HIGH IMPACT

This affects the page load speed and user interaction responsiveness by offloading email sending to a background task.

Sending an email after a user submits a form

Flask

from flask import Flask, request
from flask_mail import Mail, Message
from threading import Thread

app = Flask(__name__)
mail = Mail(app)

def send_async_email(app, msg):
    with app.app_context():
        mail.send(msg)

@app.route('/submit', methods=['POST'])
def submit():
    msg = Message('Hello', recipients=[request.form['email']])
    msg.body = 'Thanks for signing up!'
    Thread(target=send_async_email, args=(app, msg)).start()  # async call
    return 'Email sending started!'

Email sending runs in a separate thread, so the HTTP response returns immediately without waiting for the email to send.

📈 Performance GainNon-blocking request, improves INP by reducing user wait time by 500ms+

Sending an email after a user submits a form

Flask

from flask import Flask, request
from flask_mail import Mail, Message

app = Flask(__name__)
mail = Mail(app)

@app.route('/submit', methods=['POST'])
def submit():
    msg = Message('Hello', recipients=[request.form['email']])
    msg.body = 'Thanks for signing up!'
    mail.send(msg)  # synchronous call
    return 'Email sent!'

The mail.send() call blocks the request until the email is sent, causing slow response times and poor user experience.

📉 Performance CostBlocks rendering and response for 500ms+ depending on email server latency

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous email sending	N/A	Blocks server response	Delays first paint and interaction	[X] Bad
Async email sending with thread	N/A	Non-blocking	Faster first paint and interaction	[OK] Good

Rendering Pipeline

Synchronous email sending blocks the server response, delaying the browser's ability to render or respond to user input. Async sending moves email operations off the main request thread, allowing the server to respond faster and the browser to paint sooner.

→Server Response

→Interaction to Next Paint (INP)

⚠️ BottleneckServer blocking during email send delays response and user interaction readiness

Core Web Vital Affected

INP

This affects the page load speed and user interaction responsiveness by offloading email sending to a background task.

Optimization Tips

1Never send emails synchronously in the main request thread to avoid blocking user interactions.

2Use background threads or task queues to handle email sending asynchronously.

3Check performance profiles to ensure no long blocking tasks delay server responses.

Performance Quiz - 3 Questions

What is the main performance benefit of sending emails asynchronously in Flask?

A It makes the email send faster on the mail server.

B It prevents blocking the HTTP response, improving user interaction speed.

C It reduces the size of the email content.

D It improves the email delivery success rate.

DevTools: Performance

How to check: Record a performance profile while submitting the form. Look for long tasks blocking the main thread during the request.

What to look for: Long blocking tasks indicate synchronous email sending; absence of blocking shows async sending.

Practice

1. What is the main benefit of sending emails asynchronously in a Flask app?

easy

A. Emails are sent faster than synchronous sending

B. It automatically retries sending emails on failure

C. The app remains responsive and does not wait for the email to send

D. It encrypts emails for security

Solution

1. Step 1: Understand synchronous vs asynchronous sending

   Synchronous sending blocks the app until the email is sent, causing delays.

2. Step 2: Identify async sending advantage

   Async sending lets the app continue running while the email sends in the background.

3. Final Answer:

   The app remains responsive and does not wait for the email to send -> Option C

4. Quick Check:

   Async sending = app stays responsive [OK]

Hint: Async means non-blocking, so app stays fast [OK]

Common Mistakes:

• Thinking async sends emails faster
• Assuming async retries automatically
• Confusing async with encryption

2. Which of the following is the correct way to start a new thread for async email sending in Flask?

easy

A. threading.Thread(send_email()).start()

B. threading.Thread(target=send_email).start()

C. threading.Thread(target=send_email())

D. threading.Thread(send_email).run()

Solution

1. Step 1: Identify correct threading syntax

   The target argument must be the function name without calling it (no parentheses).

2. Step 2: Check method to start thread

   Use .start() to run the thread asynchronously, not .run().

3. Final Answer:

   threading.Thread(target=send_email).start() -> Option B

4. Quick Check:

   Use target=function and call .start() [OK]

Hint: Pass function name to target, call .start() to run thread [OK]

Common Mistakes:

• Calling the function inside target argument
• Using .run() instead of .start()
• Missing target keyword

3. Given this Flask async email code snippet, what will be printed?

from threading import Thread
from flask import Flask, current_app
app = Flask(__name__)

def send_async_email(app, msg):
    with app.app_context():
        print(f"Sending email to {msg['to']}")

def send_email(msg):
    Thread(target=send_async_email, args=(app, msg)).start()

msg = {'to': '[e-mail]'}
send_email(msg)

medium

A. Sending email to {'to': '[e-mail]'}

B. Error: app context missing

C. Nothing is printed

D. Sending email to [e-mail]

Solution

1. Step 1: Understand app context usage

   The send_async_email function uses app.app_context() to access Flask context safely in thread.

2. Step 2: Analyze print statement

   It prints the 'to' value from msg dictionary, which is '[e-mail]'.

3. Final Answer:

   Sending email to [e-mail] -> Option D

4. Quick Check:

   App context allows printing correct email [OK]

Hint: App context lets threads access Flask variables safely [OK]

Common Mistakes:

• Assuming app context is not needed in thread
• Expecting no output because of threading
• Printing whole dict instead of 'to' value

4. What is wrong with this async email sending code in Flask?

def send_async_email(msg):
    print(f"Sending email to {msg['to']}")

def send_email(msg):
    Thread(target=send_async_email, args=(msg,)).start()

medium

A. Missing Flask app context in thread

B. Thread target should be send_email, not send_async_email

C. args should be a dictionary, not a tuple

D. print statement should be outside the thread

Solution

1. Step 1: Identify Flask context requirement

   Flask requires app context inside threads to access app variables safely.

2. Step 2: Check code for app context usage

   The send_async_email function lacks app.app_context(), so it may fail or behave unexpectedly.

3. Final Answer:

   Missing Flask app context in thread -> Option A

4. Quick Check:

   Threads need app context to access Flask safely [OK]

Hint: Always use app.app_context() inside threads [OK]

Common Mistakes:

• Ignoring app context in threads
• Confusing target function in Thread
• Misunderstanding args format

5. You want to send an email asynchronously in Flask but also log the email sending status after it finishes. Which approach correctly combines async sending with logging?

hard

A. Use a thread with app context to send email, then log inside the same thread after sending

B. Send email synchronously, then start a thread to log status

C. Start two separate threads: one for sending email, one for logging, without app context

D. Send email asynchronously but log status immediately after starting the thread

Solution

1. Step 1: Understand async email sending with app context

   Sending email in a thread requires app.app_context() to access Flask features safely.

2. Step 2: Combine logging after sending in same thread

   Logging after sending inside the same thread ensures the status reflects actual completion.

3. Step 3: Evaluate other options

   Logging before or in separate threads without context risks incorrect or missing info.

4. Final Answer:

   Use a thread with app context to send email, then log inside the same thread after sending -> Option A

5. Quick Check:

   Send and log in same app-context thread [OK]

Hint: Log after sending inside same app-context thread [OK]

Common Mistakes:

• Logging before email is sent
• Starting logging thread without app context
• Separating send and log in different threads