M4 family · General Purposex86_64 · Intel/AMD

m4-megamem-112

The m4-megamem-112 machine type has 112 vCPUs and 1488 GB of memory. Pricing for this instance starts at $8.85 per hour and $6458.56 monthly in the us-central1 region.

Updated June 16, 2026
vCPUs
112
Memory
1488 GB
Network
Up to 50 Gbps
Storage
Persistent Disk

Save up to $3229/mo on every m4-megamem-112

Connect Google Cloud — we'll find the optimal pricing model for your workload.

All pricing options

us-central1 · USD · monthly = 730 hrs
Prices exclude local taxes
TermHourlyMonthlySavings
On-Demand
$8.8473$6458.56 Baseline
1-Year Committed Use Discount (CUD)
$5.2199$3810.55 -41%
3-Year Committed Use Discount (CUD)
$2.6542$1937.57 -70%
Preemptible / Spot
$4.4238$3229.34 -50%
You could save $3229.21/mo on this instance with the right pricing model.
Find my savings

Monthly cost estimator

Estimate your spend based on actual usage.
730 h
1h365h730h (24/7)
1
Estimated monthly
$6458.56
730 hrs × $8.8473/hr × 1

Compute

x86_64 · Intel/AMD
vCPUs i112
Memory i1488 GB
Physical processorIntel Emerald Rapids
Nested VirtualizationNot supported
Sole TenantNot supported
GPUNone
Within M4 family
m4-hypermem-16
16 vCPU
m4-megamem-28
28 vCPU
m4-hypermem-32
32 vCPU
m4-megamem-56
56 vCPU
m4-hypermem-64
64 vCPU
m4-ultramem-56
56 vCPU
m4-megamem-112
112 vCPU
m4-ultramem-112
112 vCPU
m4-megamem-224
224 vCPU
m4-ultramem-224
224 vCPU

Lock in this rate across your fleet — typically save 30–40%

Connect your Google Cloud account to apply this pricing logic to every running instance automatically.

Networking

Max egress bandwidth50 Gbps
Tier 1 bandwidth100 Gbps
Enhanced networking iYes (gvnic/virtio)
IPv6 supportYes (Dual-stack VPC)

Storage

Max persistent disks128
Max disk size512 TB
Local SSDsNo local SSD

Compare with another instance

vs.
Specm4-megamem-112m4-hypermem-16Δ
vCPUs11216-86%
Memory1488 GB248 GB-83%
Hourly Price$8.8473$1.4258-84%
Monthly Price$6458.56$1040.84-84%
Cost optimization

GCP recommender alerts can cut this bill ~30-40%.

Connect your GCP account. We'll identify every underutilized m4.* instance and show exactly where downsizing, cleaning up orphaned disks, or shifting to CUDs saves money — with zero code changes.