ASGI and async-first architecture in FastAPI - Performance & Optimization

Performance: ASGI and async-first architecture

HIGH IMPACT

This affects how quickly the server can handle multiple requests and respond without blocking, improving interaction speed and throughput.

Handling multiple web requests efficiently in a FastAPI app

FastAPI

from fastapi import FastAPI
import asyncio
app = FastAPI()

@app.get("/async")
async def async_endpoint():
    await asyncio.sleep(2)  # non-blocking sleep
    return {"message": "done"}

Using async and await allows the event loop to handle other requests during wait times, improving concurrency and responsiveness.

📈 Performance GainNon-blocking wait allows many requests to be handled concurrently, reducing input delay significantly

Handling multiple web requests efficiently in a FastAPI app

FastAPI

from fastapi import FastAPI
app = FastAPI()

@app.get("/sync")
def sync_endpoint():
    import time
    time.sleep(2)  # blocking sleep
    return {"message": "done"}

Blocking calls like time.sleep block the event loop, preventing other requests from being processed concurrently.

📉 Performance CostBlocks event loop for 2 seconds per request, causing high input delay and poor concurrency

Performance Comparison

Pattern	Concurrency	Event Loop Blocking	Input Delay	Verdict
Synchronous blocking calls	Low (serial)	High (blocks event loop)	High (long input delay)	[X] Bad
Async-first non-blocking calls	High (concurrent)	Low (event loop free)	Low (fast input response)	[OK] Good

Rendering Pipeline

ASGI async-first architecture uses an event loop to manage request handling without blocking, allowing multiple requests to be processed in overlapping time frames.

→Request Handling

→Event Loop Scheduling

→Response Sending

⚠️ BottleneckBlocking synchronous calls that pause the event loop

Core Web Vital Affected

INP

This affects how quickly the server can handle multiple requests and respond without blocking, improving interaction speed and throughput.

Optimization Tips

1Avoid blocking calls inside async endpoints to keep the event loop free.

2Use async/await for I/O operations to improve concurrency and responsiveness.

3Async-first architecture reduces input delay, improving user interaction speed.

Performance Quiz - 3 Questions

What is the main performance benefit of using async functions in FastAPI with ASGI?

A They improve the visual layout stability of the page.

B They allow handling multiple requests concurrently without blocking.

C They reduce the size of the server code bundle.

D They automatically cache responses to speed up loading.

DevTools: Network and Performance panels

How to check: Use Performance panel to record server response times and check for long blocking tasks; use Network panel to see request concurrency and timing.

What to look for: Look for long blocking tasks in the flame chart and overlapping request handling indicating concurrency.

Practice

1. What does ASGI enable FastAPI to do compared to traditional synchronous frameworks?

easy

A. Use only synchronous functions for better speed

B. Run only one request at a time to avoid conflicts

C. Handle many requests at the same time using async code

D. Automatically convert Python code to JavaScript

Solution

1. Step 1: Understand ASGI's role

   ASGI is designed to handle multiple requests concurrently using asynchronous programming.

2. Step 2: Compare with synchronous frameworks

   Traditional synchronous frameworks handle one request at a time, blocking others until done.

3. Final Answer:

   Handle many requests at the same time using async code -> Option C

4. Quick Check:

   ASGI = concurrent async handling [OK]

Hint: ASGI means multitasking with async code [OK]

Common Mistakes:

• Thinking ASGI runs requests one by one
• Confusing ASGI with code conversion tools
• Believing async slows down the app

2. Which of the following is the correct way to define an async route handler in FastAPI?

easy

A. async def read_root(): return {"message": "Hello"}

B. def read_root(): return {"message": "Hello"}

C. async read_root(): return {"message": "Hello"}

D. def async read_root(): return {"message": "Hello"}

Solution

1. Step 1: Recall async function syntax

   In Python, async functions start with async def followed by the function name.

2. Step 2: Check each option's syntax

   async def read_root(): return {"message": "Hello"} correctly uses async def. Options C and D have invalid syntax. def read_root(): return {"message": "Hello"} is synchronous.

3. Final Answer:

   async def read_root(): return {"message": "Hello"} -> Option A

4. Quick Check:

   Async function = async def [OK]

Hint: Async functions start with 'async def' [OK]

Common Mistakes:

• Omitting 'def' after 'async'
• Placing 'async' after 'def'
• Using synchronous 'def' for async routes

3. Given this FastAPI route handler, what will be the output when accessed?

from fastapi import FastAPI
import asyncio

app = FastAPI()

@app.get("/wait")
async def wait_and_return():
    await asyncio.sleep(1)
    return {"status": "done"}

medium

A. Error because asyncio.sleep cannot be awaited

B. Immediate response with {"status": "done"}

C. Server crashes due to blocking call

D. {"status": "done"} after 1 second delay

Solution

1. Step 1: Understand async sleep behavior

   The function uses await asyncio.sleep(1), which pauses the function asynchronously for 1 second.

2. Step 2: Predict response timing

   The response will be sent after the 1 second delay, returning the JSON with status done.

3. Final Answer:

   {"status": "done"} after 1 second delay -> Option D

4. Quick Check:

   Await asyncio.sleep = delayed async response [OK]

Hint: Await asyncio.sleep delays response asynchronously [OK]

Common Mistakes:

• Thinking await asyncio.sleep blocks all requests
• Expecting immediate response ignoring await
• Confusing asyncio.sleep with time.sleep

4. Identify the error in this FastAPI async route handler:

from fastapi import FastAPI
import asyncio

app = FastAPI()

@app.get("/error")
def error_route():
    await asyncio.sleep(1)
    return {"message": "done"}

medium

A. Missing async keyword before function definition

B. Cannot use await inside async function

C. FastAPI does not support async routes

D. Return statement must be inside try-except block

Solution

1. Step 1: Check function definition

   The function uses await but is defined without async, which is invalid syntax.

2. Step 2: Understand async function requirements

   To use await, the function must be declared with async def.

3. Final Answer:

   Missing async keyword before function definition -> Option A

4. Quick Check:

   Await requires async def [OK]

Hint: Use async def when using await inside function [OK]

Common Mistakes:

• Forgetting async before def
• Thinking await works in sync functions
• Believing FastAPI disallows async routes

5. You want to create a FastAPI endpoint that fetches data from two slow APIs concurrently to improve speed. Which approach best uses FastAPI's async-first architecture?

hard

A. Use async functions with await on both API calls sequentially

B. Use asyncio.gather to run both async API calls concurrently inside an async route

C. Call both APIs one after another using synchronous requests inside an async function

D. Run synchronous API calls in separate threads without async

Solution

1. Step 1: Understand concurrency with async

   Calling APIs sequentially with await waits for each to finish before starting the next, not concurrent.

2. Step 2: Use asyncio.gather for concurrency

   asyncio.gather runs multiple async tasks at the same time, improving speed.

3. Step 3: Compare options

   Use asyncio.gather to run both async API calls concurrently inside an async route uses asyncio.gather inside async route, best leveraging FastAPI's async-first design.

4. Final Answer:

   Use asyncio.gather to run both async API calls concurrently inside an async route -> Option B

5. Quick Check:

   asyncio.gather = concurrent async calls [OK]

Hint: Use asyncio.gather for concurrent async calls [OK]

Common Mistakes:

• Awaiting calls sequentially losing concurrency
• Using synchronous calls blocking event loop
• Ignoring async and threading differences