n2d-highmem-4 by Google Cloud Platform

n2d-highmem-4 is a 4 vCPUs 32 GB RAM server offered by Google Cloud Platform with 4 vCPUs, 32 GiB of memory and 0 GB of storage. The pricing starts at 0.063 USD per hour.
4 vCPU
32 GiB Memory
Spare SCore
5,387
(All-cores)
2,681
(Single-core)

Specifications

Server Metadata

Vendor ID
gcp
Server ID
912004
Name
n2d-highmem-4
API Reference Object
-
Description
4 vCPUs 32 GB RAM
Family
n2d
Hw Virt
Average Time To Start
17
Status
active
Observed At
2026-10-17T04:44:18.154510

Availability

REGION / IDSPOTONDEMAND
Mumbai (IN) / asia-south1
0.09 USD/h 0.1505 USD/h
Columbus (US) / us-east5
0.0774 USD/h 0.228 USD/h
Council Bluffs (US) / us-central1
0.1103 USD/h 0.228 USD/h
The Dalles (US) / us-west1
0.1103 USD/h 0.228 USD/h
Moncks Corner (US) / us-east1
0.1103 USD/h 0.228 USD/h
Tel Aviv (IL) / me-west1
0.0785 USD/h 0.2508 USD/h
Johannesburg (ZA) / africa-south1
0.1257 USD/h 0.2508 USD/h
St. Ghislain (BE) / europe-west1
0.1505 USD/h 0.2508 USD/h
Toronto (CA) / northamerica-northeast2
0.1358 USD/h 0.251 USD/h
Eemshaven (NL) / europe-west4
0.1359 USD/h 0.251 USD/h
Hamina (FI) / europe-north1
0.1441 USD/h 0.251 USD/h
Montréal (CA) / northamerica-northeast1
0.1494 USD/h 0.251 USD/h
Las Vegas (US) / us-west4
0.08 USD/h 0.2567 USD/h
Ashburn (US) / us-east4
0.1391 USD/h 0.2567 USD/h
Changhua County (TW) / asia-east1
0.1429 USD/h 0.264 USD/h
Milan (IT) / europe-west8
0.0678 USD/h 0.2644 USD/h
Paris (FR) / europe-west9
0.1038 USD/h 0.2644 USD/h
Dallas (US) / us-south1
0.1126 USD/h 0.269 USD/h
Madrid (ES) / europe-southwest1
0.1614 USD/h 0.269 USD/h
Salt Lake City (US) / us-west3
0.1041 USD/h 0.2738 USD/h
Los Angeles (US) / us-west2
0.1479 USD/h 0.2738 USD/h
Delhi (IN) / asia-south2
0.1635 USD/h 0.2738 USD/h
Melbourne (AU) / australia-southeast2
0.0814 USD/h 0.275 USD/h
Warsaw (PL) / europe-central2
0.165 USD/h 0.2758 USD/h
Doha (QA) / me-central1
0.1203 USD/h 0.277 USD/h
Jurong West (SG) / asia-southeast1
0.063 USD/h 0.2812 USD/h
Tokyo (JP) / asia-northeast1
0.1749 USD/h 0.2922 USD/h
Osaka (JP) / asia-northeast2
0.0687 USD/h 0.2928 USD/h
Seoul (KR) / asia-northeast3
0.0757 USD/h 0.2928 USD/h
Berlin (DE) / europe-west10
0.079 USD/h 0.2937 USD/h
Frankfurt (DE) / europe-west3
0.1586 USD/h 0.2937 USD/h
London (GB) / europe-west2
0.1762 USD/h 0.2937 USD/h
Turin (IT) / europe-west12
0.0689 USD/h 0.2941 USD/h
Zurich (CH) / europe-west6
0.1617 USD/h 0.2986 USD/h
Jakarta (ID) / asia-southeast2
0.1254 USD/h 0.3065 USD/h
Hong Kong / asia-east2
0.1607 USD/h 0.3189 USD/h
Sydney (AU) / australia-southeast1
0.1936 USD/h 0.3235 USD/h
Santiago (CL) / southamerica-west1
0.0922 USD/h 0.326 USD/h
Osasco (BR) / southamerica-east1
0.1134 USD/h 0.3619 USD/h
Dammam (SA) / me-central2
0.0822 USD/h 0.3647 USD/h

Processor

vCPUs
4
CPU Allocation
Dedicated
CPU Cores
2
CPU Architecture
x86_64
CPU Manufacturer
AMD
CPU Family
EPYC
CPU Model
7B13
CPU L1D Cache
32 KiB
CPU L1D Cache Total
64 KiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
64 KiB
CPU L2 Cache
512 KiB
CPU L2 Cache Total
1 MiB
CPU L3 Cache
32 MiB
CPU L3 Cache Total
32 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, nonstop_tsc, cpuid, extd_apicid, tsc_known_freq, pni, pclmulqdq, 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, ssbd, ibrs, ibpb, stibp, vmmcall, fsgsbase, tsc_adjust, bmi1, avx2, smep, bmi2, erms, invpcid, rdseed, adx, smap, clflushopt, clwb, sha_ni, xsaveopt, xsavec, xgetbv1, clzero, xsaveerptr, arat, npt, nrip_save, umip, vaes, vpclmulqdq, rdpid, fsrm
Ecpus
2
Scalability
50

System Resources and Accelerators

MEMORY
Memory Amount
32 GiB
Memory Amount Actual
32 GiB
ACCELERATORS
Accelerator Count
0
Accelerator Memory Min
0 MiB
Accelerator Memory Total
0 MiB
Accelerators
    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 memory-dense cloud instance featuring 32 GB RAM across 4 vCPUs, designed for memory-intensive applications requiring modest concurrent CPU performance.

      Memory OptimizedGeneral Purpose

      Google Cloud Platform n2d-highmem-4 is a memory-optimized cloud server powered by an AMD EPYC 7B13 x86_64 processor. Configured with 4 dedicated vCPUs across 2 physical cores and 32 GB of system RAM, it maintains a generous 1:8 core-to-memory ratio. The processor includes 32 MB of L3 cache alongside AES, VAES, and SHA-NI encryption extensions, though it lacks local storage drives and GPU accelerators. Benchmark evaluations highlight strong single-core compute performance in stress-ng tests and average encryption processing, contrasted by weak multi-core scaling and uncached memory read bandwidth. With a PassMark memory score in the middle tier and 4.29 million Redis SET operations per second, this instance delivers adequate qualitative cost efficiency for memory-heavy, moderate-concurrency workloads. It is best suited for small in-memory caches, light database management, and RAM-bound background services.

      Economics

      Average Price per Region

      Prices per Zone

      Lowest Prices

      Performance

      Workload Profiles

      0.26Score
      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) 306,410 ops/sec 1,917,050 ops/sec 0.16 50.00% 50.00% -60.00%
      Redis RPS (pipeline=16, SET) 2,322,693 ops/sec 11,661,818 ops/sec 0.19 20.00% 20.00% -28.00%
      PassMark Memory Mark (composite) 2,031 2,417 0.83 10.00% 10.00% -1.80%
      Memory bandwidth (read, 16 MB ~ L3) 46,104 MB/sec 108,361 MB/sec 0.42 10.00% 10.00% -8.30%
      PassMark single-thread CPU 2,317 Mops/s 2,365 Mops/s 0.96 10.00% 10.00% -0.41%

      Memory Bandwidth

      Compression

      OpenSSL

      Geekbench Single-Core

      Score: 1,426

      Geekbench Multi-Core

      Score: 3,257

      Passmark CPU Scores

      BENCHMARKSCORE
      Mark
      6022
      Compression
      61994
      Encryption
      4248
      Extended Instructions
      3466
      Floating Point Maths
      9118
      Integer Maths
      16446
      Physics
      745
      Prime Numbers
      36
      Single Threaded
      2317
      String Sorting
      8859

      Passmark Memory Scores

      BENCHMARKSCORE
      Memory Mark
      2031
      Database Operations
      1598
      Memory Latency
      76
      Memory Read Cached
      21726
      Memory Read Uncached
      13418
      Memory Write
      13622

      Stress-ng Raw Scores

      Stress-ng Relative Multicore Performance

      LLM Inference Speed for Prompt Processing

      LLM Inference Speed for Text Generation

      Static Web Server

      Redis

      Alternatives

      Servers of the Same Family

      INSTANCEvCPUsMEMORYAccelerators
      n2d-highcpu-2 22 GiB0
      n2d-standard-2 28 GiB0
      n2d-highmem-2 216 GiB0
      n2d-highcpu-4 44 GiB0
      n2d-standard-4 416 GiB0
      n2d-highcpu-8 88 GiB0
      n2d-standard-8 832 GiB0

      Similar Servers

      INSTANCEVENDORvCPUsMEMORYAccelerators

      n2d-highmem-4 FAQs