Setting and getting session data in Django - Performance & Optimization

Performance: Setting and getting session data

MEDIUM IMPACT

This affects server response time and client perceived speed by managing user session data efficiently.

Storing and retrieving user session data in Django views

Django

def view(request):
    request.session['cart_id'] = cart_id
    cart = get_cart_from_db(cart_id)
    return HttpResponse('Done')

Store only small identifiers in session and fetch large data from database on demand.

📈 Performance Gainreduces session serialization time; faster response and better INP

Storing and retrieving user session data in Django views

Django

def view(request):
    request.session['cart'] = large_cart_object
    data = request.session['cart']
    return HttpResponse('Done')

Storing large objects in session causes slow serialization and increases response time.

📉 Performance Costblocks rendering for 50-100ms depending on data size; increases server CPU usage

Performance Comparison

Pattern	Session Data Size	Session Writes	Server Response Impact	Verdict
Store large objects in session	Large	Multiple	High delay due to serialization	[X] Bad
Store small IDs and fetch data on demand	Small	Single	Low delay, faster response	[OK] Good
Multiple session writes separately	Small	Multiple	Moderate delay due to repeated saves	[!] OK
Batch session updates in one call	Small	Single	Minimal delay, efficient	[OK] Good

Rendering Pipeline

Session data is handled on the server before the response is sent. Large or frequent session writes increase server processing time, delaying response and user interaction readiness.

→Server Processing

→Response Time

→Interaction Readiness

⚠️ BottleneckServer Processing due to session serialization and save

Core Web Vital Affected

INP

This affects server response time and client perceived speed by managing user session data efficiently.

Optimization Tips

1Keep session data small to reduce serialization overhead.

2Batch session updates to minimize save operations.

3Avoid storing large objects directly in session.

Performance Quiz - 3 Questions

What is a performance benefit of storing only small identifiers in Django session instead of large objects?

A Reduces server serialization time and speeds up response

B Increases session size but reduces database queries

C Improves client-side rendering speed directly

D Eliminates the need for session cookies

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check server response times for requests involving session data.

What to look for: Look for longer server response times indicating slow session processing; compare with optimized versions.