Background file processing in FastAPI - Performance & Optimization

Performance: Background file processing

HIGH IMPACT

This concept affects page load speed and interaction responsiveness by offloading heavy file processing tasks from the main request thread.

Processing large uploaded files without blocking the main request

FastAPI

from fastapi import FastAPI, UploadFile, BackgroundTasks

app = FastAPI()

def heavy_processing(content: bytes):
    # Process file in background
    pass

@app.post('/upload')
async def upload(file: UploadFile, background_tasks: BackgroundTasks):
    content = await file.read()
    background_tasks.add_task(heavy_processing, content)
    return {'status': 'processing started'}

File processing runs in background, allowing immediate response and better user experience.

📈 Performance GainResponse returns immediately, improving INP and reducing user wait.

Processing large uploaded files without blocking the main request

FastAPI

from fastapi import FastAPI, UploadFile

app = FastAPI()

@app.post('/upload')
async def upload(file: UploadFile):
    content = await file.read()
    # Process file synchronously here
    result = heavy_processing(content)
    return {'status': 'done', 'result': result}

Heavy file processing blocks the request, delaying response and causing poor interaction responsiveness.

📉 Performance CostBlocks response for entire processing time, increasing INP and user wait time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous file processing in request	N/A	N/A	Blocks response, delays paint	[X] Bad
Background file processing with BackgroundTasks	N/A	N/A	Immediate response, no blocking	[OK] Good

Rendering Pipeline

Background file processing removes heavy tasks from the main request thread, allowing the server to respond quickly and the browser to render the page without delay.

→Server Processing

→Response Time

→User Interaction

⚠️ BottleneckMain thread blocking during synchronous file processing

Core Web Vital Affected

INP

This concept affects page load speed and interaction responsiveness by offloading heavy file processing tasks from the main request thread.

Optimization Tips

1Always offload heavy file processing to background tasks to keep responses fast.

2Avoid synchronous file processing in request handlers to prevent blocking.

3Use FastAPI's BackgroundTasks to improve interaction responsiveness (INP).

Performance Quiz - 3 Questions

What is the main performance benefit of using background file processing in FastAPI?

A It reduces the file size before uploading.

B It allows the server to respond immediately without waiting for file processing.

C It improves CSS rendering speed.

D It caches the file on the client side.

DevTools: Network

How to check: Open DevTools > Network tab, upload a file and observe the response time for the upload request.

What to look for: Fast response time indicates background processing; long blocking time indicates synchronous processing.

Practice

1. What is the main benefit of using BackgroundTasks in FastAPI for file processing?

easy

A. It allows slow tasks to run after sending the response, keeping the app fast.

B. It automatically compresses files before saving.

C. It blocks the request until the file is fully processed.

D. It encrypts files during upload.

Solution

1. Step 1: Understand the role of BackgroundTasks

   BackgroundTasks in FastAPI lets you run tasks after the response is sent, so the user doesn't wait.

2. Step 2: Identify the benefit for file processing

   Running slow file processing in the background keeps the app responsive and fast for users.

3. Final Answer:

   It allows slow tasks to run after sending the response, keeping the app fast. -> Option A

4. Quick Check:

   BackgroundTasks = run slow tasks after response [OK]

Hint: BackgroundTasks run after response to keep app fast [OK]

Common Mistakes:

• Thinking BackgroundTasks block the response
• Assuming BackgroundTasks handle file encryption
• Believing BackgroundTasks compress files automatically

2. Which of the following is the correct way to add a background task for file processing in a FastAPI endpoint?

easy

A. def upload(file: UploadFile, background_tasks: BackgroundTasks): process_file(file)

B. def upload(file: UploadFile): process_file(file) background_tasks.add_task()

C. def upload(file: UploadFile): background_tasks = BackgroundTasks() process_file(file)

D. def upload(file: UploadFile, background_tasks: BackgroundTasks): background_tasks.add_task(process_file, file)

Solution

1. Step 1: Check function parameters

   To use BackgroundTasks, it must be a parameter in the endpoint function.

2. Step 2: Add the task correctly

   Use background_tasks.add_task(function, args) to schedule the task after response.

3. Final Answer:

   def upload(file: UploadFile, background_tasks: BackgroundTasks): background_tasks.add_task(process_file, file) -> Option D

4. Quick Check:

   Use add_task with BackgroundTasks parameter [OK]

Hint: Add tasks using background_tasks.add_task inside endpoint [OK]

Common Mistakes:

• Calling process_file directly inside endpoint
• Not including BackgroundTasks as a parameter
• Creating BackgroundTasks inside the function without adding tasks

3. Given this FastAPI code snippet, what will be the response behavior when a file is uploaded?

from fastapi import FastAPI, UploadFile, BackgroundTasks
app = FastAPI()

def save_file(file: UploadFile):
    with open(f"saved_{file.filename}", "wb") as f:
        f.write(file.file.read())

@app.post("/upload")
async def upload(file: UploadFile, background_tasks: BackgroundTasks):
    background_tasks.add_task(save_file, file)
    return {"message": "File upload started"}

medium

A. The response returns immediately with message, while file saving happens in background.

B. The response waits until the file is saved, then returns the message.

C. The file is saved before the response, but no message is returned.

D. The code will raise an error because file.file.read() is not allowed.

Solution

1. Step 1: Analyze background task usage

   The save_file function is added as a background task, so it runs after response.

2. Step 2: Understand response timing

   The endpoint returns the message immediately, without waiting for save_file to finish.

3. Final Answer:

   The response returns immediately with message, while file saving happens in background. -> Option A

4. Quick Check:

   BackgroundTasks run after response = immediate reply [OK]

Hint: BackgroundTasks run after response, so response is immediate [OK]

Common Mistakes:

• Assuming file saving blocks response
• Thinking file.file.read() causes error here
• Believing no message is returned

4. Identify the error in this FastAPI endpoint for background file processing:

from fastapi import FastAPI, UploadFile, BackgroundTasks
app = FastAPI()

def process_file(file: UploadFile):
    content = file.file.read()
    with open(f"processed_{file.filename}", "wb") as f:
        f.write(content)

@app.post("/upload")
async def upload(file: UploadFile, background_tasks: BackgroundTasks):
    background_tasks.add_task(process_file, file.file.read())
    return {"message": "Processing started"}

medium

A. Missing await keyword before background_tasks.add_task call.

B. Passing file.file.read() instead of file causes the file to be read too early.

C. process_file should be async but is defined as sync.

D. File is not saved before background task starts.

Solution

1. Step 1: Check argument passed to add_task

   The code passes file.file.read() which reads the file immediately, not the file object.

2. Step 2: Understand why this is a problem

   Reading the file before background task means the task gets raw bytes, not the file to read later, causing errors or empty data.

3. Final Answer:

   Passing file.file.read() instead of file causes the file to be read too early. -> Option B

4. Quick Check:

   Pass file object, not file.file.read() to background task [OK]

Hint: Pass file object, not file.file.read(), to background task [OK]

Common Mistakes:

• Thinking add_task needs await
• Believing process_file must be async
• Ignoring file saving order

5. You want to save an uploaded file immediately and then process it in the background. Which FastAPI code snippet correctly implements this pattern?

hard

A. async def upload(file: UploadFile, background_tasks: BackgroundTasks):
background_tasks.add_task(process_file, file)
return {"message": "Processing started"}

B. async def upload(file: UploadFile):
contents = await file.read()
with open(f"saved_{file.filename}", "wb") as f:
f.write(contents)
process_file(f"saved_{file.filename}")
return {"message": "File saved and processed"}

C. async def upload(file: UploadFile, background_tasks: BackgroundTasks):
contents = await file.read()
with open(f"saved_{file.filename}", "wb") as f:
f.write(contents)
background_tasks.add_task(process_file, f"saved_{file.filename}")
return {"message": "File saved and processing started"}

D. async def upload(file: UploadFile, background_tasks: BackgroundTasks):
background_tasks.add_task(process_file, file.file.read())
return {"message": "Processing started"}

Solution

1. Step 1: Save file before background processing

   The file is read and saved immediately using await file.read() and writing to disk.

2. Step 2: Add background task with saved filename

   The background task processes the saved file path, ensuring file exists before processing.

3. Final Answer:

   Save file first, then add background task with saved filename. -> Option C

4. Quick Check:

   Save file first, then background task with filename [OK]

Hint: Save file first, then add background task with filename [OK]

Common Mistakes:

• Adding background task before saving file
• Passing file.file.read() instead of file or filename
• Calling process_file synchronously inside endpoint