Nested models in FastAPI - Performance & Optimization

Performance: Nested models

MEDIUM IMPACT

This affects the server response time and client rendering speed by increasing data serialization and deserialization complexity.

Returning deeply nested data structures in API responses

FastAPI

from pydantic import BaseModel
from fastapi import FastAPI

app = FastAPI()

class UserSummary(BaseModel):
    name: str

class CompanySummary(BaseModel):
    name: str
    owner_name: str

@app.get('/company')
def get_company():
    return CompanySummary(name='Acme', owner_name='Alice')

Flattening nested models reduces serialization complexity and payload size, speeding up response and client rendering.

📈 Performance GainReduces serialization time by 50-70%; cuts payload size by 30-60%

Returning deeply nested data structures in API responses

FastAPI

from pydantic import BaseModel
from fastapi import FastAPI

app = FastAPI()

class Address(BaseModel):
    street: str
    city: str

class User(BaseModel):
    name: str
    address: Address

class Company(BaseModel):
    name: str
    owner: User

@app.get('/company')
def get_company():
    return Company(name='Acme', owner=User(name='Alice', address=Address(street='123 Main', city='Town')))

Deep nesting causes slow serialization and large JSON payloads, increasing response time and client parsing cost.

📉 Performance CostBlocks response serialization for 10-30ms depending on depth; increases payload size by 20-50%

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Deeply nested models	N/A (server-side)	N/A	Higher due to larger payload	[X] Bad
Flattened or simplified models	N/A (server-side)	N/A	Lower due to smaller payload	[OK] Good

Rendering Pipeline

Nested models increase the server's serialization workload, delaying the response sent to the browser. Larger JSON payloads take longer to download and parse, delaying the browser's ability to render content.

→Server Serialization

→Network Transfer

→Browser Parsing

→Rendering

⚠️ BottleneckServer Serialization and Browser Parsing

Core Web Vital Affected

LCP

This affects the server response time and client rendering speed by increasing data serialization and deserialization complexity.

Optimization Tips

1Avoid deep nesting in API response models to reduce serialization time.

2Flatten nested models when possible to decrease JSON payload size.

3Use selective fields or summaries to send only necessary data.

Performance Quiz - 3 Questions

How do deeply nested models in FastAPI responses affect page load performance?

A They reduce server load by simplifying data.

B They increase serialization time and payload size, slowing down response and rendering.

C They have no impact on performance.

D They improve browser rendering speed by organizing data.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the API request, and inspect the response size and timing.

What to look for: Look for large JSON payload size and long response times indicating heavy nested serialization.