Why caching matters for performance in Django - Visual Breakdown

Concept Flow - Why caching matters for performance

User Request

↓

Check Cache

↓

Return Cached

↓

Store Result in Cache

↓

Return Response

When a user makes a request, the system first checks if the response is in cache. If yes, it returns cached data fast. If no, it processes the request, stores the result in cache, then returns it.

Execution Sample

Django

from django.core.cache import cache

def get_data():
    data = cache.get('key')
    if data is None:
        data = expensive_query()
        cache.set('key', data, 60)
    return data

This code tries to get data from cache. If missing, it runs a slow query, saves the result in cache for 60 seconds, then returns it.

Execution Table

Step	Action	Cache State Before	Cache Hit?	Data Retrieved	Cache State After
1	Call get_data()	Empty	No	Run expensive_query()	Cache set with key:data
2	Call get_data() again	Cache has key:data	Yes	Return cached data	Cache unchanged
3	Cache expires after 60s	Cache empty	No	Run expensive_query()	Cache set with key:data

💡 Cache hit returns data immediately; cache miss triggers slow query and cache update

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
data	None	Result of expensive_query()	Cached data	Result of expensive_query()

Key Moments - 2 Insights

Why does the code run expensive_query() only sometimes?

Because the cache is checked first (see execution_table step 1 and 2). If data is in cache (step 2), it returns immediately without running expensive_query().

What happens when the cache expires?

When cache expires (step 3), cache.get returns None, so expensive_query() runs again and cache is updated.

Visual Quiz - 3 Questions

Look at the execution_table, what is the cache state before the second call to get_data()?

A Cache is being updated

B Cache has key:data

C Cache is empty

D Cache is corrupted

💡 Hint

Check execution_table row 2, column 'Cache State Before'

At which step does the expensive_query() function run?

A Step 2 only

B Step 3 only

C Step 1 and Step 3

D Never

💡 Hint

Look at execution_table rows 1 and 3 under 'Data Retrieved'

If cache.set duration was increased, how would the execution_table change?

A Step 3 would happen later or not at all

B Step 1 would be skipped

C Cache would never be empty

D expensive_query() would run every time

💡 Hint

Consider when cache expires in execution_table step 3

Concept Snapshot

Caching stores results of slow operations.
On request, check cache first.
If cached, return fast.
If not, run slow code, save result.
Improves performance by avoiding repeats.

Full Transcript

When a user requests data, Django first checks if the data is in cache. If it is, Django returns the cached data immediately, making the response fast. If not, Django runs a slow operation like a database query, then saves the result in cache for future requests. This process repeats, so the slow operation only runs when needed. Cache expiration means the data is refreshed after some time. This method improves performance by reducing repeated slow work.

Practice

1. Why is caching important for a Django website's performance?

easy

A. It makes the website load new data every time

B. It deletes all data to free up space immediately

C. It slows down the server to prevent overload

D. It stores data temporarily to avoid repeating expensive operations

Solution

1. Step 1: Understand caching purpose

   Caching saves results of expensive operations temporarily.

2. Step 2: Recognize performance benefit

   By reusing saved data, the server avoids repeating work, speeding up responses.

3. Final Answer:

   It stores data temporarily to avoid repeating expensive operations -> Option D

4. Quick Check:

   Caching = Temporary storage for speed [OK]

Hint: Caching saves time by reusing data, not recalculating [OK]

Common Mistakes:

• Thinking caching deletes data immediately
• Believing caching slows down the server
• Assuming caching always loads fresh data

2. Which of the following is the correct way to set a cache value in Django using the low-level cache API?

easy

A. cache.add('key', 'value', 300)

B. cache.set('key', 'value', timeout=300)

C. cache.save('key', 'value', 300)

D. cache.put('key', 'value', timeout=300)

Solution

1. Step 1: Recall Django cache API method

   The correct method to store a value is cache.set(key, value, timeout).

2. Step 2: Check method parameters

   cache.set uses named timeout parameter, unlike add or put which are incorrect here.

3. Final Answer:

   cache.set('key', 'value', timeout=300) -> Option B

4. Quick Check:

   cache.set() stores cache with timeout [OK]

Hint: Remember: cache.set(key, value, timeout) is standard [OK]

Common Mistakes:

• Using cache.add which only adds if key missing
• Using non-existent methods like cache.save or cache.put
• Passing timeout as positional instead of named argument

3. Given this Django view code snippet, what will be printed if the cache is empty initially?

from django.core.cache import cache

def my_view(request):
    count = cache.get('count', 0)
    count += 1
    cache.set('count', count, timeout=60)
    print(count)

medium

A. 1

B. None

C. 0

D. Error

Solution

1. Step 1: Understand cache.get default

   cache.get('count', 0) returns 0 if 'count' is not in cache.

2. Step 2: Increment and set cache

   count is incremented to 1, then saved back to cache and printed.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Empty cache default 0 + 1 = 1 [OK]

Hint: cache.get with default returns default if key missing [OK]

Common Mistakes:

• Assuming cache.get returns None if missing
• Expecting printed value to be 0 without increment
• Thinking code raises error on missing key

4. This Django code tries to cache a complex object but causes an error:

from django.core.cache import cache

class MyObject:
    def __init__(self, value):
        self.value = value

obj = MyObject(10)
cache.set('obj', obj, timeout=300)

What is the likely cause of the error?

medium

A. Timeout value must be a string, not integer

B. cache.set requires a string value only

C. The object is not serializable for caching

D. MyObject class must inherit from Django model

Solution

1. Step 1: Understand cache storage requirements

   Django cache backends usually require cached data to be serializable (e.g., picklable).

2. Step 2: Check object serializability

   Custom class instances like MyObject may not be serializable by default, causing errors.

3. Final Answer:

   The object is not serializable for caching -> Option C

4. Quick Check:

   Non-serializable objects cause cache errors [OK]

Hint: Cache only serializable data like strings or dicts [OK]

Common Mistakes:

• Thinking cache only accepts strings
• Believing timeout must be string
• Assuming class must be Django model to cache

5. You want to improve your Django app's homepage speed by caching the rendered HTML for 5 minutes. Which approach best achieves this while ensuring users see updated content after 5 minutes?

hard

A. Use Django's cache_page decorator with timeout=300 on the homepage view

B. Manually save HTML to a file and serve it without cache expiration

C. Cache only database queries but not the rendered HTML

D. Disable caching to always show fresh content

Solution

1. Step 1: Identify caching method for full page

   Django's cache_page decorator caches the entire view output for a set time.

2. Step 2: Confirm timeout and freshness

   Setting timeout=300 caches for 5 minutes, then refreshes automatically.

3. Step 3: Evaluate other options

   Manual file caching lacks expiration; caching only queries misses full page speed; disabling cache loses performance.

4. Final Answer:

   Use Django's cache_page decorator with timeout=300 on the homepage view -> Option A

5. Quick Check:

   cache_page with timeout = best for timed full page cache [OK]

Hint: Use cache_page decorator with timeout for full page caching [OK]

Common Mistakes:

• Caching only queries but not full page
• Serving static files without expiration
• Disabling cache thinking it improves freshness