Performance: Cookie-based sessions vs database sessions
MEDIUM IMPACT
This affects page load speed and interaction responsiveness by changing how session data is stored and accessed.
SESSION_ENGINE = 'django.contrib.sessions.backends.signed_cookies' # Session data stored in signed cookie, no DB query needed
SESSION_ENGINE = 'django.contrib.sessions.backends.db' # Session data stored in database, fetched on each request
| Pattern | DOM Operations | Reflows | Paint Cost | Verdict |
|---|---|---|---|---|
| Cookie-based sessions | No extra DOM nodes | 0 reflows | Minimal paint impact | [OK] Good for small session data |
| Database sessions | No extra DOM nodes | 0 reflows | Minimal paint impact | [!] OK but adds server delay |
| Large cookie sessions | No extra DOM nodes | 0 reflows | Increased paint time due to payload | [X] Bad for large data |
| Database sessions with heavy queries | No extra DOM nodes | 0 reflows | Blocks rendering until DB responds | [X] Bad for high traffic |