Async generator dependencies in FastAPI - Performance & Optimization

Performance: Async generator dependencies

MEDIUM IMPACT

This affects server response time and resource management during request handling in FastAPI.

Managing database connections per request using dependencies

FastAPI

async def get_db():
    db = await async_create_db_connection()
    try:
        yield db
    finally:
        await db.aclose()

Fully async generator avoids blocking, allowing other requests to be handled concurrently.

📈 Performance Gainnon-blocking resource management, reduces response time under load

Managing database connections per request using dependencies

FastAPI

def get_db():
    db = create_db_connection()
    try:
        yield db
    finally:
        db.close()

Using a synchronous generator or blocking calls inside async dependency can block the event loop.

📉 Performance Costblocks event loop during connection setup and teardown, increasing response latency

Performance Comparison

Pattern	Event Loop Blocking	Resource Cleanup	Concurrency Impact	Verdict
Sync generator dependency	Blocks event loop	Synchronous cleanup	Reduces concurrency	[X] Bad
Async generator dependency	Non-blocking	Async cleanup	Maximizes concurrency	[OK] Good

Rendering Pipeline

Async generator dependencies run during request lifecycle, affecting how FastAPI schedules and executes request handlers without blocking the event loop.

→Request Handling

→Async Scheduling

→Resource Cleanup

⚠️ BottleneckBlocking synchronous calls inside async generators cause event loop delays.

Optimization Tips

1Always use fully async calls inside async generator dependencies to avoid blocking.

2Ensure resource cleanup is done asynchronously to prevent event loop delays.

3Avoid mixing synchronous and asynchronous code in dependencies to maintain concurrency.

Performance Quiz - 3 Questions

What is the main performance benefit of using async generator dependencies in FastAPI?

A They reduce the size of the response payload.

B They prevent blocking the event loop during resource management.

C They automatically cache responses for faster delivery.

D They increase CPU usage to speed up processing.

DevTools: Network and Performance panels

How to check: Use Performance panel to record request handling; check for long tasks blocking the event loop. Use Network panel to measure response times under load.

What to look for: Look for long blocking tasks or delayed responses indicating synchronous blocking in async dependencies.

Practice

1. What is the main purpose of using an async generator dependency in FastAPI?

easy

A. To manage setup and cleanup actions around a request automatically

B. To speed up synchronous code execution

C. To replace all regular functions with asynchronous ones

D. To create infinite loops inside API endpoints

Solution

1. Step 1: Understand async generator dependencies

   Async generator dependencies use async def with yield to run setup code before yielding and cleanup code after.

2. Step 2: Identify their purpose in FastAPI

   This pattern is mainly used to manage resources safely, like opening and closing database connections around a request.

3. Final Answer:

   To manage setup and cleanup actions around a request automatically -> Option A

4. Quick Check:

   Async generator dependencies = setup + cleanup [OK]

Hint: Think setup before yield, cleanup after yield [OK]

Common Mistakes:

• Confusing async generators with normal async functions
• Thinking they speed up synchronous code
• Assuming they replace all functions

2. Which of the following is the correct syntax to define an async generator dependency in FastAPI?

easy

A. async def resource(): yield 'data'

B. def resource(): yield 'data'

C. async def resource(): return 'data'

D. def resource(): return 'data'

Solution

1. Step 1: Identify async generator syntax

   An async generator uses async def and yield inside the function body.

2. Step 2: Compare options

   async def resource(): yield 'data' uses async def and yield, which is correct. Options A and B are synchronous, and C uses return instead of yield.

3. Final Answer:

   async def resource(): yield 'data' -> Option A

4. Quick Check:

   Async + yield = async generator [OK]

Hint: Async generator = async def + yield inside [OK]

Common Mistakes:

• Using return instead of yield
• Forgetting async keyword
• Using synchronous def for async generator

3. Given this FastAPI async generator dependency, what will be printed when the endpoint is called?

async def resource():
    print('Setup')
    yield 'data'
    print('Cleanup')

@app.get('/')
async def read(resource=Depends(resource)):
    print('Inside endpoint')
    return resource

medium

A. Inside endpoint only

B. Inside endpoint, Setup, Cleanup

C. Setup, Cleanup, Inside endpoint

D. Setup, Inside endpoint, Cleanup

Solution

1. Step 1: Understand async generator flow

   When the endpoint is called, FastAPI runs the async generator up to the yield (prints 'Setup'), then runs the endpoint code (prints 'Inside endpoint'), then after response finishes, runs code after yield (prints 'Cleanup').

2. Step 2: Order of prints

   The prints happen in order: 'Setup', 'Inside endpoint', 'Cleanup'.

3. Final Answer:

   Setup, Inside endpoint, Cleanup -> Option D

4. Quick Check:

   Yield pauses, so Setup before, Cleanup after endpoint [OK]

Hint: Setup prints before yield, cleanup after endpoint runs [OK]

Common Mistakes:

• Assuming cleanup runs before endpoint
• Thinking yield returns immediately
• Ignoring async generator lifecycle

4. Identify the error in this async generator dependency code:

async def resource():
    connection = await connect_db()
    yield connection
    await connection.close()

@app.get('/')
async def read(conn=Depends(resource)):
    return {'status': 'ok'}

medium

A. Missing await before yield

B. Cannot yield inside async def

C. Not using try-finally to ensure cleanup

D. Depends should not be used with async generators

Solution

1. Step 1: Check resource cleanup safety

   Without try-finally, if an exception occurs, await connection.close() might not run, causing resource leaks.

2. Step 2: Proper pattern for async generator cleanup

   Use try-finally around yield to guarantee cleanup runs even on errors.

3. Final Answer:

   Not using try-finally to ensure cleanup -> Option C

4. Quick Check:

   Always use try-finally for cleanup in async generators [OK]

Hint: Use try-finally to guarantee cleanup after yield [OK]

Common Mistakes:

• Forgetting try-finally causes resource leaks
• Thinking yield needs await
• Believing Depends can't use async generators

5. You want to create an async generator dependency that opens a database connection, yields it, and ensures it closes even if the endpoint raises an error. Which code snippet correctly implements this?

hard

A. async def db():
conn = await open_db()
yield conn
await conn.close()

B. async def db():
conn = await open_db()
try:
yield conn
finally:
await conn.close()

C. async def db():
conn = await open_db()
yield conn
conn.close()

D. async def db():
conn = open_db()
yield conn
await conn.close()

Solution

1. Step 1: Ensure proper async resource management

   Opening the connection must be awaited, and closing must happen even if errors occur.

2. Step 2: Use try-finally around yield

   Only async def db(): conn = await open_db() try: yield conn finally: await conn.close() uses try-finally to guarantee await conn.close() runs after yield, even on exceptions.

3. Final Answer:

   async def db(): conn = await open_db() try: yield conn finally: await conn.close() -> Option B

4. Quick Check:

   Try-finally ensures cleanup after yield [OK]

Hint: Wrap yield in try-finally to always close resources [OK]

Common Mistakes:

• Not awaiting open_db()
• Not using try-finally for cleanup
• Calling close() without await