From ec57addbc7609d79adaa83e25ffd77bbde6daf69 Mon Sep 17 00:00:00 2001 From: Jan Pieter Waagmeester Date: Mon, 23 May 2016 14:51:04 +0200 Subject: [PATCH] Some words about perfomance (fixes #133 --- docs/pages/getting-started.rst | 1 + docs/pages/performance.rst | 12 ++++++++++++ 2 files changed, 13 insertions(+) create mode 100644 docs/pages/performance.rst diff --git a/docs/pages/getting-started.rst b/docs/pages/getting-started.rst index 28789a69..4d08c50c 100644 --- a/docs/pages/getting-started.rst +++ b/docs/pages/getting-started.rst @@ -14,3 +14,4 @@ in your template setting ``OPTIONS``. .. toctree:: tutorial table-data + performance diff --git a/docs/pages/performance.rst b/docs/pages/performance.rst new file mode 100644 index 00000000..660abfde --- /dev/null +++ b/docs/pages/performance.rst @@ -0,0 +1,12 @@ +Performance +----------- + +Django-tables tries to be efficient in displaying big datasets. It tries to +avoid converting the `~django.db.models.query.QuerySet` instances to lists by +using SQL to slice the data and should be able to handle datasets with 100k +records without a problem. + +However, when using one of the customisation methods described in this +documentation, there is lot's of oppurtunity to introduce slowness. +If you experience that, try to strip the table of customisations and re-add them +one by one, checking for performance after each step.