Most people still use GP2 as the default EBS volume type in launch templates and infrastructure modules. Not because it is optimal today, but because it has been there for years.

In most production audits I review, oversized GP2 volumes are one of the easiest cost optimizations left untouched.

GP2 performance is tied to volume size and burst credits, which can lead to unstable latency and throughput during sustained workloads. For production databases, search clusters, and write-heavy services, this behavior directly impacts reliability and user experience.GP3 changes this model by separating performance from storage size, enabling consistent throughput, predictable latency, and more efficient cost control.

To understand why this difference matters in real workloads, let’s examine the architecture behind both.

**How GP2 Was Designed

**GP2 follows a size-based performance model:IOPS = 3 × Volume Size (GB)

Enter fullscreen mode

Exit fullscreen mode

Key characteristics:

Minimum 100 IOPS

Burst up to…