From 76db34e52a7852dc292a1792c8a0499ac65faced Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Wed, 25 Mar 2020 11:04:52 +0000 Subject: [3.0.x] Improved sessions notes in deployment checklist. - Added note to clear old sessions when using database-backend. - Made note to consider the cache backend more generic. Backport of 66b06822d05ca1cf897745e7cb3c89adc53363ba from master --- docs/howto/deployment/checklist.txt | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'docs/howto') diff --git a/docs/howto/deployment/checklist.txt b/docs/howto/deployment/checklist.txt index b307076b62..06bf08473a 100644 --- a/docs/howto/deployment/checklist.txt +++ b/docs/howto/deployment/checklist.txt @@ -109,9 +109,6 @@ and in production. Django defaults to per-process :ref:`local-memory caching Cache servers often have weak authentication. Make sure they only accept connections from your application servers. -If you're using Memcached, consider using :ref:`cached sessions -` to improve performance. - :setting:`DATABASES` -------------------- @@ -187,6 +184,15 @@ Performance optimizations Setting :setting:`DEBUG = False ` disables several features that are only useful in development. In addition, you can tune the following settings. +Sessions +-------- + +Consider using :ref:`cached sessions ` to improve +performance. + +If using database-backed sessions, regularly :ref:`clear old sessions +` to avoid storing unnecessary data. + :setting:`CONN_MAX_AGE` ----------------------- -- cgit v1.3