Gunicorn with Uvicorn workers in FastAPI - Performance & Optimization

Performance: Gunicorn with Uvicorn workers

HIGH IMPACT

This setup affects server request handling speed and concurrency, impacting how fast the API responds under load.

Serving a FastAPI app with multiple concurrent requests

FastAPI

gunicorn main:app -w 4 -k uvicorn.workers.UvicornWorker --bind 0.0.0.0:8000

Multiple Uvicorn worker processes handle requests concurrently, improving throughput and responsiveness.

📈 Performance GainEnables parallel request handling, reducing blocking and improving INP under load.

Serving a FastAPI app with multiple concurrent requests

FastAPI

uvicorn main:app --host 0.0.0.0 --port 8000

Single Uvicorn process handles all requests, limiting concurrency and blocking on slow operations.

📉 Performance CostBlocks event loop under heavy load, causing slow response times and poor INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single Uvicorn process	N/A (server-side)	N/A	N/A	[X] Bad
Gunicorn with multiple Uvicorn workers	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Requests enter Gunicorn master process, which distributes them to multiple Uvicorn worker processes. Each worker runs an async event loop to handle requests efficiently.

→Request Handling

→Concurrency Management

→Async Event Loop

⚠️ BottleneckSingle worker event loop blocking under heavy synchronous tasks

Core Web Vital Affected

INP

This setup affects server request handling speed and concurrency, impacting how fast the API responds under load.

Optimization Tips

1Use multiple Uvicorn workers with Gunicorn to handle concurrent requests.

2Avoid blocking the async event loop with synchronous code.

3Monitor response times under load to adjust worker count.

Performance Quiz - 3 Questions

What is the main benefit of using Gunicorn with Uvicorn workers for a FastAPI app?

A Decreases DOM node count on the client

B Reduces CSS paint cost in the browser

C Improves concurrency by running multiple async workers

D Blocks rendering until all requests complete

DevTools: Network

How to check: Open browser DevTools, go to Network tab, make multiple concurrent API requests, and observe response times.

What to look for: Look for consistent low response times and no request queuing delays indicating good concurrency.

Practice

1. What is the main reason to use Gunicorn with Uvicorn workers when running a FastAPI app?

easy

A. To convert FastAPI apps into desktop applications

B. To run FastAPI apps only in development mode

C. To automatically generate API documentation

D. To efficiently handle multiple requests asynchronously in production

Solution

1. Step 1: Understand Gunicorn and Uvicorn roles

   Gunicorn is a production server that manages multiple worker processes. Uvicorn is an async server that runs FastAPI apps efficiently.

2. Step 2: Combine Gunicorn with Uvicorn workers

   Using Gunicorn with Uvicorn workers allows handling many requests asynchronously and improves performance in production.

3. Final Answer:

   To efficiently handle multiple requests asynchronously in production -> Option D

4. Quick Check:

   Gunicorn + Uvicorn = async production efficiency [OK]

Hint: Gunicorn manages workers; Uvicorn handles async FastAPI [OK]

Common Mistakes:

• Thinking Gunicorn is only for development
• Confusing Uvicorn with API documentation tools
• Believing this setup creates desktop apps

2. Which of the following is the correct command to start a FastAPI app with 4 Uvicorn workers using Gunicorn?

easy

A. gunicorn -k uvicorn.workers.UvicornWorker -w main:app 4

B. uvicorn -w 4 -k gunicorn.workers.GunicornWorker main:app

C. gunicorn -w 4 -k uvicorn.workers.UvicornWorker main:app

D. uvicorn main:app -w 4 -k gunicorn.workers.GunicornWorker

Solution

1. Step 1: Identify Gunicorn command syntax

   Gunicorn uses '-w' to set workers and '-k' to specify worker class.

2. Step 2: Match correct worker class and app reference

   Uvicorn worker class is 'uvicorn.workers.UvicornWorker' and app is referenced as 'main:app'.

3. Final Answer:

   gunicorn -w 4 -k uvicorn.workers.UvicornWorker main:app -> Option C

4. Quick Check:

   Gunicorn -w 4 -k UvicornWorker main:app [OK]

Hint: Gunicorn uses -w for workers and -k for worker class [OK]

Common Mistakes:

• Using uvicorn command instead of gunicorn
• Swapping worker class names incorrectly
• Placing worker count after app name

3. Given this command: gunicorn -w 3 -k uvicorn.workers.UvicornWorker main:app, what will happen when the FastAPI app receives multiple simultaneous requests?

medium

A. Requests will be handled concurrently by 3 async workers improving throughput

B. Only one request will be handled at a time, others will wait

C. The app will crash because Gunicorn cannot run async workers

D. Requests will be queued but processed sequentially by a single worker

Solution

1. Step 1: Understand worker count and async support

   Gunicorn runs 3 workers, each using Uvicorn's async worker class to handle requests asynchronously.

2. Step 2: Effect on request handling

   Multiple requests can be handled concurrently by these 3 async workers, improving throughput and responsiveness.

3. Final Answer:

   Requests will be handled concurrently by 3 async workers improving throughput -> Option A

4. Quick Check:

   3 async workers = concurrent request handling [OK]

Hint: More workers + async = better concurrent handling [OK]

Common Mistakes:

• Assuming only one request at a time
• Thinking Gunicorn can't run async workers
• Believing requests queue without concurrency

4. You run gunicorn -w 2 -k uvicorn.workers.UvicornWorker app:app but get an error: ModuleNotFoundError: No module named 'uvicorn'. What is the likely cause?

medium

A. Uvicorn is not installed in the environment

B. Gunicorn does not support the -k option

C. The app module is missing

D. The worker count -w must be at least 4

Solution

1. Step 1: Analyze the error message

   The error says 'No module named uvicorn', indicating Python cannot find the uvicorn package.

2. Step 2: Check environment setup

   This usually means uvicorn is not installed in the current Python environment where Gunicorn runs.

3. Final Answer:

   Uvicorn is not installed in the environment -> Option A

4. Quick Check:

   Missing uvicorn package causes ModuleNotFoundError [OK]

Hint: Install uvicorn package to fix ModuleNotFoundError [OK]

Common Mistakes:

• Assuming Gunicorn lacks -k support
• Blaming app module instead of missing package
• Thinking worker count causes import errors

5. You want to deploy a FastAPI app with Gunicorn and Uvicorn workers on a server with 8 CPU cores. Which command best balances performance and resource use?

hard

A. gunicorn -w 8 -k uvicorn.workers.UvicornWorker main:app

B. gunicorn -w 4 -k uvicorn.workers.UvicornWorker main:app

C. gunicorn -w 16 -k uvicorn.workers.UvicornWorker main:app

D. gunicorn -w 1 -k uvicorn.workers.UvicornWorker main:app

Solution

1. Step 1: Understand worker count vs CPU cores

   Best practice is to use a moderate number of workers (such as 4) for async apps, but too many workers can cause overhead.

2. Step 2: Choose balanced worker count

   Using 4 workers on 8 cores balances concurrency and resource use without excessive context switching.

3. Final Answer:

   gunicorn -w 4 -k uvicorn.workers.UvicornWorker main:app -> Option B

4. Quick Check:

   4 workers on 8 cores = balanced performance [OK]

Hint: Use fewer workers than CPU cores for async apps [OK]

Common Mistakes:

• Using too many workers causing overhead
• Using only one worker limiting concurrency
• Matching workers exactly to CPU cores without buffer