logo

vx1-m-64c-512gb by Vultr

vx1-m-64c-512gb is a VX1 Cloud Compute (64 vCPUs, 512.0 GiB RAM) server offered by Vultr with 64 vCPUs, 512 GiB of memory and 1 GB of storage.
64 vCPU
512 GiB Memory
1 GB Storage
Spare SCore
118152
(All-cores)
3710
(Single-core)

Specifications

Server Metadata

Vendor ID
vultr
Name
vx1-m-64c-512gb
Description
VX1 Cloud Compute (64 vCPUs, 512.0 GiB RAM)
Family
VX1 Cloud Compute
Hw Virt
Average Time To Start
44
Status
active
Observed At
2026-07-20T13:40:44.474042

Availability

REGION / IDSPOTONDEMAND

Processor

vCPUs
64
CPU Allocation
Shared
CPU Cores
32
CPU Speed
2 GHz
CPU Architecture
x86_64
CPU Manufacturer
AMD
CPU Family
EPYC
CPU L1D Cache
48 KiB
CPU L1D Cache Total
2 MiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
1 MiB
CPU L2 Cache
1 MiB
CPU L2 Cache Total
32 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, adx, smap, avx512ifma, clflushopt, clwb, avx512cd, sha_ni, avx512bw, avx512vl, xsaveopt, xsavec, xgetbv1, xsaves, avx_vnni, avx512_bf16, clzero, xsaveerptr, wbnoinvd, arat, npt, lbrv, nrip_save, tsc_scale, vmcb_clean, flushbyasid, pausefilter, pfthreshold, v_vmsave_vmload, vgif, vnmi, avx512vbmi, umip, pku, ospke, avx512_vbmi2, gfni, vaes, vpclmulqdq, avx512_vnni, avx512_bitalg, avx512_vpopcntdq, la57, rdpid, movdiri, movdir64b, fsrm, avx512_vp2intersect, srso_user_kernel_no
Ecpus
31.8
Scalability
99.38

System Resources and Accelerators

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

      CPU and System Topology

      Server Description

      An x86_64 server offering 512 GB of RAM and 64 shared vCPUs for memory-intensive database and data processing workloads.

      Memory OptimizedGeneral PurposeBurstable & Budget

      The Vultr vx1-m-64c-512gb is an x86_64 memory-optimized server from the VX1 Cloud Compute family, featuring 64 vCPUs and 512.0 GB of RAM. Powered by an AMD EPYC processor running at 2.0 GHz, it provides 8.0 GB of memory per core. Tradeoffs include a shared CPU allocation and a minimal 1 GB network-attached local storage volume. In benchmark evaluations, the instance delivers top-tier performance, particularly in PassMark database operations and large-block memory bandwidth, which reaches 532.73 GB/sec for reads. It also shows strong capabilities in multi-threaded decompression and small-model LLM inference. This hardware profile is well-suited for memory-intensive workloads such as large-scale database operations, caching layers, and data processing tasks that can tolerate shared CPU resources.

      Economics

      Average Price per Region

      Prices per Zone

      Lowest Prices

      Performance

      Workload Profiles

      5.07Score
      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) 14,220,394 ops/sec 1,895,870 ops/sec 7.5 50.00% 50.00% +174.00%
      Redis RPS (pipeline=16, SET) 75,244,195 ops/sec 11,503,938 ops/sec 6.54 20.00% 20.00% +45.60%
      PassMark Memory Mark (composite) 2,837 2,410 1.18 10.00% 10.00% +1.67%
      Memory bandwidth (read, 16 MB ~ L3) 640,491 MB/sec 107,331 MB/sec 5.97 10.00% 10.00% +19.60%
      PassMark single-thread CPU 3,751 Mops/s 2,363 Mops/s 1.59 10.00% 10.00% +4.75%

      Memory Bandwidth

      Compression

      OpenSSL

      Passmark CPU Scores

      BENCHMARKSCORE
      Mark
      		98920
      Compression
      		1491053
      Encryption
      		83297
      Extended Instructions
      		112380
      Floating Point Maths
      		254091
      Integer Maths
      		417319
      Physics
      		15582
      Prime Numbers
      		978
      Single Threaded
      		3751
      String Sorting
      		187809

      Passmark Memory Scores

      BENCHMARKSCORE
      Memory Mark
      		2837
      Database Operations
      		42061
      Memory Latency
      		85
      Memory Read Cached
      		33420
      Memory Read Uncached
      		31834
      Memory Write
      		32157

      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
      vx1-g-2c-8g 28 GiB0
      vx1-g-2c-8g-120s 28 GiB0
      vx1-m-2c-16g 216 GiB0
      vx1-m-2c-16g-120s 216 GiB0
      vx1-g-4c-16g 416 GiB0
      vx1-g-4c-16g-240s 416 GiB0
      vx1-m-4c-32g-240s 432 GiB0

      Similar Servers

      INSTANCEVENDORvCPUsMEMORYGPUs

      vx1-m-64c-512gb FAQs