Admin customization with ModelAdmin in Django - Performance & Optimization

Performance: Admin customization with ModelAdmin

MEDIUM IMPACT

This affects the admin interface load time and responsiveness by controlling how data is queried and displayed.

Displaying related objects in the admin list view

Django

class BookAdmin(admin.ModelAdmin):
    list_display = ('title', 'author_name')
    list_select_related = ('author',)

    def author_name(self, obj):
        return obj.author.name

Using list_select_related fetches related authors in one query, avoiding N+1 queries.

📈 Performance Gainreduces database queries from N+1 to 1, improving load speed

Displaying related objects in the admin list view

Django

class BookAdmin(admin.ModelAdmin):
    list_display = ('title', 'author_name')

    def author_name(self, obj):
        return obj.author.name

This triggers a database query for each row to fetch the related author, causing N+1 query problem.

📉 Performance Costtriggers N additional database queries for N rows, slowing page load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using list_select_related to fetch related data	Minimal extra DOM nodes	Single reflow	Low paint cost	[OK] Good
Querying related data per row without optimization	More DOM nodes due to delayed data	Multiple reflows	Higher paint cost	[X] Bad
Displaying many fields in list_display	Large DOM tree	Multiple reflows	High paint cost	[X] Bad
Limiting fields in list_display	Smaller DOM tree	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

ModelAdmin customization affects how Django queries data and generates HTML, impacting the browser's rendering pipeline by changing the amount of data and complexity of the page.

→Data Fetching

→HTML Generation

→Layout

→Paint

⚠️ BottleneckData Fetching due to inefficient queries causing delays before rendering

Core Web Vital Affected

INP

This affects the admin interface load time and responsiveness by controlling how data is queried and displayed.

Optimization Tips

1Use list_select_related or prefetch_related to reduce database queries.

2Limit list_display fields to essential columns to reduce HTML size.

3Avoid expensive custom methods in list_display that trigger extra queries.

Performance Quiz - 3 Questions

What is the main performance issue when not using list_select_related in ModelAdmin?

A JavaScript blocking rendering

B Too many CSS files loaded

C Multiple database queries for related objects (N+1 problem)

D Large image files slowing page load

DevTools: Performance

How to check: Open Django admin page, record performance profile while loading the list view, and inspect the timeline for scripting and rendering times.

What to look for: Look for long scripting times caused by many database queries or large HTML, and multiple layout/repaint events indicating inefficient rendering.