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
-<cached-sessions-backend>` to improve performance.
-
 :setting:`DATABASES`
 --------------------
 
@@ -187,6 +184,15 @@ Performance optimizations
 Setting :setting:`DEBUG = False <DEBUG>` disables several features that are
 only useful in development. In addition, you can tune the following settings.
 
+Sessions
+--------
+
+Consider using :ref:`cached sessions <cached-sessions-backend>` to improve
+performance.
+
+If using database-backed sessions, regularly :ref:`clear old sessions
+<clearing-the-session-store>` to avoid storing unnecessary data.
+
 :setting:`CONN_MAX_AGE`
 -----------------------
 
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt
index 5921ba6625..71abe7603e 100644
--- a/docs/topics/http/sessions.txt
+++ b/docs/topics/http/sessions.txt
@@ -599,6 +599,8 @@ of ``request.session`` as described above in `using sessions in views`_.
     Django applications which have the
     :setting:`SESSION_EXPIRE_AT_BROWSER_CLOSE` setting enabled.
 
+.. _clearing-the-session-store:
+
 Clearing the session store
 ==========================