logo

voc-s-2c-16gb-320s-amd by Vultr

voc-s-2c-16gb-320s-amd is a Optimized Cloud Compute (2 vCPUs, 16.0 GiB RAM, 320 GB NVMe) server offered by Vultr with 2 vCPUs, 16 GiB of memory and 320 GB of storage.
2 vCPU
16 GiB Memory
320 GB Storage
Spare SCore
6791
(All-cores)
3424
(Single-core)

Specifications

Server Metadata

Vendor ID
vultr
Name
voc-s-2c-16gb-320s-amd
Description
Optimized Cloud Compute (2 vCPUs, 16.0 GiB RAM, 320 GB NVMe)
Family
Optimized Cloud Compute
Hw Virt
Average Time To Start
120.5
Status
active
Observed At
2026-07-20T13:40:44.471856

Availability

REGION / IDSPOTONDEMAND

Processor

vCPUs
2
CPU Allocation
Shared
CPU Cores
1
CPU Speed
2 GHz
CPU Architecture
x86_64
CPU Manufacturer
AMD
CPU Family
EPYC
CPU L1D Cache
32 KiB
CPU L1D Cache Total
32 KiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
32 KiB
CPU L2 Cache
1 MiB
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, 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, svm, 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, avx512ifma, clflushopt, clwb, avx512cd, sha_ni, avx512bw, avx512vl, xsaveopt, xsaves, avx512_bf16, clzero, xsaveerptr, wbnoinvd, arat, npt, nrip_save, vnmi, avx512vbmi, umip, pku, ospke, avx512_vbmi2, gfni, vaes, vpclmulqdq, avx512_vnni, avx512_bitalg, avx512_vpopcntdq, la57, rdpid, fsrm
Ecpus
2
Scalability
200

System Resources and Accelerators

MEMORY
Memory Amount
16 GiB
Memory Amount Actual
16 GiB
GPU
GPU Count
0
GPU Memory Min
0 MiB
GPU Memory Total
0 MiB
GPUs
    STORAGE
    Storage Size
    320 GB
    Storage Type
    nvme ssd
    Storages
      NETWORK
      Inbound Traffic
      0 GB/month
      Outbound Traffic
      6144 GB/month
      IPv4
      1

      CPU and System Topology

      Server Description

      An AMD EPYC virtual server combining a high memory-to-core ratio with fast local NVMe storage for single-threaded and memory-dense workloads.

      Memory OptimizedStorage & DatabaseGeneral Purpose

      Vultr voc-s-2c-16gb-320s-amd is an AMD EPYC-based instance within the Optimized Cloud Compute family, featuring 2 vCPUs on a shared CPU allocation, 16.0 GB of RAM, and 320 GB of local NVMe SSD storage. Built on the x86_64 architecture, the processor operates at 2.0 GHz and supports AVX-512 and AES instruction sets. Benchmark data reveals top-tier single-core performance in stress-ng and strong single-threaded compression speeds, though multi-core CPU metrics, database operations, and static web serving throughput fall into lower percentiles. With an 8:1 memory-to-vCPU ratio and generous local storage, this instance provides a cost-efficient balance of memory and storage density. It is best suited for memory-optimized workloads, single-threaded processing tasks, lightweight caching, and development environments that do not require dedicated CPU cores or high multi-threaded throughput.

      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) 212,482 ops/sec 1,895,870 ops/sec 0.112 50.00% 50.00% -66.50%
      Redis RPS (pipeline=16, SET) 2,183,365 ops/sec 11,503,938 ops/sec 0.19 20.00% 20.00% -28.30%
      PassMark Memory Mark (composite) 2,387 2,410 0.99 10.00% 10.00% -0.10%
      Memory bandwidth (read, 16 MB ~ L3) 178,990 MB/sec 107,331 MB/sec 1.67 10.00% 10.00% +5.26%
      PassMark single-thread CPU 3,215 Mops/s 2,363 Mops/s 1.36 10.00% 10.00% +3.12%

      Memory Bandwidth

      Compression

      OpenSSL

      Passmark CPU Scores

      BENCHMARKSCORE
      Mark
      		5978
      Compression
      		57249
      Encryption
      		2862
      Extended Instructions
      		5228
      Floating Point Maths
      		11747
      Integer Maths
      		13390
      Physics
      		763
      Prime Numbers
      		42
      Single Threaded
      		3215
      String Sorting
      		8464

      Passmark Memory Scores

      BENCHMARKSCORE
      Memory Mark
      		2387
      Database Operations
      		1151
      Memory Latency
      		68
      Memory Read Cached
      		30787
      Memory Read Uncached
      		28564
      Memory Write
      		28523

      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
      voc-c-1c-2gb-25s-amd 12 GiB0
      voc-g-1c-4gb-30s-amd 14 GiB0
      voc-m-1c-8gb-50s-amd 18 GiB0
      voc-s-1c-8gb-150s-amd 18 GiB0
      voc-c-2c-4gb-50s-amd 24 GiB0
      voc-c-2c-4gb-75s-amd 24 GiB0
      voc-g-2c-8gb-50s-amd 28 GiB0

      Similar Servers

      INSTANCEVENDORvCPUsMEMORYGPUs

      voc-s-2c-16gb-320s-amd FAQs