Task queue concept in Flask - Performance & Optimization

Performance: Task queue concept

HIGH IMPACT

Task queues affect how background tasks are handled, improving page responsiveness and reducing server blocking during user requests.

Handling long-running tasks in a Flask web app

Flask

from flask import Flask, request, jsonify
from celery import Celery

app = Flask(__name__)
celery = Celery(app.name, broker='redis://localhost:6379/0')

@celery.task
def long_task():
    import time
    time.sleep(10)
    return 'done'

@app.route('/process')
def process():
    task = long_task.delay()
    return jsonify({'task_id': task.id, 'status': 'processing'})

The long task runs asynchronously in a worker, freeing the web server to respond immediately.

📈 Performance GainNon-blocking request, reduces INP drastically, improves user experience.

Handling long-running tasks in a Flask web app

Flask

from flask import Flask, request
app = Flask(__name__)

@app.route('/process')
def process():
    # Long task runs directly in request
    result = long_task()
    return f"Result: {result}"

def long_task():
    import time
    time.sleep(10)  # Simulates a slow task
    return 'done'

The long task blocks the request thread, causing slow response and poor user experience.

📉 Performance CostBlocks rendering and response for 10 seconds, causing high INP and poor LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous long task in request	Minimal	N/A	Blocks paint until task completes	[X] Bad
Asynchronous task queue with Celery	Minimal	N/A	Immediate paint, task runs in background	[OK] Good

Rendering Pipeline

Without a task queue, long tasks block the request thread, delaying response and browser rendering. With a task queue, the server quickly responds, allowing the browser to paint and interact sooner.

→Request Handling

→Response Time

→Interaction to Next Paint (INP)

⚠️ BottleneckRequest Handling blocks due to synchronous long tasks.

Core Web Vital Affected

INP

Task queues affect how background tasks are handled, improving page responsiveness and reducing server blocking during user requests.

Optimization Tips

1Offload long-running tasks to background workers to keep the server responsive.

2Avoid blocking request threads with synchronous heavy processing.

3Use task queues like Celery with Redis or RabbitMQ for scalable background jobs.

Performance Quiz - 3 Questions

What is the main performance benefit of using a task queue in a Flask app for long-running tasks?

A It improves CSS selector performance.

B It prevents the web server from blocking during requests.

C It reduces the size of the Flask app bundle.

D It decreases the number of DOM nodes.

DevTools: Performance

How to check: Record a performance profile while triggering the long task endpoint; observe main thread blocking time and responsiveness.

What to look for: Look for long tasks blocking the main thread and delayed first input response indicating poor INP.

Practice

1. What is the main purpose of using a task queue in a Flask application?

easy

A. To serve static files faster

B. To run slow or long tasks in the background without blocking the main app

C. To handle user authentication securely

D. To speed up the Flask app by caching all responses

Solution

1. Step 1: Understand task queue role

   Task queues let slow jobs run separately from the main app, so the app stays responsive.

2. Step 2: Identify the correct purpose

   Running slow tasks in the background matches the main purpose of task queues.

3. Final Answer:

   To run slow or long tasks in the background without blocking the main app -> Option B

4. Quick Check:

   Task queue purpose = background slow jobs [OK]

Hint: Task queues handle slow jobs outside main app flow [OK]

Common Mistakes:

• Confusing task queues with caching
• Thinking task queues handle authentication
• Assuming task queues speed up static file serving

2. Which of the following is the correct way to enqueue a task using rq in Flask?

easy

A. queue.enqueue(my_task, arg1, arg2)

B. queue.run(my_task, arg1, arg2)

C. queue.start(my_task, arg1, arg2)

D. queue.execute(my_task, arg1, arg2)

Solution

1. Step 1: Recall rq enqueue method

   In rq, tasks are added to the queue using the enqueue() method.

2. Step 2: Match method to options

   Only queue.enqueue(my_task, arg1, arg2) uses enqueue() correctly with task and arguments.

3. Final Answer:

   queue.enqueue(my_task, arg1, arg2) -> Option A

4. Quick Check:

   rq enqueue method = enqueue() [OK]

Hint: Use enqueue() to add tasks to rq queue [OK]

Common Mistakes:

• Using run(), start(), or execute() instead of enqueue()
• Forgetting to pass task arguments
• Calling enqueue on wrong object

3. Given this Flask rq task code snippet:

from rq import Queue
from redis import Redis

redis_conn = Redis()
queue = Queue(connection=redis_conn)

def add(x, y):
    return x + y

job = queue.enqueue(add, 3, 4)
print(job.result)

What will be printed immediately after running this code?

medium

A. None

B. 7

C. Error: job.result not available

D. 3 + 4

Solution

1. Step 1: Understand rq job processing

   When a job is enqueued, it runs asynchronously. The result is not ready immediately.

2. Step 2: Check job.result value right after enqueue

   Immediately after enqueue, job.result is None because the worker hasn't processed it yet.

3. Final Answer:

   None -> Option A

4. Quick Check:

   job.result before worker runs = None [OK]

Hint: job.result is None until worker finishes task [OK]

Common Mistakes:

• Assuming job.result is ready immediately
• Expecting synchronous return value
• Confusing job.result with function return

4. You wrote this code to enqueue a task in Flask with rq:

queue.enqueue(my_task, arg1, arg2)

But the task never runs. What is the most likely reason?

medium

A. Redis server is not installed

B. The task function my_task is missing

C. You forgot to start the rq worker process

D. You used enqueue instead of run

Solution

1. Step 1: Check rq worker role

   rq worker must be running to process tasks from the queue.

2. Step 2: Identify missing worker

   If tasks never run, the worker process is likely not started.

3. Final Answer:

   You forgot to start the rq worker process -> Option C

4. Quick Check:

   Worker must run to process tasks [OK]

Hint: Always run rq worker to process queued tasks [OK]

Common Mistakes:

• Assuming enqueue runs task immediately
• Not starting rq worker process
• Confusing Redis installation with worker running

5. You want to run a slow image processing function in the background using Flask and rq. Which combination correctly sets up the task queue and worker?

hard

A. Install Redis, but only enqueue tasks; worker runs automatically without command

B. Create Flask app, call task function directly; no need for Redis or worker

C. Use Flask's built-in threading to run task; no Redis or rq needed

D. Create Redis connection, create rq Queue with it, enqueue task; run rq worker in terminal

Solution

1. Step 1: Setup Redis and rq Queue

   You must create a Redis connection and pass it to rq Queue to enqueue tasks properly.

2. Step 2: Run rq worker separately

   The rq worker must be started manually in the terminal to process queued tasks.

3. Final Answer:

   Create Redis connection, create rq Queue with it, enqueue task; run rq worker in terminal -> Option D

4. Quick Check:

   Redis + rq Queue + worker process = correct setup [OK]

Hint: Redis + rq Queue + manual worker run = background tasks [OK]

Common Mistakes:

• Calling task function directly instead of enqueueing
• Assuming worker runs automatically
• Using Flask threading instead of task queue