Receiver decorator in Django - Performance & Optimization

Performance: Receiver decorator

MEDIUM IMPACT

This affects the event handling and signal processing speed in Django applications, impacting responsiveness during runtime.

Connecting signal handlers in Django

Django

from django.db.models.signals import post_save
from django.dispatch import receiver

@receiver(post_save)
def my_handler(sender, **kwargs):
    print('Signal received')

The receiver decorator ensures a single, clear connection to the signal, preventing duplicate calls and improving efficiency.

📈 Performance GainSingle signal connection reduces redundant processing and improves input responsiveness.

Connecting signal handlers in Django

Django

from django.db.models.signals import post_save
from django.dispatch import Signal

def my_handler(sender, **kwargs):
    print('Signal received')

post_save.connect(my_handler)

Manually connecting signals can lead to multiple connections if done repeatedly, causing duplicate handler calls and slower response.

📉 Performance CostTriggers multiple signal handler calls, increasing CPU usage and slowing interaction responsiveness.

Performance Comparison

Pattern	Signal Connections	Duplicate Calls	CPU Usage	Verdict
Manual connect() calls in multiple places	Multiple	Yes	High	[X] Bad
Using @receiver decorator once per handler	Single	No	Low	[OK] Good

Rendering Pipeline

The receiver decorator registers signal handlers during app initialization, affecting how Django processes signals during runtime events.

→Signal Registration

→Signal Dispatch

→Handler Execution

⚠️ BottleneckHandler Execution when multiple redundant handlers run

Core Web Vital Affected

INP

This affects the event handling and signal processing speed in Django applications, impacting responsiveness during runtime.

Optimization Tips

1Use @receiver decorator to connect signals once and avoid duplicates.

2Avoid manual signal connections scattered across code to prevent multiple handler calls.

3Efficient signal handling improves input responsiveness (INP) in Django apps.

Performance Quiz - 3 Questions

What is a performance benefit of using the @receiver decorator in Django?

A It reduces the size of static files.

B It automatically caches database queries.

C It prevents multiple signal connections and duplicate handler calls.

D It speeds up template rendering.

DevTools: Django Debug Toolbar

How to check: Enable the signals panel in Django Debug Toolbar and trigger the event; observe how many times the handler runs.

What to look for: Multiple handler calls indicate redundant connections; a single call confirms efficient signal handling.

Practice

1. What is the main purpose of the @receiver decorator in Django?

easy

A. To register a template filter

B. To create a new database model

C. To connect a function to a signal so it runs automatically when the signal is sent

D. To define a URL route in Django

Solution

1. Step 1: Understand what signals do in Django

   Signals notify parts of your app when something happens, like saving a model.

2. Step 2: Role of the @receiver decorator

   The decorator links a function to a signal so it runs automatically when the signal is sent.

3. Final Answer:

   To connect a function to a signal so it runs automatically when the signal is sent -> Option C

4. Quick Check:

   Receiver decorator connects functions to signals = D [OK]

Hint: Receiver links functions to signals for automatic execution [OK]

Common Mistakes:

• Confusing receiver with model or URL definitions
• Thinking receiver creates models or templates
• Mixing up signals with URL routing

2. Which of the following is the correct syntax to use the @receiver decorator for the post_save signal of a model named Book?

easy

A. @receiver(post_save, sender=Book)
def my_handler(sender, instance, **kwargs):
pass

B. @receiver(post_save(Book))
def my_handler(sender, instance, **kwargs):
pass

C. @receiver(sender=Book, post_save)
def my_handler(sender, instance, **kwargs):
pass

D. @receiver(post_save)
def my_handler(Book, instance, **kwargs):
pass

Solution

1. Step 1: Check the correct decorator syntax

   The @receiver decorator takes the signal as first argument and sender=ModelName as keyword argument.

2. Step 2: Match the correct function signature

   The handler function must accept sender, instance, and **kwargs.

3. Final Answer:

   @receiver(post_save, sender=Book) def my_handler(sender, instance, **kwargs): pass -> Option A

4. Quick Check:

   Correct decorator syntax = C [OK]

Hint: Use @receiver(signal, sender=Model) syntax [OK]

Common Mistakes:

• Passing sender as positional argument
• Incorrect function parameters
• Missing sender keyword argument

3. Given this code snippet, what will be printed when a Book instance is saved?

from django.db.models.signals import post_save
from django.dispatch import receiver

@receiver(post_save, sender=Book)
def notify(sender, instance, **kwargs):
    print(f"Book saved: {instance.title}")

book = Book(title='Django Basics')
book.save()

medium

A. Book saved: None

B. Error: receiver not connected

C. No output printed

D. Book saved: Django Basics

Solution

1. Step 1: Understand the signal connection

   The @receiver decorator connects notify to post_save for Book.

2. Step 2: What happens on book.save()?

   Saving the book triggers post_save, calling notify, which prints the book's title.

3. Final Answer:

   Book saved: Django Basics -> Option D

4. Quick Check:

   post_save triggers print with instance title = B [OK]

Hint: post_save calls receiver printing instance data [OK]

Common Mistakes:

• Assuming no output without explicit call
• Confusing instance attribute access
• Thinking receiver needs manual call

4. Identify the error in this signal receiver code:

from django.db.models.signals import post_save
from django.dispatch import receiver

@receiver(post_save, sender=Author)
def handle_save(instance, **kwargs):
    print(f"Author saved: {instance.name}")

medium

A. Incorrect decorator usage, should not use sender

B. Missing sender parameter in function definition

C. Function name must be post_save_handler

D. No error, code is correct

Solution

1. Step 1: Check function parameters for signal handlers

   Signal handlers must accept sender, instance, and **kwargs.

2. Step 2: Identify missing parameter

   The function handle_save lacks the sender parameter, causing an error.

3. Final Answer:

   Missing sender parameter in function definition -> Option B

4. Quick Check:

   Signal handler must have sender parameter = A [OK]

Hint: Signal handlers need sender, instance, **kwargs parameters [OK]

Common Mistakes:

• Omitting sender parameter
• Wrong function signature order
• Assuming function name matters

5. You want to run a function only when a User model instance is created (not updated). How do you use the @receiver decorator with post_save to achieve this?

hard

A. @receiver(post_save, sender=User)
def user_created(sender, instance, created, **kwargs):
if created:
print('New user created')

B. @receiver(post_save, sender=User)
def user_created(sender, instance, **kwargs):
print('New user created')

C. @receiver(post_save, sender=User)
def user_created(sender, instance, created=False, **kwargs):
if created == False:
print('New user created')

D. @receiver(post_save, sender=User)
def user_created(sender, instance, **kwargs):
if not created:
print('New user created')

Solution

1. Step 1: Understand the created flag in post_save

   The post_save signal passes a created boolean indicating if the instance was newly created.

2. Step 2: Use created to run code only on creation

   Check if created: inside the receiver function to run code only when a new instance is created.

3. Final Answer:

   @receiver(post_save, sender=User) def user_created(sender, instance, created, **kwargs): if created: print('New user created') -> Option A

4. Quick Check:

   Use created flag in post_save receiver = A [OK]

Hint: Check 'created' flag in post_save receiver to detect new instances [OK]

Common Mistakes:

• Ignoring the created parameter
• Checking created incorrectly
• Missing created parameter in function