AWS t3a.smallvsAWS t3a.xlarge

t3a.small pairs 2 vCPUs with 2GB of RAM at $0.0188/hr On-Demand (about $14/mo at 24×7). t3a.xlarge pairs 4 vCPUs with 16GB at $0.1504/hr (~$108/mo). t3a.small is 700% cheaper per hour than t3a.xlarge ($0.1316/hr gap).

Because both instances are in the **t3a family**, the only thing that changes between them is sizing — same silicon, same architecture (AMD EPYC (x86_64)), same burstable/sustained behavior. The choice is purely about how much capacity you actually need: t3a.small gives you 2 vCPUs and 2GB of RAM, t3a.xlarge gives you 4 vCPUs and 16GB. AWS scales pricing close to linearly within a family, so picking the right size is mostly about right-sizing your workload, not getting a better deal per vCPU.

On raw price-per-performance, the two are t3a.small delivers ~731% more single-thread Sysbench score per dollar (67128 vs 8078 points per $1/hr). That's the cleanest signal we have for "which one runs your workload faster per dollar," but it only matters if your workload is single-thread-bound; for parallel workloads the multi-core scores (1309 vs 2618) are what to weigh. Spot pricing flips many of these comparisons — when t3a.small drops to $0.0088/hr and t3a.xlarge drops to $0.0574/hr, the cheap-per-hour winner can swing meaningfully.

In practice, pick t3a.small when your workload is closer to burstable general-purpose (bursty traffic — web apps, dev/test boxes, CI runners, small databases). Pick t3a.xlarge when it's closer to burstable general-purpose (bursty traffic — web apps, dev/test boxes, CI runners, small databases). When neither side is obviously right, the cheaper hourly rate usually wins for fault-tolerant batch workloads, while the higher single-core score usually wins for latency-sensitive web traffic. The regional pricing tables linked from each instance page below show where each is currently cheapest — sometimes a >20% regional gap flips the comparison entirely.