Tatizo la query za N+1 ni tatizo la kawaida zaidi la utendaji wa Django ORM: kufikia objects zinazohusiana ndani ya loop kunasababisha query tofauti ya database kwa kila moja. select_related na prefetch_related zinalitatua kwa kuleta data inayohusiana kwa ufanisi — ni zana muhimu za uboreshaji.
books = Book.objects.()
book books:
(book.author.name)
Kila ufikiaji wa book.author unahoji database tena kwa ulegevu. Kwa vitabu 100, hiyo ni queries 101 — muuaji mkali na wa siri wa utendaji ambao mara nyingi unajitokeza tu chini ya kiasi halisi cha data.
# ✅ ONE query with a JOIN
books = Book.objects.select_related("author").all()
for book in books:
print(book.author.name) # NO extra queries — author was JOINed in
# 100 books → 1 query total
select_related inafanya SQL JOIN kuleta object(s) zinazohusiana katika query ileile. Itumie kwa relationships za forward ForeignKey na OneToOne (object moja inayohusiana), ambapo JOIN ina ufanisi.
# ✅ TWO queries total (not N+1)
authors = Author.objects.prefetch_related("books").all()
for author in authors:
for book in author.books.all(): # NO extra queries — books were prefetched
print(book.title)
# query 1: all authors; query 2: all their books → Django joins them in Python
prefetch_related inaendesha query tofauti kwa objects zinazohusiana na inaziunganisha katika Python. Itumie kwa relationships za ManyToMany na reverse ForeignKey (objects nyingi zinazohusiana), ambapo JOIN ingezidisha rows kwa njia isiyo na ufanisi.
select_related → ForeignKey, OneToOne (forward, single object) → SQL JOIN, 1 query
prefetch_related → ManyToMany, reverse ForeignKey (many objects) → 2 queries, joined in Python
You can combine and chain them, and span relationships:
Book.objects.select_related("author").prefetch_related("tags")
Book.objects.select_related("author__publisher") # multi-level
✓ Django Debug Toolbar — shows the query count per page (spot N+1 visually)
✓ django-silk, or logging queries (connection.queries) to count them
→ If a page runs hundreds of similar queries, you likely have an N+1.
Tatizo la query za N+1 ni tatizo moja la kawaida zaidi na lenye athari kubwa zaidi la utendaji katika programu za Django, na kuelewa select_related/prefetch_related ni muhimu kwa kuandika code yenye utendaji bora.
Tatizo ni la udanganyifu kwa sababu syntax rahisi ya ORM inayofanya kufikia objects zinazohusiana kuwa rahisi sana (book.author.name) inasababisha kimya query ya database kila wakati — code inayofanya kazi vizuri na rekodi chache inaharibika kwa janga na kiasi halisi cha data (rekodi 100 → queries 101), mara nyingi inagunduliwa tu katika production chini ya mzigo.
Zana hizi mbili ndizo suluhisho la kawaida na muhimu: select_related inatumia SQL JOIN kuleta relationships za forward ForeignKey/OneToOne katika query moja, wakati prefetch_related inatumia query tofauti (iliyounganishwa katika Python) kwa relationships za ManyToMany/reverse-ForeignKey ambapo JOIN ingekuwa isiyo na ufanisi — na kujua ipi ya kutumia kwa aina ipi ya relationship ndio ujuzi muhimu.
Kuzimudu kunageuza mamia ya queries kuwa moja au mbili, mara nyingi kuboresha utendaji wa ukurasa kwa kiasi kikubwa.
Uboreshaji huu ni wa msingi sana kiasi kwamba kutambua matatizo ya N+1 (kwa kutumia zana kama Django Debug Toolbar kuona idadi kubwa ya queries) na kutumia suluhisho sahihi ni umahiri wa msingi unaotofautisha waendelezaji wanaoandika code ya Django yenye ufanisi na wale ambao programu zao zinapungua kasi data inapokua.
Pia ni mojawapo ya mada za Django za mahojiano zinazopimwa mara kwa mara, hasa kwa sababu inaonyesha ufahamu wa kivitendo na muhimu kwa utendaji wa ORM.