Cache invalidation strategies in Django - Performance & Optimization

Performance: Cache invalidation strategies

HIGH IMPACT

This affects page load speed by controlling how fresh cached content is served and how often the server recomputes or fetches data.

Serving dynamic content with cache that updates when data changes

Django

from django.core.cache import cache

def get_data():
    data = cache.get('my_data')
    if not data:
        data = expensive_db_query()
        cache.set('my_data', data)
    return data

def update_data(new_data):
    save_to_db(new_data)
    cache.delete('my_data')  # invalidate cache immediately

Invalidates cache immediately when data changes, ensuring fresh content without waiting for timeout.

📈 Performance GainReduces stale content delivery and avoids unnecessary cache expiration spikes.

Serving dynamic content with cache that updates when data changes

Django

from django.core.cache import cache

def get_data():
    data = cache.get('my_data')
    if not data:
        data = expensive_db_query()
        cache.set('my_data', data, timeout=3600)  # fixed 1 hour timeout
    return data

Using a fixed timeout can serve stale data for up to an hour even if the underlying data changes immediately.

📉 Performance CostCauses poor user experience due to stale content; may increase server load when cache expires simultaneously.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Fixed timeout cache invalidation	N/A	N/A	May delay fresh content load	[X] Bad
Manual cache key deletion	N/A	N/A	Multiple cache calls increase server load	[!] OK
Batch cache key deletion (delete_many)	N/A	N/A	Fewer cache calls, consistent invalidation	[OK] Good
Cache versioning	N/A	N/A	Automatic fresh content with minimal overhead	[OK] Good

Rendering Pipeline

Cache invalidation affects how quickly fresh content is available to the browser, impacting the server response time and thus the browser's rendering start.

→Server Response

→Critical Rendering Path

→Resource Fetching

⚠️ BottleneckServer Response time due to cache misses or stale data forcing recomputation

Core Web Vital Affected

LCP

This affects page load speed by controlling how fresh cached content is served and how often the server recomputes or fetches data.

Optimization Tips

1Avoid fixed timeout invalidation for frequently changing data.

2Use cache.delete_many to delete multiple related cache entries efficiently.

3Implement cache versioning to automatically handle data updates.

Performance Quiz - 3 Questions

What is a downside of using a fixed timeout cache invalidation strategy?

A It always deletes cache immediately after data changes.

B It reduces server load by never recomputing data.

C It can serve stale content until the timeout expires.

D It automatically updates cache keys with data changes.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check response headers for cache status (e.g., X-Cache or Age headers).

What to look for: Look for cache hits (fast responses) vs cache misses (longer server times) to verify cache effectiveness and invalidation.

Practice

1. What is the main purpose of cache invalidation in Django caching?

easy

A. To store data permanently without expiration

B. To keep cached data fresh and accurate

C. To increase the size of the cache

D. To disable caching completely

Solution

1. Step 1: Understand cache invalidation concept

   Cache invalidation means removing or updating cached data so it stays correct and up-to-date.

2. Step 2: Identify the purpose in Django caching

   In Django, cache invalidation ensures users see fresh data by removing outdated cache entries.

3. Final Answer:

   To keep cached data fresh and accurate -> Option B

4. Quick Check:

   Cache invalidation = fresh data [OK]

Hint: Cache invalidation means keeping data fresh [OK]

Common Mistakes:

• Thinking cache invalidation increases cache size
• Believing cache never expires
• Confusing cache invalidation with disabling cache

2. Which Django cache method is used to remove a specific cached item?

easy

A. cache.delete()

B. cache.clear()

C. cache.set()

D. cache.get()

Solution

1. Step 1: Recall Django cache methods

   cache.delete() removes a specific key from the cache, clearing that cached item.

2. Step 2: Differentiate from other methods

   cache.clear() removes all cache, cache.set() adds data, cache.get() retrieves data.

3. Final Answer:

   cache.delete() -> Option A

4. Quick Check:

   Remove specific cache = cache.delete() [OK]

Hint: Use cache.delete() to remove one cached item [OK]

Common Mistakes:

• Using cache.clear() to remove one item
• Confusing cache.set() with deletion
• Trying to delete cache with cache.get()

3. Given this code snippet, what will be the output if the cache key 'user_1' is deleted before retrieval?

from django.core.cache import cache
cache.set('user_1', 'Alice', timeout=300)
cache.delete('user_1')
result = cache.get('user_1', 'Not Found')
print(result)

medium

A. Not Found

B. Alice

C. None

D. Error

Solution

1. Step 1: Analyze cache.set and cache.delete calls

   The key 'user_1' is set to 'Alice' but then immediately deleted from cache.

2. Step 2: Check cache.get behavior after deletion

   Since 'user_1' was deleted, cache.get returns the default value 'Not Found'.

3. Final Answer:

   Not Found -> Option A

4. Quick Check:

   Deleted key returns default value [OK]

Hint: Deleted cache keys return default on get [OK]

Common Mistakes:

• Expecting 'Alice' after deletion
• Assuming cache.get returns None by default
• Thinking deletion causes error

4. Identify the error in this Django cache invalidation code:

from django.core.cache import cache
cache.set('page_data', 'content', timeout=600)
cache.delete('page_data')
cache.delete('page_data')

medium

A. cache.set() must be called after cache.delete()

B. cache.delete() requires a timeout argument

C. Deleting the same key twice causes an error

D. No error; deleting a non-existent key is safe

Solution

1. Step 1: Understand cache.delete behavior

   Deleting a key that does not exist does not cause an error in Django cache.

2. Step 2: Check the code sequence

   First delete removes 'page_data', second delete tries to remove it again safely without error.

3. Final Answer:

   No error; deleting a non-existent key is safe -> Option D

4. Quick Check:

   Deleting missing key is safe [OK]

Hint: Deleting missing cache keys is safe [OK]

Common Mistakes:

• Thinking deleting twice causes error
• Believing cache.delete needs timeout
• Assuming cache.set must follow delete

5. You want to ensure cached user profile data expires automatically after 10 minutes but also want to manually clear it when the user updates their profile. Which cache invalidation strategy combination is best?

hard

A. Use cache.clear() to remove all cache every 10 minutes

B. Only use cache.set() with timeout=600, no manual deletion

C. Use cache.set() with timeout=600 and call cache.delete() on profile update

D. Only use cache.delete() without timeout

Solution

1. Step 1: Understand automatic expiration

   Setting timeout=600 (10 minutes) makes cache auto-expire after that time.

2. Step 2: Understand manual invalidation need

   Calling cache.delete() on profile update removes stale cached data immediately.

3. Step 3: Combine both strategies

   Using both timeout and manual delete ensures fresh data and timely expiration.

4. Final Answer:

   Use cache.set() with timeout=600 and call cache.delete() on profile update -> Option C

5. Quick Check:

   Timeout + manual delete = best strategy [OK]

Hint: Combine timeout and manual delete for fresh cache [OK]

Common Mistakes:

• Relying only on timeout causes stale data after update
• Using cache.clear() removes all cache unnecessarily
• Deleting without timeout loses auto-expiration benefit