logo

cpx32 by Hetzner Cloud

cpx32 is a CPX 32 server offered by Hetzner Cloud with 4 vCPUs, 8 GiB of memory and 160 GB of storage. The pricing starts at 0.0649 USD per hour.
4 vCPU
8 GiB Memory
160 GB Storage
Spare SCore
12107
(All-cores)
3041
(Single-core)

Specifications

Server Metadata

Vendor ID
hcloud
Server ID
110
Name
cpx32
Description
CPX 32
Family
cpx
Hw Virt
Status
active
Observed At
2026-07-23T02:02:12.624020

Availability

REGION / IDSPOTONDEMAND
Nuremberg (DE) / nbg1-dc3
- 0.0649 USD/h
Helsinki (FI) / hel1-dc2
- 0.0649 USD/h
Falkenstein (DE) / fsn1-dc14
- 0.0649 USD/h
Singapore (SG) / sin-dc1
- 0.0896 USD/h

Processor

vCPUs
4
Hypervisor
QEMU
CPU Allocation
Shared
CPU Cores
4
CPU Speed
2 GHz
CPU Architecture
x86_64
CPU Manufacturer
AMD
CPU Family
EPYC
CPU L1D Cache
32 KiB
CPU L1D Cache Total
128 KiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
128 KiB
CPU L2 Cache
1 MiB
CPU L2 Cache Total
4 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, rep_good, nopl, 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, perfctr_core, ssbd, ibrs, ibpb, stibp, ibrs_enhanced, vmmcall, fsgsbase, bmi1, avx2, smep, bmi2, erms, invpcid, avx512f, avx512dq, rdseed, adx, smap, avx512ifma, clflushopt, clwb, avx512cd, sha_ni, avx512bw, avx512vl, xsaveopt, xsavec, xgetbv1, xsaves, avx512_bf16, clzero, xsaveerptr, wbnoinvd, arat, avx512vbmi, umip, pku, ospke, avx512_vbmi2, gfni, vaes, vpclmulqdq, avx512_vnni, avx512_bitalg, avx512_vpopcntdq, la57, rdpid, fsrm
Ecpus
4
Scalability
100

System Resources and Accelerators

MEMORY
Memory Amount
8 GiB
Memory Amount Actual
8 GiB
GPU
GPU Count
0
GPU Memory Min
0 MiB
GPU Memory Total
0 MiB
GPUs
    STORAGE
    Storage Size
    160 GB
    Storage Type
    nvme ssd
    Storages
      NETWORK
      Inbound Traffic
      0 GB/month
      Outbound Traffic
      20480 GB/month
      IPv4
      0

      CPU and System Topology

      Server Description

      A budget-friendly virtual server combining shared AMD EPYC processors and fast NVMe storage for single-thread intensive workloads.

      Compute OptimizedBurstable & Budget

      Hetzner Cloud cpx32 is an x86_64 virtual server featuring 4 shared AMD EPYC vCPUs running at 2.0 GHz, 8.0 GB of RAM, and a bundled 160 GB NVMe SSD. Operating under a QEMU hypervisor, this server delivers strong single-core performance, highlighted by a Geekbench single-core score of 1975.0 and a stress-ng single-core score of 3040.68. Multi-core capabilities, memory read bandwidth, and cryptographic operations perform in the average tier, while static web serving throughput represents a relative bottleneck. Lacking dedicated CPU cores and public IPv4 addresses, the cpx32 provides a cost-efficient, compute-leaning resource profile. It is best suited for software compilation, development environments, and lightweight background processing tasks that leverage its fast NVMe storage and strong single-threaded execution without requiring sustained, dedicated multi-core performance.

      Economics

      Average Price per Region

      Prices per Zone

      Lowest Prices

      Performance

      Workload Profiles

      0.474Score
      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) 523,002 ops/sec 1,896,415 ops/sec 0.276 50.00% 50.00% -47.50%
      Redis RPS (pipeline=16, SET) 4,755,948 ops/sec 11,539,523 ops/sec 0.412 20.00% 20.00% -16.30%
      PassMark Memory Mark (composite) 1,925 2,411 0.798 10.00% 10.00% -2.23%
      Memory bandwidth (read, 16 MB ~ L3) 235,986 MB/sec 107,368 MB/sec 2.2 10.00% 10.00% +8.20%
      PassMark single-thread CPU 2,860 Mops/s 2,363 Mops/s 1.21 10.00% 10.00% +1.92%

      Memory Bandwidth

      Compression

      OpenSSL

      Geekbench Single-Core

      Score: 1,975

      Geekbench Multi-Core

      Score: 6,058

      Passmark CPU Scores

      BENCHMARKSCORE
      Mark
      		 10494
      Compression
      		 103914
      Encryption
      		 5136
      Extended Instructions
      		 9511
      Floating Point Maths
      		 21007
      Integer Maths
      		 23918
      Physics
      		 1377
      Prime Numbers
      		 76
      Single Threaded
      		 2860
      String Sorting
      		 15265

      Passmark Memory Scores

      BENCHMARKSCORE
      Memory Mark
      		 1925
      Database Operations
      		 4225
      Memory Latency
      		 71
      Memory Read Cached
      		 26865
      Memory Read Uncached
      		 25912
      Memory Write
      		 25797

      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

      INSTANCEvCPUsMEMORYGPUs
      cpx12 12 GiB0
      cpx11 22 GiB0
      cpx22 24 GiB0
      cpx21 34 GiB0
      cpx31 48 GiB0
      cpx42 816 GiB0
      cpx41 816 GiB0

      Similar Servers

      INSTANCEVENDORvCPUsMEMORYGPUs

      cpx32 FAQs