Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Reducing queries for ForeignKeys in Django admin inlines" | Hashnode

Feed/

Discussion

Reducing queries for ForeignKeys in Django admin inlines

Use 93x less queries using patched raw_id_fields and prefetching

Jan 11, 2023·3 min read·deepintodjango.comUpdated Apr 24, 2023Read the article

#django
#prefetching
#optimization

#performance

#python

Written by

Jurrian Tromp

@jurrian · Utrecht, The Netherlands

View profile

Freelance Webdeveloper

Made my first website in Microsoft Word at age 13, when I discovered the "save as html" button. Since then I've journeyed various computing languages, eventually settling for Python. I love diving into the core of my favorite framework - Django - discover and writing about new stuff.

Responses1

Markdown supported · ⌘↵ to post

Ander

Aug 4, 2023

I am having performance issues because of the inlines, I am really curious about your solution, but is it just for Django v4? that way of defining inlines = ["some-inline"] as strings doesn't look familiar, shouldn't that be classes instead?

Jurrian Tromp

Aug 19, 2023

AFAIK this is applies to all Django versions. You are right that they should be classes instead. It might be that as a string it still works as lazy loading, so probably both work. The key of the problem is how the Django internals work in such a way that it creates a lot of extra queries.