Task retry and error handling in Django - Performance & Optimization

Performance: Task retry and error handling

MEDIUM IMPACT

This affects backend task execution speed and user experience by controlling how failed tasks are retried and errors are handled.

Retrying failed background tasks in Django

Django

from celery import shared_task

@shared_task(bind=True, max_retries=3, default_retry_delay=10)
def process_task(self):
    try:
        # task logic
        pass
    except Exception as exc:
        raise self.retry(exc=exc)

Uses Celery's built-in retry with limits and delays, avoiding blocking and infinite loops.

📈 Performance GainNon-blocking retries, limited attempts, better resource use

Retrying failed background tasks in Django

Django

from time import sleep

def process_task():
    try:
        # task logic
        pass
    except Exception:
        sleep(10)  # naive retry delay
        process_task()  # recursive retry without limit

This causes blocking delays and potential infinite recursion, leading to high CPU and memory use.

📉 Performance CostBlocks worker thread, can cause memory leaks and high CPU usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking recursive retry	0	0	0	[X] Bad
Asynchronous retry with limits (Celery)	0	0	0	[OK] Good

Rendering Pipeline

Task retry and error handling occur on the backend and do not directly affect browser rendering but impact user experience by controlling response times and error visibility.

→Backend Task Execution

→Response Time

⚠️ BottleneckBlocking retries or unhandled errors can delay task completion and increase server load.

Optimization Tips

1Avoid blocking retries that freeze worker threads.

2Use asynchronous retry mechanisms with limits and delays.

3Catch errors properly to prevent crashes and resource leaks.

Performance Quiz - 3 Questions

What is a major performance risk of using blocking recursive retries in Django task handling?

A It improves task completion speed by retrying immediately.

B It can cause high CPU and memory usage due to blocking and infinite recursion.

C It reduces server load by limiting retries.

D It automatically handles errors without developer input.

DevTools: Network and Performance panels

How to check: Use Network panel to monitor API response times and Performance panel to check UI responsiveness during backend retries.

What to look for: Look for long response times or repeated failed requests indicating inefficient retry or error handling.