Performance - dbsandis/TwiligtApp GitHub Wiki
Good question—performance and scalability on AWS Lightsail depend heavily on the instance size you choose and how efficiently your Django app is written. Here’s a realistic breakdown of expected performance and user limits before you need to upgrade or migrate.
Performance Expectations by Lightsail Instance Type
Common Instance Types for Django Apps
| Instance | vCPUs | RAM | Monthly Cost | Concurrent Users* | Notes |
|---|---|---|---|---|---|
| 1 GB / 1vCPU | 1 | 1 GB | ~$5 | ~10–15 | Best for dev/test, not production |
| 2 GB / 1vCPU | 1 | 2 GB | ~$10 | ~30–50 | MVP launch capable |
| 4 GB / 2vCPU | 2 | 4 GB | ~$20 | ~100–150 | Best choice for early production |
| 8 GB / 2vCPU | 2 | 8 GB | ~$40 | ~250–400 | Handles moderate load |
| 16 GB / 4vCPU | 4 | 16 GB | ~$80 | ~500–800 | Suitable for full production use |
Summary Recommendation for Launch
Start with:
- 4 GB / 2vCPU Lightsail for Django backend
- 2 GB / 1vCPU Lightsail for WordPress login site
- RDS (PostgreSQL or MySQL) in db.t3.micro or t3.small
- Offload static files to S3 from day one
This setup should comfortably support 100–200 users per hour, and scale affordably.
Would you like a deployment checklist for Django on Lightsail with Gunicorn/Nginx for this setup?