m1-ultramem-160 as a GKE node
160 vCPU3844 GiBx86_64Google Cloud us-central1M1 Ultra Memory 160
Where the m1-ultramem-160 goes
Default GKE setup: GKE ≤ 1.36.
CPU159.33 of 160 vCPU left for your pods
Memory3,759.97 GiB of 3844 GiB left for your pods
your podsDaemonSets (200m, 300 MiB assumed)kubelet reservedeviction
110max pods per node
$18,375.85on demand / month · $25.17/h
$3,156.63spot / month (varies)
m1-ultramem-160 GKE max pods and allocatable memory — quick answers
- How many pods can a m1-ultramem-160 run as a node with GKE ≤ 1.36? Up to 110; kubelet keeps 85747 MiB of memory and 470m CPU, leaving 3,760.26 GiB and 159.53 vCPU for pods.
- How many pods can a m1-ultramem-160 run as a node with GKE 1.37+ (Container-Optimized OS)? Up to 110; kubelet keeps 2250 MiB of memory and 470m CPU, leaving 3,841.80 GiB and 159.53 vCPU for pods.
- How many 500m / 1 GiB pods fit? 107 per node after DaemonSets; 1 nodes for 10 replicas, about $18,375.85/month on demand.
What kubelet reserves on m1-ultramem-160
| Setup | Max pods | kube-reserved CPU | Memory reserved + eviction | Allocatable CPU | Allocatable memory | Memory usable |
|---|---|---|---|---|---|---|
| GKE ≤ 1.36 tiered memory reservation | 110 | 470m | 85647 Mi + 100 Mi | 159.53 | 3,760.26 GiB | 97.8% |
| GKE 1.37+ (Container-Optimized OS) 15 MiB × max pods + 500 MiB, CPU capped at 1 vCPU | 110 | 470m | 2150 Mi + 100 Mi | 159.53 | 3,841.80 GiB | 99.9% |
How these numbers are computed: reservation formulas. Check a live node with kubectl describe node → Allocatable.
How many pods fit on one m1-ultramem-160
Assumes DaemonSets (CNI, kube-proxy, log and metrics agents) request 200m CPU, 300 Mi and 3 pods per node. Try your own numbers in the node calculator.
| Pod requests (CPU / memory) | GKE ≤ 1.36 | GKE 1.37+ (Container-Optimized OS) | $ per pod / month |
|---|---|---|---|
| 100m / 128 Mi | 107 | 107 | $171.74 |
| 250m / 256 Mi | 107 | 107 | $171.74 |
| 250m / 512 Mi | 107 | 107 | $171.74 |
| 500m / 512 Mi | 107 | 107 | $171.74 |
| 500m / 1024 Mi | 107 | 107 | $171.74 |
| 1000m / 1024 Mi | 107 | 107 | $171.74 |
| 1000m / 2048 Mi | 107 | 107 | $171.74 |
| 2000m / 4096 Mi | 79 | 79 | $232.61 |
| 4000m / 8192 Mi | 39 | 39 | $471.18 |
Similar GKE node types
| Type | vCPU | GiB | Alloc CPU | Alloc memory | Max pods | $/month | $ per alloc GiB |
|---|---|---|---|---|---|---|---|
| n1-ultramem-160 | 160 | 3844 | 159.53 | 3,760.26 GiB | 110 | $15,581.70 | $4.14 |
| m3-ultramem-128 | 128 | 3904 | 127.61 | 3,819.06 GiB | 110 | $17,786.30 | $4.66 |
| h4d-megamem-192-lssd | 192 | 3024 | 191.45 | 2,956.66 GiB | 110 | $9,257.12 | $3.13 |
| m4-megamem-224 | 224 | 2976 | 223.37 | 2,909.62 GiB | 110 | $12,917.12 | $4.44 |
| m4n-megamem-224 | 224 | 2976 | 223.37 | 2,909.62 GiB | 110 | $23,250.81 | $7.99 |
| m4-ultramem-112 | 112 | 2976 | 111.65 | 2,909.62 GiB | 110 | $11,422.68 | $3.93 |
| m4n-ultramem-112 | 112 | 2976 | 111.65 | 2,909.62 GiB | 110 | $20,560.81 | $7.07 |
| m2-ultramem-208 | 208 | 5888 | 207.41 | 5,763.38 GiB | 110 | $30,741.71 | $5.33 |
Closest match on other clouds
| Type | vCPU | GiB | Alloc CPU | Alloc memory | Max pods | $/month | $ per alloc GiB |
|---|---|---|---|---|---|---|---|
| m176s4v3 | 176 | 3892 | 174.14 | 3,886.97 GiB | 250 | $18,184.30 | $4.68 |
| m176ds4v3 | 176 | 3892 | 174.14 | 3,886.97 GiB | 250 | $19,323.10 | $4.97 |
| m176bds4v3 | 176 | 3892 | 174.14 | 3,886.97 GiB | 250 | $45,865.90 | $11.80 |
| x1e.32xlarge | 128 | 3904 | 127.61 | 3,901.14 GiB | 234 | $19,482.24 | $4.99 |
| x2iedn.32xlarge | 128 | 4096 | 127.61 | 4,087.74 GiB | 737 | $19,473.48 | $4.76 |
| x2iedn.metal | 128 | 4096 | 127.61 | 4,087.74 GiB | 737 | $19,473.48 | $4.76 |