h4d-standard-192 by Google Cloud Platform

h4d-standard-192 is a 192 vCPUs, 744 GB RAM server offered by Google Cloud Platform with 192 vCPUs, 720 GiB of memory and 0 GB of storage. The pricing starts at 2.7497 USD per hour.
192 vCPU
720 GiB Memory
Spare SCore
655,072
(All-cores)
3,461
(Single-core)

Specifications

Server Metadata

Vendor ID
gcp
Server ID
999904050
Name
h4d-standard-192
Description
192 vCPUs, 744 GB RAM
Family
h4d
Hw Virt
Average Time To Start
31
Status
active
Observed At
2026-09-17T10:07:32.463187

Availability

REGION / IDSPOTONDEMAND
Council Bluffs (US) / us-central1
3.6374 USD/h 7.8538 USD/h
Moncks Corner (US) / us-east1
3.6374 USD/h 7.8538 USD/h
Eemshaven (NL) / europe-west4
2.88 USD/h 8.4035 USD/h
Jurong West (SG) / asia-southeast1
3.3262 USD/h 10.2097 USD/h
Mumbai (IN) / asia-south1
2.7497 USD/h 10.9953 USD/h

Processor

vCPUs
192
CPU Allocation
Dedicated
CPU Cores
192
CPU Architecture
x86_64
CPU Manufacturer
AMD
CPU Family
EPYC
CPU Model
9B45
CPU L1D Cache
48 KiB
CPU L1D Cache Total
9 MiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
6 MiB
CPU L2 Cache
1 MiB
CPU L2 Cache Total
192 MiB
CPU L3 Cache
32 MiB
CPU L3 Cache Total
768 MiB
CPU Flags
fpu, vme, de, pse, tsc, msr, pae, mce, cx8, apic, sep, mtrr, pge, mca, cmov, pat, pse36, clflush, mmx, fxsr, sse, sse2, ht, syscall, nx, mmxext, fxsr_opt, pdpe1gb, rdtscp, lm, constant_tsc, rep_good, nopl, xtopology, nonstop_tsc, cpuid, extd_apicid, tsc_known_freq, pni, pclmulqdq, monitor, ssse3, fma, cx16, pcid, sse4_1, sse4_2, x2apic, movbe, popcnt, aes, xsave, avx, f16c, rdrand, hypervisor, lahf_lm, cmp_legacy, cr8_legacy, abm, sse4a, misalignsse, 3dnowprefetch, osvw, topoext, mwaitx, ssbd, ibrs, ibpb, stibp, ibrs_enhanced, vmmcall, fsgsbase, tsc_adjust, bmi1, avx2, smep, bmi2, invpcid, avx512f, avx512dq, rdseed, adx, smap, avx512ifma, clflushopt, clwb, avx512cd, sha_ni, avx512bw, avx512vl, xsaveopt, xsavec, xgetbv1, xsaves, avx_vnni, avx512_bf16, clzero, xsaveerptr, wbnoinvd, arat, avx512vbmi, umip, pku, ospke, avx512_vbmi2, gfni, vaes, vpclmulqdq, avx512_vnni, avx512_bitalg, avx512_vpopcntdq, rdpid, movdiri, movdir64b, avx512_vp2intersect, flush_l1d
Ecpus
189.3
Scalability
98.59

System Resources and Accelerators

MEMORY
Memory Amount
720 GiB
Memory Amount Actual
720 GiB
GPU
GPU Count
0
GPU Memory Min
0 MiB
GPU Memory Total
0 MiB
GPUs
    STORAGE
    Storage Size
    0 GB
    Storages
      NETWORK
      Inbound Traffic
      0 GB/month
      Outbound Traffic
      0 GB/month
      IPv4
      0

      CPU and System Topology

      Server Description

      A dedicated 192-core AMD EPYC server with high memory bandwidth, optimized for massive parallel processing and high-throughput database workloads.

      General PurposeCompute Optimized

      Google Cloud Platform h4d-standard-192 is an x86_64 server from the h4d family, featuring 192 dedicated physical AMD EPYC 9B45 cores with a 1.0 thread-per-core configuration and 720.0 GB of RAM. Lacking local storage and GPU accelerators, this instance relies on external storage and is optimized for pure CPU-bound execution. Benchmark results place the server in the top 10% tier, highlighted by a stress-ng multi-core score of 655,072.06, a Redis SET performance of 495.56 million operations per second, and a static web serving throughput of 187.5 GB/sec. Memory read bandwidth reaches 1,054.65 GB/sec for large blocks. This configuration is highly efficient for large-scale database operations, high-throughput web serving, and parallelized CPU-bound workloads.

      Economics

      Average Price per Region

      Prices per Zone

      Lowest Prices

      Performance

      Workload Profiles

      14.5Score
      Precomputed compound score for Cache Intensive workloads. A weighted average (geometric mean) of benchmark scores compared to their medians: score = ∏ (x_i / m_i)^(w_i / Σw). The score of 1.0 represents a synthetic baseline server with the median performance of each component benchmark; 0.5 means roughly half the performance; and 2.0 means twice the performance of that reference profile. Component weights: 50% Redis RPS (pipeline=1, SET), 20% Redis RPS (pipeline=16, SET), 10% PassMark Memory Mark (composite), 10% Memory bandwidth (read, 16 MB ~ L3), 10% PassMark single-thread CPU. Rationale for component selection: In-memory key-value store workload, mixing direct Redis performance metrics with memory speed and latency benchmarks, and single-core CPU performance profiles.
      Component Score Weight Impact
      Raw Reference Normalized Target Actual
      Redis RPS (pipeline=1, SET) 55,368,606 ops/sec 1,919,696 ops/sec 28.8 50.00% 50.00% +437.00%
      Redis RPS (pipeline=16, SET) 358,879,158 ops/sec 11,736,081 ops/sec 30.6 20.00% 20.00% +98.20%
      PassMark Memory Mark (composite) 3,134 2,418 1.3 10.00% 10.00% +2.66%
      Memory bandwidth (read, 16 MB ~ L3) 1,291,867 MB/sec 108,260 MB/sec 11.9 10.00% 10.00% +28.10%
      PassMark single-thread CPU 3,470 Mops/s 2,365 Mops/s 1.47 10.00% 10.00% +3.93%

      Memory Bandwidth

      Compression

      OpenSSL

      Passmark CPU Scores

      BENCHMARKSCORE
      Mark
      		 175336
      Compression
      		 5186485
      Encryption
      		 274651
      Extended Instructions
      		 441027
      Floating Point Maths
      		 1313816
      Integer Maths
      		 1332769
      Physics
      		 61420
      Prime Numbers
      		 4299
      Single Threaded
      		 3470
      String Sorting
      		 671666

      Passmark Memory Scores

      BENCHMARKSCORE
      Memory Mark
      		 3134
      Database Operations
      		 45604
      Memory Latency
      		 73
      Memory Read Cached
      		 31086
      Memory Read Uncached
      		 30795
      Memory Write
      		 31080

      Stress-ng Raw Scores

      Stress-ng Relative Multicore Performance

      Static Web Server

      Redis

      PostgreSQL heavy read-only throughput

      Alternatives

      Servers of the Same Family

      INSTANCEvCPUsMEMORYGPUs
      h4d-highmem-192 1921488 GiB0
      h4d-highmem-192-lssd 1921488 GiB0

      Similar Servers

      INSTANCEVENDORvCPUsMEMORYGPUs

      h4d-standard-192 FAQs