Workload guide · Development
Databases: hardware requirements guide
Postgres, MySQL, Redis and other databases as services.
Hardware requirements by tier
Three tiers for every workload: the minimum that works, the recommended sweet spot, and the comfortable headroom level. These are the same tiers the WisePC decision engine uses when it plans a build around your goal.
| Tier | CPU cores | RAM | Storage | GPU | Network |
|---|---|---|---|---|---|
| Minimum | 2 cores | 8 GB | 1 TB (ssd) | None | 1 GbE |
| Recommended | 4 cores | 16 GB | 2 TB (ssd) | None | 2.5 GbE |
| Comfortable | 8 cores | 64 GB | 8 TB (ssd) | None | 10 GbE |
Which tier do you need?
- Pick Minimum (2 cores, 8 GB RAM) only for a single-purpose machine on a tight budget — expect little headroom.
- Recommended (4 cores, 16 GB RAM) is the sweet spot: enough for the workload plus the usual side-services, without overspending.
- Pick Comfortable (8 cores, 64 GB RAM) when this workload shares the machine with others or will grow — you pay for headroom, not for anxiety.
- GPU rule for this workload: None.
Frequently asked questions
How much RAM does databases need?
8 GB is the sensible minimum, 16 GB covers most real setups, and 64 GB gives comfortable headroom for growth and extra services.
How many CPU cores does databases need?
A 2-core CPU is the minimum, 4 cores is the recommended sweet spot, and 8 cores is comfortable when it shares the machine with other workloads.
Does databases need a dedicated GPU?
No — integrated graphics or a headless setup is enough.
What storage and network does databases expect?
Storage: 2 TB of SSD is the recommended baseline (1 TB minimum, 8 TB comfortable). Network: 2.5 GbE is the recommended baseline.
What runs well alongside databases?
It pairs naturally with: Docker, Local AI inference.