Connecting signal handlers in Django - Performance & Optimization

Performance: Connecting signal handlers

MEDIUM IMPACT

This affects the server-side processing time and can indirectly impact page load speed by delaying response generation.

Registering signal handlers in Django applications

Django

from django.apps import AppConfig

class MyAppConfig(AppConfig):
    name = 'myapp'

    def ready(self):
        import myapp.signals  # connects handlers once

# In myapp/signals.py
from django.db.models.signals import post_save
from django.dispatch import receiver

@receiver(post_save, sender=MyModel)
def my_handler(sender, instance, **kwargs):
    # heavy processing here
    pass

Connecting signals once in AppConfig.ready ensures handlers run only once per event, reducing redundant processing.

📈 Performance GainSingle handler execution per event, reducing CPU usage and improving response time

Registering signal handlers in Django applications

Django

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

@receiver(post_save, sender=MyModel)
def my_handler(sender, instance, **kwargs):
    # heavy processing here
    pass

# Importing this module in multiple places triggers multiple connections

Connecting signal handlers multiple times causes the handler to run multiple times per event, increasing processing time.

📉 Performance CostTriggers multiple handler executions per event, increasing server CPU usage and response time

Performance Comparison

Pattern	Handler Calls	CPU Usage	Response Delay	Verdict
Multiple signal connections	Multiple per event	High	Increased	[X] Bad
Single connection in AppConfig.ready	One per event	Low	Minimal	[OK] Good

Rendering Pipeline

Signal handlers run during server request processing before the response is sent. Multiple connections cause repeated handler calls, increasing server CPU time and delaying response generation.

→Server Processing

→Response Generation

⚠️ BottleneckRepeated signal handler execution increases server CPU load and response time

Optimization Tips

1Connect signal handlers once during app startup, not per request.

2Use AppConfig.ready() to register signals safely.

3Avoid importing signal connection code in multiple modules.

Performance Quiz - 3 Questions

What is the main performance risk of connecting Django signal handlers multiple times?

A Signals stop working completely

B Handlers run multiple times per event, increasing server load

C Signals cause client-side rendering delays

D Signals increase database size

DevTools: Django Debug Toolbar / Logging

How to check: Enable Django Debug Toolbar or add logging in signal handlers to count how many times they run per request.

What to look for: Multiple handler executions per single event indicate redundant connections causing performance issues.