CLOUDNATIVE-32xCPU-384GB by UpCloud

CLOUDNATIVE-32xCPU-384GB is a Cloud Native (32 vCPUs, 384 GiB RAM) server offered by UpCloud with 32 vCPUs, 384 GiB of memory and 0 GB of storage. The pricing starts at 1.4699 USD per hour.
32 vCPU
384 GiB Memory
Spare SCore
21,669
(All-cores)
748
(Single-core)

Specifications

Server Metadata

Vendor ID
upcloud
Name
CLOUDNATIVE-32xCPU-384GB
Description
Cloud Native (32 vCPUs, 384 GiB RAM)
Family
Cloud Native
Hw Virt
Average Time To Start
121
Status
active
Observed At
2026-10-05T09:39:14.551876

Availability

REGION / IDSPOTONDEMAND
Sydney #1 (AU) / au-syd1
- 1.4699 USD/h
Frankfurt #1 (DE) / de-fra1
- 1.4699 USD/h
Copenhagen #1 (DK) / dk-cph1
- 1.4699 USD/h
Madrid #1 (ES) / es-mad1
- 1.4699 USD/h
Helsinki #1 (FI) / fi-hel1
- 1.4699 USD/h
Helsinki #2 (FI) / fi-hel2
- 1.4699 USD/h
Amsterdam #1 (NL) / nl-ams1
- 1.4699 USD/h
Stavanger #1 (NO) / no-svg1
- 1.4699 USD/h
Warsaw #1 (PL) / pl-waw1
- 1.4699 USD/h
Stockholm #1 (SE) / se-sto1
- 1.4699 USD/h
Singapore #1 (SG) / sg-sin1
- 1.4699 USD/h
London #1 (GB) / uk-lon1
- 1.4699 USD/h
Chicago #1 (US) / us-chi1
- 1.4699 USD/h
New York #1 (US) / us-nyc1
- 1.4699 USD/h
San Jose #1 (US) / us-sjo1
- 1.4699 USD/h

Processor

vCPUs
32
Hypervisor
KVM
CPU Allocation
Shared
CPU Cores
32
CPU Speed
2 GHz
CPU Architecture
x86_64
CPU Manufacturer
AMD
CPU Family
EPYC
CPU Model
7542
CPU L1D Cache
64 KiB
CPU L1D Cache Total
2 MiB
CPU L1I Cache
64 KiB
CPU L1I Cache Total
2 MiB
CPU L2 Cache
512 KiB
CPU L2 Cache Total
16 MiB
CPU L3 Cache
16 MiB
CPU L3 Cache Total
16 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, sse4_1, sse4_2, x2apic, movbe, popcnt, tsc_deadline_timer, aes, xsave, avx, f16c, rdrand, hypervisor, lahf_lm, cmp_legacy, cr8_legacy, abm, sse4a, misalignsse, 3dnowprefetch, osvw, perfctr_core, ssbd, ibrs, ibpb, stibp, vmmcall, fsgsbase, tsc_adjust, bmi1, avx2, smep, bmi2, rdseed, adx, smap, clflushopt, clwb, sha_ni, xsaveopt, xsavec, xgetbv1, clzero, xsaveerptr, wbnoinvd, arat, umip, rdpid, arch_capabilities
Ecpus
29
Scalability
90.62

System Resources and Accelerators

MEMORY
Memory Amount
384 GiB
Memory Amount Actual
384 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
      76800 GB/month
      IPv4
      1

      CPU and System Topology

      Server Description

      A memory-optimized virtual server featuring thirty-two shared cores and high memory density for memory-intensive, multi-threaded workloads.

      Memory OptimizedBurstable & BudgetGeneral Purpose

      UpCloud CLOUDNATIVE-32xCPU-384GB is an x86_64 memory-optimized virtual server built on the KVM hypervisor. It features 32 shared vCPUs powered by an AMD EPYC 7542 processor running at 2.0 GHz, paired with 384.0 GB of system memory, yielding 12.0 GB of RAM per core. The server does not include local storage or GPU accelerators. Performance benchmarks show a distinct tradeoff: single-core stress-ng performance is in the bottom 10%, whereas Geekbench multi-core and multi-threaded bzip3 decompression scores rank in the top 25%. Most other metrics, including memory bandwidth and Redis SET operations, perform in the average middle 50% tier. This resource profile is suited for memory-intensive workloads such as database operations, caching, and multi-threaded text processing where shared CPU allocation is acceptable.

      Economics

      Average Price per Region

      Prices per Zone

      Lowest Prices

      Performance

      Workload Profiles

      1.3Score
      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) 2,631,133 ops/sec 1,916,704 ops/sec 1.4 50.00% 50.00% +18.00%
      Redis RPS (pipeline=16, SET) 20,743,797 ops/sec 11,642,227 ops/sec 1.8 20.00% 20.00% +12.00%
      PassMark Memory Mark (composite) 2,007 2,417 0.83 10.00% 10.00% -1.80%
      Memory bandwidth (read, 16 MB ~ L3) 150,309 MB/sec 108,361 MB/sec 1.4 10.00% 10.00% +3.40%
      PassMark single-thread CPU 2,010 Mops/s 2,365 Mops/s 0.83 10.00% 10.00% -1.80%

      Memory Bandwidth

      Compression

      OpenSSL

      Geekbench Single-Core

      Score: 1,980

      Geekbench Multi-Core

      Score: 17,094

      Passmark CPU Scores

      BENCHMARKSCORE
      Mark
      42176
      Compression
      591505
      Encryption
      34362
      Extended Instructions
      47475
      Floating Point Maths
      98167
      Integer Maths
      135556
      Physics
      5120
      Prime Numbers
      344
      Single Threaded
      2010
      String Sorting
      75935

      Passmark Memory Scores

      BENCHMARKSCORE
      Memory Mark
      2007
      Database Operations
      15772
      Memory Latency
      85
      Memory Read Cached
      22318
      Memory Read Uncached
      8767
      Memory Write
      8815

      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

      PostgreSQL heavy read-only throughput

      Alternatives

      Similar Servers

      INSTANCEVENDORvCPUsMEMORYGPUs

      CLOUDNATIVE-32xCPU-384GB FAQs