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.

Practice

1. What is the main purpose of customizing a Django ModelAdmin class?

easy

A. To define URL routes for the model views

B. To control how a model is displayed and managed in the Django admin interface

C. To write custom SQL queries for the model

D. To create new database tables automatically

Solution

1. Step 1: Understand ModelAdmin role

   The ModelAdmin class customizes the admin interface for a model, such as which fields show and how data is filtered.

2. Step 2: Identify what ModelAdmin does not do

   It does not create tables, write SQL, or define URLs; those are handled elsewhere in Django.

3. Final Answer:

   To control how a model is displayed and managed in the Django admin interface -> Option B

4. Quick Check:

   ModelAdmin controls admin display = D [OK]

Hint: ModelAdmin customizes admin display, not database or URLs [OK]

Common Mistakes:

• Confusing ModelAdmin with database migrations
• Thinking ModelAdmin handles URL routing
• Assuming ModelAdmin writes SQL queries

2. Which of the following is the correct way to register a model with a custom ModelAdmin in Django admin?

easy

A. admin.site.add(MyModel, MyModelAdmin)

B. admin.register(MyModel, MyModelAdmin)

C. admin.site.register(MyModel, MyModelAdmin)

D. admin.register_site(MyModel, MyModelAdmin)

Solution

1. Step 1: Recall Django admin registration syntax

   The correct method to register a model with a custom admin class is admin.site.register(Model, ModelAdmin).

2. Step 2: Check other options for validity

   Other options like admin.register or admin.site.add do not exist in Django's admin API.

3. Final Answer:

   admin.site.register(MyModel, MyModelAdmin) -> Option C

4. Quick Check:

   Use admin.site.register to register models = A [OK]

Hint: Use admin.site.register(Model, AdminClass) to register [OK]

Common Mistakes:

• Using admin.register instead of admin.site.register
• Trying to call admin.site.add which doesn't exist
• Confusing method names for registration

3. Given this ModelAdmin code, what fields will appear in the Django admin list view?

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

admin.site.register(Book, BookAdmin)

medium

A. 'title', 'author', and 'published_date' fields

B. Only 'title' and 'author' fields

C. All fields of the Book model

D. No fields will appear because list_display is incorrect

Solution

1. Step 1: Understand list_display usage

   The list_display attribute defines exactly which fields show in the admin list view.

2. Step 2: Check the fields listed

   The tuple includes 'title', 'author', and 'published_date', so these three fields will appear.

3. Final Answer:

   'title', 'author', and 'published_date' fields -> Option A

4. Quick Check:

   list_display shows specified fields = A [OK]

Hint: list_display shows only fields listed in its tuple [OK]

Common Mistakes:

• Assuming all model fields show by default
• Thinking list_display must include all fields
• Believing list_display is optional for showing fields

4. What is wrong with this ModelAdmin code snippet?

class AuthorAdmin(admin.ModelAdmin):
    search_fields = 'name'

admin.site.register(Author, AuthorAdmin)

medium

A. search_fields should be a list or tuple, not a string

B. AuthorAdmin must inherit from admin.ModelAdminBase

C. admin.site.register is missing parentheses

D. search_fields cannot be used in ModelAdmin

Solution

1. Step 1: Check search_fields type

   The search_fields attribute must be a list or tuple of field names, not a single string.

2. Step 2: Validate other parts

   Inheritance from admin.ModelAdmin is correct, registration syntax is correct, and search_fields is valid in ModelAdmin.

3. Final Answer:

   search_fields should be a list or tuple, not a string -> Option A

4. Quick Check:

   search_fields needs list/tuple = C [OK]

Hint: Wrap search_fields in [] or () even for one field [OK]

Common Mistakes:

• Using a plain string instead of list/tuple for search_fields
• Confusing ModelAdmin inheritance class
• Missing parentheses in admin.site.register (not here though)

5. You want to add a filter sidebar in Django admin to filter books by their 'genre' and 'published_year'. Which ModelAdmin attribute should you customize, and how?

hard

A. Add filter_fields = ['genre', 'published_year'] in the ModelAdmin

B. Use search_fields = ('genre', 'published_year') to enable filtering

C. Override filter_sidebar = True in the ModelAdmin

D. Set list_filter = ('genre', 'published_year') in the ModelAdmin class

Solution

1. Step 1: Identify correct attribute for filters

   The list_filter attribute adds filter sidebars for specified fields in the admin list view.

2. Step 2: Check other options for correctness

   filter_fields and filter_sidebar do not exist; search_fields is for search, not filters.

3. Final Answer:

   Set list_filter = ('genre', 'published_year') in the ModelAdmin class -> Option D

4. Quick Check:

   Use list_filter for sidebar filters = B [OK]

Hint: Use list_filter tuple to add filter sidebar fields [OK]

Common Mistakes:

• Using search_fields instead of list_filter for filters
• Trying to use non-existent filter_fields attribute
• Assuming filter_sidebar is a valid option