Dependencies with parameters in FastAPI - Performance & Optimization

Performance: Dependencies with parameters

MEDIUM IMPACT

This affects server response time and resource usage during request handling.

Using dependencies with parameters in FastAPI endpoints

FastAPI

from fastapi import Depends, FastAPI

app = FastAPI()

def get_db_connection(param: str):
    # Simulate expensive setup
    return f"DB connection with {param}"

def get_param():
    return "my_param"

@app.get("/items/")
async def read_items(db=Depends(lambda: get_db_connection(get_param()))):
    return {"db": db}

Explicitly passing parameters ensures the dependency is called with correct arguments and can be cached or reused if designed properly.

📈 Performance GainReduces unnecessary calls and improves response time by controlling parameter passing.

Using dependencies with parameters in FastAPI endpoints

FastAPI

from fastapi import Depends, FastAPI

app = FastAPI()

def get_db_connection(param: str):
    # Simulate expensive setup
    return f"DB connection with {param}"

@app.get("/items/")
async def read_items(db=Depends(get_db_connection)):
    return {"db": db}

The dependency function expects a parameter but is used without passing it explicitly, causing FastAPI to call it without parameters or with default values, leading to unexpected behavior or repeated expensive calls.

📉 Performance CostTriggers repeated expensive calls per request, increasing response time.

Performance Comparison

Pattern	Dependency Calls	Parameter Passing	Response Time Impact	Verdict
Implicit parameter dependency	Multiple per request	No explicit passing	High due to repeated calls	[X] Bad
Explicit parameter passing with caching	Single or cached call	Explicit and controlled	Low, efficient reuse	[OK] Good

Rendering Pipeline

FastAPI resolves dependencies before executing the endpoint function. Dependencies with parameters require evaluating those parameters first, which can add CPU time and delay response generation.

→Dependency Resolution

→Request Handling

⚠️ BottleneckDependency Resolution stage when parameters cause repeated or expensive calls

Optimization Tips

1Always pass parameters explicitly to dependencies to avoid repeated calls.

2Cache expensive dependency results when parameters do not change.

3Profile dependency resolution time to identify bottlenecks.

Performance Quiz - 3 Questions

What is a main performance risk when using dependencies with parameters in FastAPI?

A Repeated expensive calls if parameters are not passed explicitly

B Increased bundle size due to dependencies

C Slower CSS rendering in the browser

D Higher memory usage in the client browser

DevTools: Network and Performance panels

How to check: Use the Network panel to measure response times for endpoints using dependencies with parameters. Use the Performance panel to profile CPU time spent in dependency resolution.

What to look for: Look for longer response times or CPU spikes during dependency calls indicating inefficient parameter handling.