Gunicorn with Uvicorn workers in FastAPI - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run Gunicorn with Uvicorn workers for a FastAPI app?

You start a FastAPI app using Gunicorn with Uvicorn workers like this:

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

What is the expected behavior?

A Gunicorn crashes because it cannot use Uvicorn workers with FastAPI.

B Gunicorn runs a single process that handles all requests synchronously without async support.

C Uvicorn runs independently and Gunicorn only acts as a proxy without managing workers.

D Gunicorn manages 4 worker processes, each running an async Uvicorn server serving the FastAPI app.

💡 Hint

Think about how Gunicorn and Uvicorn work together to handle async FastAPI apps.

Gunicorn can manage multiple worker processes. Using the Uvicorn worker class allows each worker to run an async server that serves the FastAPI app concurrently.

📝 Syntax

intermediate

Which command correctly starts a FastAPI app with Gunicorn and Uvicorn workers?

Choose the correct command to run a FastAPI app defined in app.py with 3 Uvicorn workers using Gunicorn.

A gunicorn -w 3 -k uvicorn.workers.UvicornWorker app:app

B gunicorn -k uvicorn.workers.UvicornWorker -w app:app 3

C uvicorn -w 3 -k gunicorn.workers.GunicornWorker app:app

D gunicorn app:app -w 3 -k uvicorn.workers.UvicornWorker

💡 Hint

Remember the order: number of workers (-w), worker class (-k), then app module.

The correct syntax is gunicorn -w 3 -k uvicorn.workers.UvicornWorker app:app. Options A, B, and D have incorrect order or wrong flags.

🔧 Debug

advanced

Why does Gunicorn with Uvicorn workers fail to start when using 'app = FastAPI()' inside a function?

Consider this main.py:

def create_app():
    from fastapi import FastAPI
    app = FastAPI()
    return app

You run:

gunicorn -w 2 -k uvicorn.workers.UvicornWorker main:app

But Gunicorn fails to start. Why?

A Gunicorn expects the app variable to be a FastAPI instance at the module level, not created inside a function.

B Gunicorn cannot run more than one worker with apps created inside functions.

C The FastAPI app must be named 'application' for Gunicorn to detect it.

D Gunicorn requires the app to be created with Uvicorn, not FastAPI directly.

💡 Hint

Think about how Gunicorn imports the app object.

Gunicorn imports the app variable at the module level. Since the function defines but does not instantiate app at module level (missing app = create_app()), app is undefined, causing the failure.

❓ state_output

advanced

What is the effect of setting --reload with Gunicorn and Uvicorn workers?

You run this command:

gunicorn -w 2 -k uvicorn.workers.UvicornWorker main:app --reload

What happens?

A Gunicorn crashes because --reload is not supported with Uvicorn workers.

B Gunicorn ignores --reload; only Uvicorn supports auto-reload, so no reload happens.

C Gunicorn reloads only the master process but not the workers, causing inconsistent reloads.

D Gunicorn reloads all workers automatically when code changes, restarting the server.

💡 Hint

Consider which server handles reload in this setup.

Gunicorn's --reload flag does not work well with Uvicorn workers. Uvicorn itself supports reload, but when run under Gunicorn, reload is ignored. So no automatic reload happens.

🧠 Conceptual

expert

How does Gunicorn with Uvicorn workers improve FastAPI app performance in production?

Explain why using Gunicorn with multiple Uvicorn workers is better than running a single Uvicorn server for a FastAPI app in production.

A Gunicorn converts the FastAPI app to synchronous code, improving compatibility with older servers.

B Uvicorn workers reduce memory usage by sharing the same event loop across all workers.

C Gunicorn manages multiple worker processes, allowing the app to use multiple CPU cores and handle more concurrent requests.

D Gunicorn automatically caches all responses, reducing the need to run the app code repeatedly.

💡 Hint

Think about how multiple processes help with CPU usage and concurrency.

Gunicorn can spawn multiple worker processes, each running a Uvicorn server. This allows the app to use multiple CPU cores and handle many requests concurrently, improving performance and reliability in production.