Why caching matters for performance in Django - Performance Evidence

Performance: Why caching matters for performance

HIGH IMPACT

Caching reduces server processing time and speeds up page load by reusing stored data instead of recalculating it.

Serving dynamic page content efficiently

Django

from django.views.decorators.cache import cache_page

@cache_page(60 * 15)  # Cache for 15 minutes
def view(request):
    data = expensive_database_query()
    return render(request, 'template.html', {'data': data})

Caches the rendered page for 15 minutes, serving repeated requests instantly without rerunning the query.

📈 Performance GainReduces server processing time to near zero for cached requests, improving LCP significantly

Serving dynamic page content efficiently

Django

def view(request):
    data = expensive_database_query()
    return render(request, 'template.html', {'data': data})

Every request runs the expensive query causing slow response and high server load.

📉 Performance CostBlocks rendering for 200+ ms per request under load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No caching, full query on each request	N/A (server-side)	N/A	High due to slow server response	[X] Bad
Using Django cache_page decorator	N/A (server-side)	N/A	Low due to fast server response	[OK] Good

Rendering Pipeline

Caching bypasses repeated server-side data fetching and template rendering, delivering ready content quickly to the browser.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (database queries and template rendering)

Core Web Vital Affected

LCP

Caching reduces server processing time and speeds up page load by reusing stored data instead of recalculating it.

Optimization Tips

1Cache expensive computations or database queries to reduce server load.

2Use Django's cache_page decorator for easy view-level caching.

3Cached responses improve Largest Contentful Paint by delivering content faster.

Performance Quiz - 3 Questions

What is the main performance benefit of caching in Django views?

A Increases the number of database queries

B Reduces server processing time by reusing stored responses

C Makes the browser do more work rendering pages

D Adds extra delay to every request

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page and check response times for cached vs uncached requests.

What to look for: Look for significantly lower response time and smaller server processing time on cached requests.

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