Task results and status in Django - Performance & Optimization

Performance: Task results and status

MEDIUM IMPACT

This concept affects how quickly users see task completion feedback and how efficiently the server handles background task updates.

Updating task status on the frontend after a background task completes

Django

def start_task_view(request):
    task = background_task.delay()
    return JsonResponse({'task_id': task.id, 'status': 'started'})

# Frontend polls or uses WebSocket to get status updates asynchronously

Starts task asynchronously and immediately responds, allowing UI to stay responsive while polling for updates.

📈 Performance GainNon-blocking response, reduces input delay, improves INP metric.

Updating task status on the frontend after a background task completes

Django

def task_view(request):
    result = long_running_task()
    return JsonResponse({'status': 'done', 'result': result})

This blocks the request until the task finishes, delaying response and freezing the UI.

📉 Performance CostBlocks rendering for the entire task duration, causing high INP and poor user experience.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous task execution in request	Minimal DOM changes	0 reflows during task but blocks response	Delayed paint due to blocking	[X] Bad
Asynchronous task with polling or WebSocket	Incremental DOM updates on status change	1 reflow per update	Smooth paint with small incremental changes	[OK] Good

Rendering Pipeline

Task status updates flow from server to client asynchronously, avoiding blocking the main thread and allowing smooth UI updates.

→Network

→JavaScript Execution

→Paint

→Composite

⚠️ BottleneckBlocking synchronous task execution delays network response and JavaScript updates.

Core Web Vital Affected

INP

This concept affects how quickly users see task completion feedback and how efficiently the server handles background task updates.

Optimization Tips

1Never block HTTP responses with long-running tasks.

2Use asynchronous task queues like Celery for background processing.

3Update task status asynchronously via polling or WebSocket to keep UI responsive.

Performance Quiz - 3 Questions

What is the main performance problem with running a long task synchronously in a Django view?

A It blocks the response, causing high input delay and poor user experience.

B It increases the bundle size of the frontend assets.

C It causes excessive CSS recalculations.

D It triggers multiple layout shifts on the page.

DevTools: Performance

How to check: Record a session while triggering a task and observe the Main thread activity and network requests for blocking or asynchronous behavior.

What to look for: Look for long tasks blocking the main thread and delayed network responses indicating synchronous blocking.

Practice

1. In Django with Celery, which object do you use to check the status and result of a background task by its ID?

easy

A. AsyncResult

B. TaskStatus

C. TaskResult

D. ResultChecker

Solution

1. Step 1: Identify the object for task tracking

   Celery provides AsyncResult to track task status and results using the task ID.

2. Step 2: Confirm usage in Django context

   In Django projects using Celery, AsyncResult is the standard way to check if a task is pending, running, or finished.

3. Final Answer:

   AsyncResult -> Option A

4. Quick Check:

   Task status and results = AsyncResult [OK]

Hint: Remember: AsyncResult tracks task status by ID [OK]

Common Mistakes:

• Confusing AsyncResult with task function names
• Using non-existent classes like TaskStatus
• Trying to access results directly without AsyncResult

2. Which of the following is the correct way to create an AsyncResult instance for a task with ID stored in task_id?

easy

A. result = AsyncResult(task=task_id)

B. result = AsyncResult.get(task_id)

C. result = AsyncResult.fetch(task_id)

D. result = AsyncResult(task_id)

Solution

1. Step 1: Recall AsyncResult constructor usage

   The AsyncResult class is instantiated by passing the task ID as the first argument.

2. Step 2: Check each option's syntax

   Only AsyncResult(task_id) correctly creates the instance. Methods like .get() or .fetch() are not constructors.

3. Final Answer:

   result = AsyncResult(task_id) -> Option D

4. Quick Check:

   Instantiate AsyncResult with task ID directly [OK]

Hint: Use AsyncResult(task_id) to create result object [OK]

Common Mistakes:

• Calling get() or fetch() as constructor
• Passing keyword argument 'task' instead of positional
• Confusing AsyncResult with task function calls

3. Given the code:

result = AsyncResult('abc123')
status = result.status
output = result.result

What will status and output represent if the task is still running?

medium

A. status is 'PENDING', output is None

B. status is 'RUNNING', output is None

C. status is 'FAILURE', output is the error info

D. status is 'SUCCESS', output is the task result

Solution

1. Step 1: Understand AsyncResult status values

   By default, while a task is running without calling update_state inside the task, result.status remains 'PENDING'.

2. Step 2: Check result property during running

   result.result returns None until the task completes.

3. Final Answer:

   status is 'PENDING', output is None -> Option A

4. Quick Check:

   Running task (default): status='PENDING', result=None [OK]

Hint: Default running tasks show status 'PENDING' and result None [OK]

Common Mistakes:

• Mistaking for 'RUNNING' status (doesn't exist)
• Confusing with 'STARTED' which requires explicit update_state
• Thinking result is available before completion

4. You wrote:

result = AsyncResult(task_id)
if result.status == 'SUCCESS':
    print(result.result)
else:
    print('Task not done')

But it always prints 'Task not done' even after task completion. What is the likely issue?

medium

A. You must call result.get() instead of accessing result.result

B. You should check for 'COMPLETED' instead of 'SUCCESS'

C. The task ID is incorrect or expired

D. AsyncResult does not have a status attribute

Solution

1. Step 1: Understand status checking logic

   The code checks if result.status equals 'SUCCESS' to print the result.

2. Step 2: Identify why status never shows 'SUCCESS'

   If the task ID is wrong or expired, AsyncResult will not find the task and status stays 'PENDING' or similar.

3. Final Answer:

   The task ID is incorrect or expired -> Option C

4. Quick Check:

   Wrong task ID causes status never to be 'SUCCESS' [OK]

Hint: Check task ID validity if status never changes [OK]

Common Mistakes:

• Using wrong status string like 'COMPLETED'
• Assuming result.result always updates without completion
• Ignoring task ID correctness

5. You want to handle a task result in Django only if it succeeded, otherwise log the error. Which code snippet correctly checks the task status and safely accesses the result or error?

hard

A. result = AsyncResult(task_id)
if result.ready():
handle(result.result)
else:
log_error('Task not ready')

B. result = AsyncResult(task_id)
try:
handle(result.get(timeout=1))
except Exception as e:
log_error(e)

C. result = AsyncResult(task_id)
if result.status == 'PENDING':
handle(result.result)
else:
log_error('Task failed')

D. result = AsyncResult(task_id)
if result.status == 'SUCCESS':
handle(result.result)
elif result.status == 'FAILURE':
log_error(result.get())

Solution

1. Step 1: Understand safe result retrieval

   Using result.get() with a timeout waits for completion and raises exceptions on failure.

2. Step 2: Check error handling approach

   Wrapping result.get() in try-except catches task failures and allows logging errors safely.

3. Step 3: Compare other options

   Options B, C, and D do not handle exceptions properly; C incorrectly treats 'PENDING' as success.

4. Final Answer:

   Use try-except with result.get() to handle success and failure -> Option B

5. Quick Check:

   Use result.get() with try-except for safe task result handling [OK]

Hint: Use try-except with result.get() to catch errors [OK]

Common Mistakes:

• Checking only status strings without exception handling
• Assuming ready() means success
• Treating PENDING as success