Meta tags:
description= This page discusses the use cases, performance limits, and unique features of Hyperdisk Balanced volumes—zonal disks with customizable IOPS and throughput.;
Headings (most frequently used words):
hyperdisk, balanced, performance, for, and, provisioned, limits, size, about, with, support, baseline, volumes, pricing, iops, throughput, multiple, replication, stay, organized, collections, save, categorize, content, based, on, your, preferences, use, cases, machine, series, change, the, or, when, attached, to, an, instance, disaster, recovery, protection, regional, availability, storage, pools, share, volume, between, vms, limitations, what, next, default, values, quota, achieve, higher, across, regions, cross, zonal, products, resources, engage,
Text of the page (most frequently used words):
000 (217), and (135), the (129), create (129), for (123), vms (105), hyperdisk (104), with (91), #performance (75), instance (68), about (67), #balanced (64), troubleshoot (62), iops (56), 160 (56), you (53), volume (50), 400 (49), disk (47), manage (46), server (40), use (39), view (38), using (37), disks (36), 800 (35), machine (33), compute (33), windows (33), mig (33), configure (32), volumes (31), throughput (31), overview (31), can (30), size (28), google (27), cloud (27), limits (27), custom (27), reservation (27), set (27), from (25), engine (25), storage (24), that (23), instances (22), sql (22), 240 (21), access (20), availability (20), types (20), 100 (20), monitor (20), images (20), provisioned (19), 600 (19), network (19), image (18), snapshots (18), type (18), gpu (18), resources (17), standard (17), 320 (17), apply (17), linux (17), see (16), policies (16), pools (16), attached (16), n4a (16), reservations (16), high (15), regional (15), mib (15), default (15), virtual (15), groups (15), ssh (15), recommendations (15), configuration (15), multiple (14), workloads (14), microsoft (14), cluster (14), bulk (14), 200 (14), gib (14), best (14), workload (14), creation (14), host (14), load (14), connect (14), c4d (13), c4a (13), values (13), management (13), change (12), delete (12), between (12), vcpus (12), maximum (12), based (12), sole (12), persistent (12), more (11), add (11), your (11), zonal (11), zones (11), tpu (11), n4d (11), h4d (11), 500 (11), following (11), 140 (11), practices (11), stateful (11), data (10), time (10), metal (10), c4n (10), c3d (10), specify (10), boot (10), metadata (10), migs (10), machines (10), migrate (10), logs (10), mode (9), existing (9), replication (9), back (9), disaster (9), recovery (9), limit (9), choose (9), application (9), licenses (9), managed (9), tenant (9), openshift (9), shutdown (9), start (9), hpc (9), all (8), this (8), are (8), details (8), license (8), zone (8), across (8), m4n (8), when (8), modify (8), mysql (8), service (8), import (8), cpu (8), resource (8), login (8), optimize (8), internal (8), install (8), agent (8), update (8), guest (8), keys (8), flexibility (8), dns (8), optimized (8), thumb (7), information (7), multi (7), attach (7), failover (7), regions (7), region (7), instant (7), 192 (7), single (7), higher (7), quota (7), baseline (7), capacity (7), provision (7), applications (7), new (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), remove (7), maintenance (7), templates (7), snapshot (7), backup (7), events (6), send (6), most (6), share (6), available (6), 120 (6), 480 (6), a4x (6), highgpu (6), operations (6), project (6), don (6), tib (6), configurable (6), series (6), databases (6), usage (6), security (6), migration (6), updates (6), files (6), nested (6), gpus (6), group (6), demand (6), run (6), extension (6), transfer (6), customized (6), spot (6), code (5), samples (5), support (5), understand (5), within (5), have (5), only (5), infrastructure (5), must (5), cross (5), protect (5), asynchronous (5), then (5), also (5), state (5), achieve (5), supports (5), minimum (5), range (5), postgresql (5), monitoring (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), placement (5), node (5), highly (5), build (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), control (5), workstation (5), faq (5), flex (5), português (4), español (4), pricing (4), other (4), down (4), its (4), learn (4), writer (4), than (4), each (4), creating (4), replicate (4), specific (4), 250 (4), shared (4), table (4), lists (4), how (4), advanced (4), free (4), tools (4), distributed (4), authentication (4), issues (4), ubuntu (4), console (4), bandwidth (4), tcp (4), pmu (4), number (4), local (4), ssd (4), get (4), projects (4), upgrade (4), live (4), autoscaling (4), requests (4), calendar (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), uses (4), extensions (4), work (4), suspend (4), location (4), resize (4), graceful (4), locations (4), plans (4), review (4), bound (4), terms (3), need (3), content (3), apache (3), every (3), additional (3), limitations (3), where (3), created (3), suspended (3), stopped (3), costs (3), always (3), another (3), event (3), copy (3), example (3), tpu7x (3), ct6e (3), 125 (3), 180 (3), ultramem (3), 384 (3), 150 (3), max (3), reach (3), least (3), has (3), exceed (3), important (3), supported (3), once (3), after (3), level (3), min (3), less (3), formulas (3), value (3), depends (3), general (3), guides (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), pro (3), serial (3), configurations (3), patterns (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), policy (3), list (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), plan (3), during (3), prepare (3), deployment (3), rhel (3), environment (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), workstations (3), tpus (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), contact (2), products (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), next (2), hours (2), twice (2), hour (2), window (2), confidential (2), one (2), billed (2), total (2), isn (2), maintains (2), write (2), feature (2), like (2), reduce (2), purchase (2), same (2), outage (2), secondary (2), east4 (2), west1 (2), protection (2), offers (2), steady (2), 176 (2), v6e (2), 112 (2), 280 (2), 144 (2), 128 (2), 288 (2), h200 (2), h100 (2), require (2), 256 (2), second (2), per (2), these (2), section (2), affect (2), include (2), similar (2), unless (2), detailed (2), larger (2), 666667 (2), 500x (2), 625 (2), calculate (2), 319 (2), common (2), fit (2), cases (2), purpose (2), cost (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (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), 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), simulate (2), topology (2), together (2), repairs (2), repair (2), check (2), failures (2), template (2), target (2), distribution (2), physical (2), cancel (2), interfaces (2), ipv6 (2), static (2), decrease (2), basic (2), consistent (2), scoped (2), appliances (2), encrypt (2), names (2), format (2), mount (2), memory (2), extreme (2), credentials (2), organization (2), user (2), through (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (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, 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, what, accessed, was, until, them, charges, incur, even, any, while, enables, simplify, planning, avoid, overprovisioning, consider, let, clone, unlikely, enabling, became, unavailable, could, point, 1920, 32t, 1440, 24t, 960, 224, 416, 208, megamem, 640, 300, 360, maxgpu, ultragpu, edgegpu, megagpu, half, duplex, read, means, sum, reads, writes, exceeds, two, certain, regardless, still, would, remaining, 499, included, first, above, amounts, not, principles, billable, assigns, 585, 156, 750, some, corresponding, ranges, listed, preceding, formula, allowable, allowed, determine, given, 159, sizes, fixed, respectively, according, vary, but, much, varies, questions, com, preview, know, needs, creates, later, such, line, business, lob, desktop, vdi, good, including, designed, sub, millisecond, latencies, document, describes, features, combination, price, ownership, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, 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, compact, idpf, interface, irdma, driver, nic, customize, threads, sustained, merge, split, extend, renew, without, savings, dynamic, overcommit, cpus, 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, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, command, vpc, controls, 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, 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, different, considerations, synchronous, consistency, failback, make, evaluate, settings, help, kms, customer, supplied, symbolic, links, practice, device, ram, 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, examples, slurm, reserved, team, slice, slices, adds, scenarios, deterministic, base, requirements, ready, aci, configured, preempted, historical, alternative, displays, ops, logging, subnet, public, gpudirect, enabled, ultra, platform, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, accelerators, platforms, scores, discover, skip, main,
Text of the page (random words):
ling add an instance group to a load balancer request routing to a multi region external https load balancer cross region load balancing for microsoft iis backends set up internal tcp udp load balancing build reliable and scalable applications use autohealing for highly available applications use load balancing for highly available applications use autoscaling for highly scalable applications globally autoscale a web service on compute engine patterns for scalable and resilient applications patterns for using floating ip addresses on compute engine optimize resource utilization use recommendations to manage resources apply machine type recommendations to vms configure machine type recommendations apply machine type recommendations to migs view and apply idle resources recommendations view and understand vm insights view and understand mig insights manage idle vm recommendations idle vm recommendations overview view and apply idle vm recommendations configure idle vm recommendations manage reservation recommendations reservation recommendations overview view and apply idle reservation recommendations view and apply underutilized reservation recommendations configure idle reservation recommendations configure underutilized reservation recommendations overcommit cpus on sole tenant vms manual live migration about manual live migration manually live migrate vms share sole tenant node groups next generation dynamic resource management cost savings get discounts for committed usage about commitments and committed use discounts cuds resource based cuds purchase resource based commitments without attached reservations with attached reservations for os licenses manage resource based commitments renew commitments automatically extend commitment terms merge and split commitments upgrade commitments share resource based cuds across projects get discounts for sustained usage disk performance optimize hyperdisk performance optimize persistent disk performance optimize local ssd performance workload performance set the number of threads per core customize the number of visible cpu cores analyze the cpu performance using the pmu pmu overview enable the pmu in vms manage the pmu in vms network performance network bandwidth use google virtual nic use irdma network driver use idpf network interface configure a vm with higher bandwidth reduce latency by using compact placement policies optimize tcp network communication optimize tcp network performance optimize tcp network resiliency benchmark higher bandwidth vms optimize app latency with load balancing use dpdk to improve network performance network performance and gpu vms networking and gpu machines use higher network bandwidth patterns for using multiple host nics troubleshoot general tips troubleshoot connectivity troubleshoot rdp troubleshoot ssh troubleshoot os login troubleshoot vms troubleshoot vm operations troubleshoot vm creation troubleshoot resource availability errors troubleshoot bulk api vm creation troubleshoot vm reboots and shutdowns troubleshoot vm suspension troubleshoot vm updates troubleshoot unresponsive vms troubleshoot vm startup troubleshoot fstab errors troubleshoot kernel panic collecting core dumps rescue an inaccessible vm troubleshoot cpu bus locks troubleshoot cpu soft lockups troubleshoot vm configurations troubleshoot arm vms troubleshoot gpu vms troubleshoot nvidia gpu errors generate a nvidia bug report for blackwell gpus troubleshoot nested virtualization troubleshoot using vm screenshots troubleshoot sole tenant nodes troubleshoot vm performance issues troubleshoot sudoers files troubleshoot windows vms troubleshoot windows vms collecting diagnostic information troubleshoot using the serial console troubleshoot using the serial console viewing serial port output troubleshoot instance groups troubleshoot managed instance groups migs troubleshoot os management troubleshoot licenses troubleshoot image import and export troubleshooting sles pay as you go registration troubleshooting ubuntu pro registration troubleshoot metadata server troubleshoot metadata server troubleshoot networking issues troubleshoot common networking issues troubleshoot network drivers troubleshoot vm performance issues troubleshoot storage troubleshoot disk creation troubleshoot full disks and disk resizing troubleshoot disk encryption troubleshoot nvme disks troubleshoot instant snapshots troubleshoot standard snapshots troubleshoot reservations and commitments troubleshoot reservation creation troubleshoot reservation consumption troubleshooting reservation monitoring troubleshoot reservation updates troubleshoot future reservation creation and updates troubleshoot automatic commitment renewal troubleshoot quota errors troubleshoot concurrent operation quota errors troubleshoot workload authentication troubleshoot default service accounts troubleshoot workload to workload authentication ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation compute compute engine guides send feedback about hyperdisk balanced stay organized with collections save and categorize content based on your preferences this document describes the features of hyperdisk balanced the general purpose hyperdisk type hyperdisk balanced is the best fit for most workloads and offers the best combination of price and performance for total cost of ownership for more information about hyperdisk and the other hyperdisk types see about hyperdisk you can specify up to 160 000 iops and 2 400 mib s of throughput for a single hyperdisk balanced volume hyperdisk balanced is designed for sub millisecond latencies to create a new hyperdisk balanced volume see create a hyperdisk volume use cases hyperdisk balanced is a good fit for most workloads including the following use cases databases like mysql and postgresql virtual desktop infrastructure vdi line of business lob applications instance boot disks if the machine series or tpu supports only hyperdisk the boot disk for such instances must be a hyperdisk balanced or hyperdisk balanced high availability volume machine series support you can use hyperdisk balanced with the following machine series a3 h100 a3 h200 a4 a4x a4x max c3 c3d c4 c4a c4d c4n g4 h3 h4d m1 m2 m3 m4 m4n n4 n4a n4d tpu v6e tpu7x x4 z3 about provisioned performance for hyperdisk balanced you don t have to provision performance when you create hyperdisk volumes if you don t provision performance compute engine creates the volume with default values that you can modify later for details about default values see default iops and throughput values if you know your performance needs you can specify iops and throughput limits for a hyperdisk balanced volume when you create the volume and you can change the provisioned values after you create the volume you can t specify an iops or throughput level if you don t specify a size important a hyperdisk volume can t reach its provisioned performance unless you attach it to a compute instance that supports that level of performance or higher for detailed performance limits for all supported instances by machine type see performance limits when attached to an instance size and performance limits the following limits apply to the size iops and throughput values you can specify for a hyperdisk balanced volume size between 4 gib and 64 tib the default size is 100 gib preview c4 supports a maximum hyperdisk balanced volume size of 128 tib for access to this feature contact hyperdisk questions google com iops between 3 000 and 160 000 iops for volumes less than 320 gib the range of iops values you can specify varies by size for details see limits for provisioned iops throughput between 140 and 2 400 mib s of throughput but the throughput value depends on how much iops you provision for details see limits for provisioned throughput limits for provisioned iops you can choose the iops limit for a hyperdisk balanced volume according to the following limits the minimum and maximum limits vary by size minimum configurable iops 4 or 5 gib volumes iops is fixed at 2 000 and 2 500 iops respectively 6 gib 64 tib at least 3 000 iops maximum configurable iops 6 319 gib volumes the maximum iops limit depends on the volume s size see the following table for more information 320 gib 64 tib volumes at most 160 000 iops to calculate the range of configurable iops values for a specific volume size use these formulas minimum iops 3 000 iops maximum iops min 500x 160 000 mib s where x is the volume s size the following table lists the limits for configurable iops for common volume sizes size gib configurable iops values 4 2 000 5 2 500 10 3 000 to 5 000 50 3 000 to 25 000 150 3 000 to 75 000 319 3 000 to 159 500 320 or more 3 000 to 160 000 limits for provisioned throughput the throughput limit that you specify must be within a range of allowed values the range depends on the volume s provisioned iops to determine the range of throughput limits for a given iops value p use the following formulas minimum throughput max 140 p 256 mib s maximum throughput min 2 400 p 4 mib s the following table lists the limits for some provisioned iops values and the corresponding throughput ranges if a size isn t listed use the preceding formula to calculate the allowable values provisioned iops configurable throughput mib s 2 000 140 to 500 2 500 140 to 625 3 000 140 to 750 4 000 140 to 1 000 8 000 140 to 2 000 32 000 140 to 2 400 40 000 156 to 2 400 64 000 250 to 2 400 150 000 585 to 2 400 160 000 625 to 2 400 default size iops and throughput values if you don t specify a size iops or throughput value when you create a hyperdisk balanced volume compute engine assigns default values the default size for hyperdisk balanced volumes is 100 gib the default iops and throughput are based on the following formulas where x is the volume s size in gib default iops volumes 6 gib or less 500x iops volumes between 6 gib and 26 666667 tib 6x 3 000 iops volumes larger than 26 666667 tib 160 000 iops default throughput volumes 6 gib or less 140 mib s volumes larger than 6 gib min 2 400 1 5x 140 mib s important a hyperdisk volume can t reach its provisioned performance unless you attach it to a compute instance that supports that level of performance or higher for detailed performance limits for all supported instances by machine type see performance limits when attached to an instance baseline performance hyperdisk balanced volumes include baseline or free performance the first 3 000 iops and 140 mib s of throughput that you provision for a volume are free performance you provision above the baseline amounts is billable performance and is not free if you provision a volume with 5 000 iops you re billed for 2 000 iops similar principles apply to throughput baseline performance is also included with hyperdisk balanced volumes that you create in the following hyperdisk storage pools standard performance hyperdisk storage pools standard capacity hyperdisk storage pools advanced capacity hyperdisk storage pools hyperdisk balanced volumes in advanced performance hyperdisk storage pools don t include baseline performance baseline performance and quota baseline iops and throughput don t affect the iops and throughput quota for a project s hyperdisk balanced and hyperdisk balanced high availability volumes for example if your project has a quota of 500 000 iops and you create a hyperdisk balanced volume with 3 000 iops then you still have a quota of 500 000 iops after you create the volume if you also create a hyperdisk balanced high availability volume with 4 000 iops then the project would have a remaining iops quota of 499 000 change the provisioned performance or size you can change the provisioned size of a hyperdisk balanced volume at most twice within a 4 hour window and you can change the provisioned performance at most once every 4 hours to learn how to modify size or performance see modify the size and provisioned performance of a hyperdisk volume performance limits when attached to an instance this section lists the performance limits for each machine type that supports hyperdisk balanced you can specify up to 160 000 iops and 2 400 mib s of throughput for a single hyperdisk balanced volume this section lists the maximum performance that hyperdisk balanced volumes can achieve for each supported instance a hyperdisk balanced 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 balanced volumes attached to the same instance regardless of each volume s provisioned performance achieve higher performance with multiple hyperdisk balanced volumes certain instances can exceed the maximum performance for a single hyperdisk balanced volume 160 000 iops or 2 400 mib per second mib s an instance can only achieve these higher limits if you attach multiple hyperdisk balanced volumes to the instance if an instance s performance limit in the following table exceeds 160 000 iops or 2 400 mib s then the instance can only achieve that limit if you attach multiple hyperdisk balanced volumes for example the performance limit for a c4a 72 instance using hyperdisk balanced is 240 000 iops and 5 000 mib s to achieve this maximum performance you must attach at least two hyperdisk balanced volumes to the instance 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 megagpu 8g 160 000 4 800 a3 highgpu 1g 120 000 1 800 a3 highgpu 2g 160 000 2 400 a3 highgpu 4g 160 000 4 800 a3 highgpu 8g 160 000 4 800 a3 edgegpu 8g 160 000 4 800 a3 a3 h200 a3 ultragpu 8g 1 320 000 10 000 a4 1 a4 highgpu 8g 1 320 000 10 000 a4x 1 a4x highgpu 4g 1 320 000 10 000 a4x max 1 a4x maxgpu 4g metal 1 320 000 12 500 c3 c3 4 25 000 400 c3 8 50 000 800 c3 22 120 000 1 800 c3 44 160 000 2 400 c3 88 160 000 4 800 c3 176 160 000 10 000 c3 192 160 000 10 000 c3d c3d 4 25 000 400 c3d 8 50 000 800 c3d 16 75 000 1 200 c3d 30 75 000 1 200 c3d 60 160 000 2 400 c3d 90 160 000 2 400 c3d 180 160 000 2 400 c3d 360 160 000 2 400 c4 1 c4 2 1 50 000 400 c4 4 1 50 000 400 c4 8 1 50 000 800 c4 16 1 100 000 1 600 c4 24 1 100 000 1 600 c4 32 1 100 000 1 600 c4 48 1 160 000 2 400 c4 96 1 240 000 4 800 c4 144 1 240 000 6 250 c4 192 1...
|
