Meta tags:
description=View the Hyperdisk size, performance, and VM attachment limits for each supported Compute Engine machine type.;

Headings (most frequently used words):

performance, hyperdisk, limits, with, per, instance, volumes, multiple, machine, balanced, achieve, higher, for, and, extreme, maximum, series, that, support, on, by, type, types, steady, state, high, availability, throughput, of, stay, organized, collections, save, categorize, content, based, your, preferences, determine, which, apply, terminology, size, attachment, what, next, ml, summary, total, capacity, number, disks, across, all, products, pricing, resources, engage, network, optimized, scenarios, require, instances, to, reach, provisioned, examples,

Text of the page (most frequently used words):
000 (917), 400 (281), the (229), 800 (197), for (159), instance (158), #hyperdisk (157), with (155), 160 (143), performance (141), and (139), 200 (135), 600 (134), create (116), types (104), vms (103), 500 (95), 240 (90), #machine (87), limits (84), standard (83), custom (81), about (71), vcpus (71), n4a (70), volumes (68), c4n (66), c4d (64), disk (64), c4a (63), 100 (62), troubleshoot (62), you (57), maximum (57), 350 (55), n4d (53), c3d (52), can (50), type (50), manage (46), throughput (46), that (45), attached (42), disks (41), using (41), view (39), attach (39), 192 (39), server (39), iops (38), windows (35), use (34), sol (34), state (33), metal (33), mig (33), compute (32), balanced (32), m4n (32), configure (32), overview (31), extreme (30), steady (30), cloud (29), persistent (29), 480 (29), 320 (29), google (28), all (28), 120 (28), mib (28), limit (28), volume (28), n2d (27), reservation (27), set (27), a4x (26), availability (26), instances (26), engine (25), achieve (25), highgpu (25), more (24), multiple (24), apply (23), see (22), this (22), network (22), number (22), high (22), from (22), 960 (21), sql (21), are (20), t2d (20), monitor (20), images (20), gpu (19), 128 (18), 176 (18), resources (17), following (17), across (17), access (17), image (17), linux (17), policies (16), h4d (16), workload (16), reservations (16), information (15), optimized (15), each (15), tpu (15), exceed (15), size (15), also (15), least (15), shared (15), virtual (15), snapshots (15), groups (15), ssh (15), recommendations (15), configuration (15), single (14), 384 (14), 250 (14), higher (14), microsoft (14), creation (14), host (14), load (14), connect (14), storage (13), series (13), capacity (13), between (13), provisioned (13), ultragpu (13), management (13), bulk (13), cluster (13), per (12), 288 (12), must (12), operations (12), sole (12), best (12), regional (12), then (11), example (11), based (11), delete (11), practices (11), workloads (11), stateful (11), same (10), tib (10), only (10), when (10), metadata (10), migs (10), machines (10), migrate (10), add (10), logs (10), zones (10), optimize (9), your (9), these (9), table (9), total (9), has (9), 180 (9), tpu7x (9), ct6e (9), 125 (9), one (9), cpu (9), choose (9), application (9), licenses (9), managed (9), tenant (9), openshift (9), shutdown (9), time (9), start (9), hpc (9), support (8), license (8), max (8), h200 (8), h100 (8), section (8), supported (8), 224 (8), 144 (8), lists (8), 840 (8), 112 (8), service (8), import (8), resource (8), login (8), internal (8), install (8), disaster (8), recovery (8), agent (8), existing (8), update (8), guest (8), boot (8), keys (8), flexibility (8), dns (8), thumb (7), other (7), available (7), reach (7), require (7), 280 (7), gpus (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), enable (7), manually (7), idle (7), addresses (7), request (7), scale (7), deploy (7), back (7), mysql (7), zonal (7), remove (7), maintenance (7), templates (7), snapshot (7), backup (7), events (6), details (6), send (6), how (6), work (6), local (6), ssd (6), offers (6), 360 (6), maxgpu (6), read (6), write (6), second (6), uses (6), ultramem (6), usage (6), security (6), migration (6), data (6), updates (6), instant (6), files (6), nested (6), applications (6), group (6), mode (6), demand (6), pools (6), run (6), failover (6), extension (6), change (6), new (6), transfer (6), customized (6), spot (6), code (5), samples (5), understand (5), 257 (5), 920 (5), 300 (5), 256 (5), half (5), duplex (5), means (5), sum (5), reads (5), writes (5), every (5), important (5), two (5), certain (5), regardless (5), lssd (5), megagpu (5), issues (5), 420 (5), monitoring (5), databases (5), default (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), placement (5), node (5), highly (5), build (5), multi (5), modify (5), schedules (5), audit (5), symphony (5), options (5), email (5), scripts (5), manager (5), operating (5), systems (5), enhanced (5), capabilities (5), stop (5), tenancy (5), restore (5), regions (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), down (4), format (4), memory (4), tpus (4), 512 (4), than (4), examples (4), suppose (4), list (4), exceeds (4), v6e (4), hightpu (4), 680 (4), 380 (4), edgegpu (4), none (4), configurations (4), document (4), tools (4), distributed (4), authentication (4), ubuntu (4), console (4), bandwidth (4), tcp (4), pmu (4), get (4), share (4), projects (4), upgrade (4), live (4), autoscaling (4), cross (4), region (4), requests (4), calendar (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), zone (4), suspend (4), location (4), resize (4), graceful (4), locations (4), plans (4), replication (4), review (4), bound (4), terms (3), need (3), content (3), its (3), apache (3), accelerator (3), general (3), documentation (3), depends (3), however (3), have (3), ct5lp (3), want (3), listed (3), scenarios (3), 1920 (3), 1440 (3), 416 (3), 208 (3), 640 (3), three (3), applies (3), level (3), specific (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), pro (3), serial (3), patterns (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), project (3), policy (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), plan (3), during (3), prepare (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), query (3), disable (3), properties (3), account (3), increase (3), schedule (3), lifecycle (3), design (3), non (3), pool (3), move (3), creating (3), workstations (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), site (2), youtube (2), center (2), started (2), system (2), pricing (2), products (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), next (2), purpose (2), detailed (2), within (2), refer (2), links (2), attachment (2), still (2), mixture (2), follows (2), combined (2), any (2), depending (2), both (2), sections (2), therefore (2), 32t (2), 24t (2), 870 (2), 450 (2), 815 (2), 150 (2), 750 (2), megamem (2), learn (2), offer (2), displays (2), sustain (2), minimum (2), different (2), affect (2), terminology (2), highcpu (2), bare (2), cpus (2), applicable (2), know (2), determine (2), which (2), requirements (2), sdk (2), languages (2), frameworks (2), costs (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), quota (2), commitment (2), consumption (2), full (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), report (2), arm (2), core (2), api (2), rdp (2), app (2), latency (2), analyze (2), visible (2), cores (2), automatically (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), autohealing (2), iis (2), external (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), provider (2), place (2), running (2), directory (2), setting (2), services (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), name (2), file (2), authenticate (2), method (2), synchronization (2), global (2), switch (2), byol (2), payg (2), byos (2), changes (2), families (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), repair (2), check (2), failures (2), template (2), suspended (2), stopped (2), target (2), distribution (2), physical (2), cancel (2), once (2), interfaces (2), ipv6 (2), static (2), decrease (2), basic (2), consistent (2), scoped (2), copy (2), appliances (2), asynchronous (2), encrypt (2), names (2), mount (2), credentials (2), organization (2), user (2), through (2), advanced (2), rdma (2), created (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), apis (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, page, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, includes, wherever, what, corresponding, separate, individual, combination, but, less, 123, because, illustrate, demonstrate, order, first, rule, enforced, various, factors, summary, describe, discussed, don, ct5p, v5p, v5e, 2400, 1600, 16g, acheieve, hand, would, 272, known, features, 286, 143, 900, 130, 090, 340, 050, 670, 700, 520, 260, even, equal, greater, like, most, cases, actual, 204, select, display, expect, among, refers, namely, highmem, come, highlssd, standardlssd, designation, represents, denoted, where, consult, scenario, discussion, works, meet, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, common, pay, viewing, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, improve, resiliency, communication, reduce, compact, idpf, interface, irdma, driver, nic, customize, threads, sustained, merge, split, extend, renew, without, purchase, cost, savings, dynamic, overcommit, floating, reliable, udp, backends, routing, https, scaling, consuming, consume, combine, cud, allow, sharing, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, were, deployed, transition, test, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, address, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, net, interactive, mongodb, flask, terraform, servers, over, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, after, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, command, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, preserved, turn, off, alternate, fails, repairing, maintain, click, upgrades, override, selectively, applying, accelerate, out, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, deletion, spread, edit, rename, reset, resume, restart, referrers, source, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, make, evaluate, settings, help, kms, customer, supplied, symbolic, practice, device, ram, additional, exapools, verify, identity, ptr, record, failure, rates, tags, restrict, automate, password, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, networks, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, constraint, accounting, provision, slurm, reserved, team, slice, slices, adds, deterministic, base, ready, aci, configured, preempted, historical, alternative, similar, ops, logging, subnet, public, gpudirect, enabled, ultra, specify, platform, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, accelerators, platforms, scores, discover, free, skip, main,

Text of the page (random words):
a 50 000 iops limit then the sum of the reads and writes every second can t exceed 50 000 instance machine type maximum iops maximum throughput mib s a3 a3 h100 a3 highgpu 4g 350 000 5 000 a3 megagpu 8g 400 000 8 000 a3 highgpu 8g 400 000 8 000 a3 edgegpu 8g 400 000 8 000 a3 a3 h200 a3 ultragpu 8g 2 500 000 10 000 a4 2 a4 highgpu 8g 2 500 000 10 000 a4x 2 a4x highgpu 4g 2 500 000 12 500 a4x max 2 a4x maxgpu 4g metal 2 500 000 12 500 c3 1 c3 88 1 350 000 5 000 c3 176 1 500 000 10 000 c3 192 1 500 000 10 000 c3 192 metal 1 500 000 10 000 c3d c3d 60 1 350 000 5 000 c3d 90 1 350 000 5 000 c3d 180 1 350 000 5 000 c3d 360 1 350 000 5 000 c4 2 c4 96 2 350 000 5 000 c4 144 2 350 000 5 000 c4 192 2 500 000 10 000 c4 288 2 500 000 10 000 c4 288 metal 2 500 000 10 000 c4a c4a 64 350 000 5 000 c4a 72 350 000 5 000 c4a 96 metal 350 000 5 000 c4d 2 c4d 64 2 350 000 5 000 c4d 96 2 350 000 5 000 c4d 192 2 350 000 5 000 c4d 384 2 500 000 10 000 c4n 2 c4n 2 2 80 000 1 000 c4n 4 2 100 000 1 000 c4n 8 2 120 000 1 800 c4n 16 2 160 000 3 000 c4n 24 2 240 000 4 000 c4n 48 2 380 000 8 000 c4n 96 2 500 000 12 500 c4n 192 2 1 000 000 25 000 g4 g4 standard 96 350 000 5 000 g4 standard 192 350 000 5 000 g4 standard 384 500 000 10 000 m2 m2 208 100 000 3 815 m2 416 100 000 3 815 m3 1 m3 64 1 350 000 5 000 m3 128 1 450 000 6 870 m4 2 m4 64 2 200 000 3 600 m4 112 2 350 000 5 000 m4 224 2 500 000 10 000 m4n 2 m4n 16 2 160 000 3 000 m4n 28 2 280 000 5 000 m4n 32 2 320 000 6 000 m4n 56 2 400 000 10 000 m4n 64 2 420 000 11 500 m4n 112 2 500 000 12 500 n2 n2 80 1 160 000 5 000 n2 96 160 000 5 000 n2 128 160 000 5 000 x4 x4 480 metal 1 400 000 10 000 x4 960 metal 1 400 000 10 000 x4 1440 24t metal 1 400 000 10 000 x4 1920 32t metal 1 400 000 10 000 z3 1 z3 88 1 350 000 5 000 z3 176 1 350 000 5 000 z3 192 metal 1 500 000 10 000 1 if using hyperdisk extreme with an instance that uses microsoft windows refer to the known issues for windows vm instances 2 also offers steady state performance for more information see performance limits for machine types with steady state performance hyperdisk ml performance limits this section lists the maximum performance that hyperdisk ml volumes can achieve for each supported instance a hyperdisk ml volume s performance when it s attached to an instance can t exceed the limits for the instance s machine type the performance limits are also shared across all hyperdisk ml volumes attached to the same instance regardless of each volume s provisioned performance scenarios that require multiple instances to reach provisioned performance the provisioned throughput for a hyperdisk ml volume is shared between each instance the volume is attached to up to the maximum limit for the machine type that s listed in the following table if a hyperdisk ml volume s provisioned performance is higher than an instance s performance limit the volume can achieve its provisioned performance only if it is attached to multiple instances for example suppose you have a hyperdisk ml volume provisioned with 500 000 mib s of throughput and you want to attach the volume to a3 ultragpu 8 instances a single a3 ultragpu 8 instance can t acheieve more than 4 000 mib s of throughput therefore to achieve the volume s provisioned throughput you must attach the volume to at least 125 500 000 4 000 a3 ultragpu 8 instances on the other hand for the a2 highgpu 1g machine type you would need 272 instances for more information about hyperdisk ml see about hyperdisk ml important to reach the iops limits you must use an i o size of 4 kb maximum throughput limits require an i o size of at least 256 kb hyperdisk performance is half duplex so the iops and throughput limits are shared between read and write operations this means that if a machine type has a 50 000 iops limit then the sum of the reads and writes every second can t exceed 50 000 instance machine type maximum iops maximum throughput mib s a2 a2 1g 28 800 1 800 a2 2g 38 400 2 400 a2 4g 38 400 2 400 a2 8g 38 400 2 400 a2 megagpu 16g 38 400 2 400 a3 a3 h100 a3 1g 6 400 400 a3 2g 28 800 1 800 a3 4g 38 400 2 400 a3 8g 76 800 4 800 a3 a3 h200 a3 ultragpu 8g 1 160 000 10 000 a4 1 a4 highgpu 8g 1 160 000 10 000 a4x 1 a4x highgpu 4g 1 200 000 12 500 a4x max 1 a4x maxgpu 4g metal 1 200 000 12 500 c3 c3 4 6 400 400 c3 8 12 800 800 c3 22 28 800 1 800 c3 44 38 400 2 400 c3 88 76 800 4 800 c3 176 160 000 10 000 c3 192 metal 76 800 4 800 c3d c3d 4 6 400 400 c3d 8 12 800 800 c3d 16 19 200 1 200 c3d 30 19 200 1 200 c3d 60 38 400 2 400 c3d 90 38 400 2 400 c3d 180 38 400 2 400 c3d 360 38 400 2 400 c4 1 c4 2 1 6 400 400 c4 4 1 6 400 400 c4 8 1 12 800 800 c4 16 1 25 600 1600 c4 24 1 25 600 1 600 c4 32 1 25 600 1 600 c4 48 1 38 400 2 400 c4 96 1 80 000 5 000 c4 144 1 100 000 6 250 c4 192 1 160 000 10 000 c4 288 1 160 000 10 000 c4 288 lssd metal 1 200 000 12 500 c4a c4a 1 6 400 400 c4a 2 12 800 800 c4a 4 12 800 800 c4a 8 16 000 1 000 c4a 16 25 600 1 600 c4a 32 38 400 2 400 c4a 48 52 800 3 300 c4a 64 70 400 4 400 c4a 72 80 000 5 000 c4a 72 80 000 5 000 c4a 96 metal 80 000 5 000 c4d 1 c4d 2 1 6 400 400 c4d 4 1 6 400 400 c4d 8 1 12 800 800 c4d 16 1 19 200 1 200 c4d 32 1 25 600 1 600 c4d 48 1 25 600 1 600 c4d 64 1 38 400 2 400 c4d 96 1 50 000 3 125 c4d 192 1 100 000 6 250 c4d 384 1 160 000 10 000 c4d 384 metal 1 160 000 10 000 c4n 1 c4n 2 1 12 800 800 c4n 4 1 12 800 800 c4n 8 1 25 600 1 600 c4n 16 1 44 800 2 800 c4n 24 1 51 200 3 200 c4n 48 1 100 000 6 250 c4n 96 1 160 000 10 000 c4n 192 1 320 000 20 000 g2 g2 standard 4 12 800 800 g2 standard 8 19 200 1 200 g2 standard 12 28 800 1 800 g2 standard 16 38 400 2 400 g2 standard 24 38 400 2 400 g2 standard 32 38 400 2 400 g2 standard 48 38 400 2 400 g2 standard 96 38 400 2 400 g4 g4 standard 6 6 400 400 g4 standard 12 12 800 800 g4 standard 24 19 200 1 200 g4 standard 48 25 600 1 600 g4 standard 96 44 800 2 800 g4 standard 192 76 800 4 800 g4 standard 384 160 000 10 000 n4 n4 2 3 840 240 n4 4 3 840 240 n4 8 7 680 480 custom n4 types with 10 to 14 vcpus 7 680 480 n4 16 19 200 1 200 custom n4 types with 18 to 30 vcpus 19 200 1 200 n4 32 25 600 1 600 custom n4 types with 34 to 46 vcpus 25 600 1 600 n4 48 38 400 2 400 custom n4 types with 50 to 62 vcpus 38 400 2 400 n4 64 38 400 2 400 custom n4 types with 66 to 78 vcpus 38 400 2 400 n4 80 38 400 2 400 n4a n4a 1 3 840 240 n4a 2 3 840 240 n4a 4 3 840 240 n4a 8 7 680 480 n4a 16 19 200 1 200 n4a 32 25 600 1 600 n4a 48 38 400 2 400 n4a 64 38 400 2400 n4d n4d 2 3 840 240 n4d 4 3 840 240 n4d 8 7 680 480 n4d 16 19 200 1 200 n4d 32 25 600 1 600 n4d 48 38 400 2 400 n4d 64 38 400 2 400 n4d 80 38 400 2 400 n4d 96 38 400 2 400 tpu v5e ct5lp hightpu 1t 19 200 1 200 ct5lp hightpu 4t 28 800 1 800 ct5lp hightpu 8t 28 800 1 800 tpu v5p ct5p hightpu 4t 76 800 4 800 tpu v6e ct6e standard 1t 19 200 1 200 ct6e standard 4t 38 400 2 400 ct6e standard 8t 38 400 2 400 tpu7x 1 tpu7x standard 4t 1 96 000 6 000 1 also offers steady state performance for more information see performance limits for machine types with steady state performance hyperdisk throughput performance limits this section lists the maximum performance that hyperdisk throughput volumes can achieve for each supported instance a hyperdisk throughput volume s performance when it s attached to an instance can t exceed the limits for the instance s machine type the performance limits are also shared across all hyperdisk throughput volumes attached to the same instance regardless of each volume s provisioned performance achieve higher performance with multiple hyperdisk throughput volumes certain instances can exceed the maximum performance for a single hyperdisk throughput volume 2 400 mib s an instance can achieve these higher limits if you attach multiple hyperdisk throughput volumes to the instance if an instance s performance limit in the following table exceeds 2 400 mib s then the instance can achieve that limit only if you attach multiple hyperdisk throughput volumes for example the performance limit for a a3 8g instance using hyperdisk throughput volumes is 3 000 mib s therefore to achieve 3 000 mib s of throughput you must attach at least two hyperdisk throughput volumes to the instance for more information about hyperdisk throughput see about hyperdisk throughput important to reach the iops limits you must use an i o size of 4 kb maximum throughput limits require an i o size of at least 256 kb hyperdisk performance is half duplex so the iops and throughput limits are shared between read and write operations this means that if a machine type has a 50 000 iops limit then the sum of the reads and writes every second can t exceed 50 000 the performance limits also apply to custom machine types instance machine type maximum iops maximum throughput mib s a3 a3 h100 a3 1g 4 800 1 200 a3 2g 9 600 2 400 a3 4g 9 600 2 400 a3 8g 12 000 3 000 a4x max a4x maxgpu 4g metal 40 000 10 000 c3 c3 4 960 240 c3 8 3 200 800 c3 22 4 800 1 200 c3 44 7 200 1 800 c3 88 9 600 2 400 c3 176 19 200 4 800 c3 192 19 200 4 800 c3d c3d 4 960 240 c3d 8 3 200 800 c3d 16 4 800 1 200 c3d 30 7 200 1 800 c3d 60 9 600 2 400 c3d 90 9 600 2 400 c3d 180 9 600 2 400 c3d 360 9 600 2 400 c4 1 c4 2 1 1 600 400 c4 4 1 1 600 400 c4 8 1 3 200 800 c4 16 1 4 000 1 000 c4 24 1 4 800 1 200 c4 32 1 6 400 1 600 c4 48 1 9 600 2 400 c4 64 1 12 800 3 200 c4 96 1 20 000 5 000 c4 144 1 20 000 5 000 c4 192 1 40 000 10 000 c4 288 1 40 000 10 000 c4a c4a 1 1 600 400 c4a 2 3 200 800 c4a 4 3 200 800 c4a 8 4 000 1 000 c4a 16 6 400 1 600 c4a 32 9 600 2 400 c4a 48 13 200 3 300 c4a 64 17 600 4 400 c4a 72 20 000 5 000 c4a 96 metal 20 000 5 000 c4n c4n 2 3 200 800 c4n 4 3 200 800 c4n 8 6 400 1 600 c4n 16 11 200 2 800 c4n 24 12 800 3 200 c4n 48 25 000 6 250 c4n 96 40 000 10 000 c4n 192 80 000 20 000 g2 g2 standard 4 960 240 g2 standard 8 3 200 800 g2 standard 12 3 200 800 g2 standard 16 4 800 1 200 g2 standard 24 4 800 1 200 g2 standard 32 7 200 1 800 g2 standard 48 9 600 2 400 g2 standard 96 9 600 2 400 g4 g4 standard 6 1 600 400 g4 standard 12 3 200 800 g4 standard 24 4 800 1 200 g4 standard 48 6 400 1 600 g4 standard 96 11 200 2 800 g4 standard 192 19 200 4 800 g4 standard 384 40 000 10 000 h3 h3 standard 88 960 240 m3 m3 32 7 200 1 800 m3 64 9 600 2 400 m3 128 9 600 2 400 n2 n2 2 800 200 n2 4 960 240 custom n2 types with 6 vcpus 960 240 n2 8 3 200 800 custom n2 types with 10 to 14 vcpus 3 200 800 n2 16 4 800 1 200 custom n2 types with 18 to 30 vcpus 4 800 1 200 n2 32 7 200 1 800 custom n2 types with 36 to 44 vcpus 7 200 1 800 n2 48 9 600 2 400 custom n2 types with 52 to 60 vcpus 9 600 2 400 n2 64 12 000 3 000 custom n2 types with 68 to 76 vcpus 12 000 3 000 n2 80 12 000 3 000 n2 96 12 000 3 000 n2 128 9 600 2 400 n2d n2d 2 800 200 n2d 4 960 240 n2d 8 3 200 800 n2d 16 4 800 1 200 n2d 32 7 200 1 800 n2d 48 9 600 2 400 n2d 64 9 600 2 400 n2d 80 9 600 2 400 n2d 96 9 600 2 400 n2d 128 9 600 2 400 n2d 224 9 600 2 400 n4 n4 2 960 240 n4 4 960 240 custom n4 types with 6 vcpus 960 240 n4 8 1 920 480 custom n4 types with 10 to 14 vcpus 1 920 480 n4 16 4 800 1 200 custom n4 types with 18 to 30 vcpus 4 800 1 200 n4 32 6 400 1 600 custom n4 types with 34 to 46 vcpus 6 400 1 600 n4 48 9 600 2 400 custom n4 types with 50 to 62 vcpus 9 600 2 400 n4 64 9 600 2 400 custom n4 types with 66 to 78 vcpus 9 600 2 400 n4 80 9 600 2 400 n4a n4a 1 960 240 n4a 2 960 240 custom n4a types with 3 vcpus 960 240 n4a 4 960 240 custom n4a types with 5 to 7 vcpus 960 240 n4a 8 1 920 480 custom n4a types with 9 to 15 vcpus 1 920 480 n4a 16 4 800 1 200 custom n4a types with 17 to 31 vcpus 4 800 1 200 n4a 32 6 400 1 600 custom n4a types with 33 to 47 vcpus 6 400 1 600 n4a 48 9 600 2 400 custom n4a types with 49 to 63 vcpus 9 600 2 400 n4a 64 9 600 2 400 n4d n4d 2 960 240 n4d 4 960 240 n4d 8 1 920 480 n4d 16 4 800 1 200 n4d 32 6 400 1 600 n4d 48 9 600 2 400 n4d 64 9 600 2 400 n4d 80 9 600 2 400 n4d 96 9 600 2 400 t2d t2d 1 800 200 t2d 2 800 200 t2d 4 960 240 t2d 8 3 200 800 t2d 16 4 800 1 200 t2d 32 7 200 1 800 t2d 48 9 600 2 400 t2d 60 9 600 2 400 z3 z3 8 3 200 800 z3 14 3 200 800 z3 16 3 200 800 z3 22 4 800 1 200 z3 32 4 800 1 200 z3 44 7 200 1 800 z3 88 9 600 2 400 z3 176 9 600 2 400 1 also offers steady state performance for more information see performance limits for machine types with steady state performance hyperdisk size and attachment limits per instance the following sections describe the limits to the size and number of hyperdisk volumes you can attach to a single instance the limits discussed don t apply to any local ssd disks attached to the same instance summary of hyperdisk per instance limits maximum total capacity per instance the maximum total capacity of all the volumes attached to an instance is between 257 tib to 512 tib depending on various factors for details see maximum total capacity per instance maximum number of volumes attached to an instance compute engine limits the number of hyperdisk volumes that you can attach to a single instance the following limits apply in order when both limits apply the first rule in the list is enforced the number of hyperdisk volumes that you can attach to the instance 8 to 128 depending on the hyperdisk type and the instance s machine type the number of hyperdisk and persistent disk volumes that you can attach to the instance 128 for more information see maximum number of disks across all types the following examples demonstrate how the limits work examples suppose you have a c3 96 instance the following limits apply maximum number of hyperdisk volumes across all types 128 however for each hyperdisk type the limits are as follows hyperdisk throughput 64 hyperdisk ml 64 hyperdisk extreme 8 hyperdisk balanced or hyperdisk balanced high availability 32 maximum number of persistent disk and hyperdisk volumes that you can attach to the instance 128 maximum combined total capacity of all volumes 512 tib the following examples illustrate these limits maximum number of a single type of hyperdisk per instance if you attach 8 hyperdisk extreme volumes to the instance you can attach up to 123 more hyperdisk volumes to the instance however you can attach only 3 more hyperdisk extreme volumes to the instance because the maximum number of hyperdisk extreme volumes 8 maximum number of hyperdisk volumes per instance 128 if you attach 8 hyperdisk extreme volumes to the instance you can attach up to 120 more hyperdisk volumes to the instance maximum number of disks or volumes per instance across all types 128 if you attach a combined total of 128 hyperdisk volumes to the instance then you can t attach any more hyperdisk or persistent disk volumes however if you attach only 64 hyperdisk volumes to the instance you can still attach up to 64 persistent disk or hyperdisk volumes to the instance maximum total capacity per instance the maximum total disk capacity in tib across all hyperdisk and persistent disk types that you attach to an instance depends on the number of vcpus that the instance has the capacity limits are as follows for machine types with less t...