chore: add comparison links & storage recommendations

dannykopping · dannykopping · commit da6ca12d1dfe · 2025-07-15T09:29:31.000+02:00
Signed-off-by: Danny Kopping &lt;dannykopping@gmail.com&gt;
diff --git a/docs/admin/infrastructure/validated-architectures/index.md b/docs/admin/infrastructure/validated-architectures/index.md
@@ -323,19 +323,33 @@ For production deployments, we recommend using dedicated compute instances rathe
 - **Medium deployments (1000-2000 users)**: `db.m6i.xlarge` (4 vCPU, 16 GB RAM) or `db.r6i.xlarge` (4 vCPU, 32 GB RAM)
 - **Large deployments (2000+ users)**: `db.m6i.2xlarge` (8 vCPU, 32 GB RAM) or `db.r6i.2xlarge` (8 vCPU, 64 GB RAM)
 
+[Comparison](https://instances.vantage.sh/rds?memory_expr=%3E%3D0&vcpus_expr=%3E%3D0&memory_per_vcpu_expr=%3E%3D0&gpu_memory_expr=%3E%3D0&gpus_expr=%3E%3D0&maxips_expr=%3E%3D0&storage_expr=%3E%3D0&filter=db.r6i.large%7Cdb.m6i.large%7Cdb.m6i.xlarge%7Cdb.r6i.xlarge%7Cdb.r6i.2xlarge%7Cdb.m6i.2xlarge&region=us-east-1&pricing_unit=instance&cost_duration=hourly&reserved_term=yrTerm1Standard.noUpfront&compare_on=true)
+
 ##### Azure (Azure Database for PostgreSQL)
 
 - **Small deployments (<1000 users)**: `Standard_D2s_v5` (2 vCPU, 8 GB RAM) or `Standard_E2s_v5` (2 vCPU, 16 GB RAM)
 - **Medium deployments (1000-2000 users)**: `Standard_D4s_v5` (4 vCPU, 16 GB RAM) or `Standard_E4s_v5` (4 vCPU, 32 GB RAM)
 - **Large deployments (2000+ users)**: `Standard_D8s_v5` (8 vCPU, 32 GB RAM) or `Standard_E8s_v5` (8 vCPU, 64 GB RAM)
 
+[Comparison](https://instances.vantage.sh/azure?memory_expr=%3E%3D0&vcpus_expr=%3E%3D0&memory_per_vcpu_expr=%3E%3D0&gpu_memory_expr=%3E%3D0&gpus_expr=%3E%3D0&maxips_expr=%3E%3D0&storage_expr=%3E%3D0&filter=d2s-v5%7Ce2s-v5%7Cd4s-v5%7Ce4s-v5%7Ce8s-v5%7Cd8s-v5&region=us-east&pricing_unit=instance&cost_duration=hourly&reserved_term=yrTerm1Standard.allUpfront&compare_on=true)
+
 ##### Google Cloud (Cloud SQL for PostgreSQL)
 
-- **Small deployments (<1000 users)**: `db-standard-2` (2 vCPU, 7.5 GB RAM) or `db-highmem-2` (2 vCPU, 13 GB RAM)
-- **Medium deployments (1000-2000 users)**: `db-standard-4` (4 vCPU, 15 GB RAM) or `db-highmem-4` (4 vCPU, 26 GB RAM)
-- **Large deployments (2000+ users)**: `db-standard-8` (8 vCPU, 30 GB RAM) or `db-highmem-8` (8 vCPU, 52 GB RAM)
+- **Small deployments (<1000 users)**: `db-perf-optimized-N-2` (2 vCPU, 16 GB RAM)
+- **Medium deployments (1000-2000 users)**: `db-perf-optimized-N-4` (4 vCPU, 32 GB RAM)
+- **Large deployments (2000+ users)**: `db-perf-optimized-N-8` (8 vCPU, 64 GB RAM)
+
+[Comparison](https://cloud.google.com/sql/docs/postgres/machine-series-overview#n2)
+
+##### Storage recommendations
+
+For optimal database performance, use the following storage types:
+
+- **AWS RDS/Aurora**: Use `gp3` (General Purpose SSD) volumes with at least 3,000 IOPS for production workloads. For high-performance requirements, consider `io1` or `io2` volumes with provisioned IOPS.
+
+- **Azure Database for PostgreSQL**: Use Premium SSD (P-series) with appropriate IOPS and throughput provisioning. Standard SSD can be used for development/test environments.
 
-> **Note**: Avoid burstable instance types (AWS t-family, Azure B-series) for production workloads as they provide inconsistent CPU performance. The baseline CPU for these instances is typically 20-40% of the maximum, with usage above baseline being throttled.
+- **Google Cloud SQL**: Use SSD persistent disks for production workloads. Standard (HDD) persistent disks are suitable only for development or low-performance requirements.
 
 If you enable
 [database encryption](../../../admin/security/database-encryption.md) in Coder,
