From b042ab897636987701d3a35d6b566c6bef9d6ea2 Mon Sep 17 00:00:00 2001 From: Tom Forbes Date: Sat, 18 Aug 2018 14:22:21 +0100 Subject: [PATCH] Fixed #29685 -- Added QuerySet.explain() to the database optimization docs. --- docs/topics/db/optimization.txt | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/topics/db/optimization.txt b/docs/topics/db/optimization.txt index 96ff65fd7e..dad68f58af 100644 --- a/docs/topics/db/optimization.txt +++ b/docs/topics/db/optimization.txt @@ -11,8 +11,9 @@ Profile first ============= As general programming practice, this goes without saying. Find out :ref:`what -queries you are doing and what they are costing you -`. You may also want to use an external project like +queries you are doing and what they are costing you `. +Use :meth:`.QuerySet.explain` to understand how specific ``QuerySet``\s are +executed by your database. You may also want to use an external project like django-debug-toolbar_, or a tool that monitors your database directly. Remember that you may be optimizing for speed or memory or both, depending on @@ -114,6 +115,14 @@ When you have a lot of objects, the caching behavior of the ``QuerySet`` can cause a large amount of memory to be used. In this case, :meth:`~django.db.models.query.QuerySet.iterator()` may help. +Use ``explain()`` +----------------- + +:meth:`.QuerySet.explain` gives you detailed information about how the database +executes a query, including indexes and joins that are used. These details may +help you find queries that could be rewritten more efficiently, or identify +indexes that could be added to improve performance. + Do database work in the database rather than in Python ======================================================