h200-1920 is a 224 vCPUs, 1920 GiB RAM, 8080 GB NVMe, 8xH200 141 GiB VRAM server offered by OVHcloud with 224 vCPUs, 1920 GiB of memory and 8.08 TB of storage.
An ultra-high-density GPU server featuring eight NVIDIA Hopper H200 accelerators, massive system memory, and high-speed local NVMe storage.
GPU AcceleratedMemory OptimizedCompute Optimized
OVHcloud h200-1920 is a dedicated GPU-accelerated server designed for massive parallel computing workloads. Running on a KVM hypervisor with an x86_64 architecture, it features 224 dedicated vCPUs clocked at 3.0 GHz and 1920.0 GB of system memory, yielding 8.57 GB of RAM per core. The server is equipped with eight NVIDIA Hopper H200 GPUs, providing a total of 1128 GB of VRAM. Storage is supported by 8080 GB of local NVMe SSDs, while network performance is anchored by a 25 Gbps baseline bandwidth. One complimentary public IPv4 address is included. This hardware profile is engineered for resource-intensive workloads such as large language model training, complex AI inference, and high-performance data science simulations.
Economics
Average Price per Region
Prices per Zone
Lowest Prices
Workload Profiles
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.
Precomputed compound score for CI/CD Build 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% Geekbench Clang compilation (multi-core), 10% Geekbench Clang compilation (single-core), 20% stress-ng div16 best-N cores, 5% PassMark integer math, 5% PassMark compression, 5% Brotli compression (multi-core, level 0), 5% PassMark string sorting. Rationale for component selection: Build performance is mainly driven by multi-core compilation throughput, but also bundles single-core compilation speed and general CPU performance, multi-core compression and text/scripting processing.
Precomputed compound score for Compute Heavy Applications 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: 15% stress-ng div16 best-N cores, 10% stress-ng div16 single core, 20% PassMark CPU Mark (composite), 10% Memory bandwidth (read, 64 MB), 15% PassMark floating point, 15% PassMark AVX/SSE/FMA (SIMD), 10% PassMark integer math, 5% PassMark physics simulation. Rationale for component selection: Number-crunching workload augmenting raw CPU performance stressing, general CPU performance benchmarks, memory bandwidth, and pure math computation speed like floating point, integer, SIMD (AVX/SSE/FMA) operations.
Precomputed compound score for Data Analysis 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: 70% PassMark CPU Mark (composite), 10% Gzip compression (single-core, level 5), 10% Memory bandwidth (read, 64 MB), 10% PassMark Memory Mark (composite). Rationale for component selection: Data analysis and ETL workloads are memory-bandwidth-bound and CPU-throughput-driven. The profile combines general CPU performance and memory bandwidth/latency as the primary drivers, supplemented by single-core compression speed as a proxy for serialisation-heavy ETL tasks.
Precomputed compound score for LLM Inference 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: 15% LLM text generation (SmolLM-135M, 128 tok), 15% LLM prompt processing (SmolLM-135M, 512 tok), 15% LLM text generation (Llama 7B, 128 tok), 15% LLM prompt processing (Llama 7B, 512 tok), 15% LLM text generation (Llama-3.3 70B, 128 tok), 15% LLM prompt processing (Llama-3.3 70B, 512 tok), 5% Memory bandwidth (read, 256 MB), 2% PassMark AVX/SSE/FMA (SIMD), 2% PassMark floating point. Rationale for component selection: VRAM and memory-bandwidth-bound LLM inference workload, using direct LLM speed benchmarks at three model sizes, and supplementing with raw memory bandwidth and SIMD performance benchmarks.
Precomputed compound score for Web Server 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: 30% Static web RPS (1 kB, 8 conn/vCPU), 20% Static web RPS (64 kB, 8 conn/vCPU), 20% Static web throughput (256 kB, 8 conn/vCPU), 20% OpenSSL AES-256-CBC (16 kB blocks), 5% Gzip compression (multi-core, level 5), 5% PassMark string sorting. Rationale for component selection: Primary workloads drivers are single-process static HTTP serving speed and throughput, text processing, TLS termination, and asset compression.
Alternatives
Servers of the Same Family
INSTANCE
vCPUs
MEMORY
GPUs
Similar Servers
INSTANCE
VENDOR
vCPUs
MEMORY
GPUs
h200-1920 FAQs
h200-1920 is a 224 vCPUs, 1920 GiB RAM, 8080 GB NVMe, 8xH200 141 GiB VRAM server offered by OVHcloud with 224 vCPUs, 1920 GiB of memory and 8.08 TB of storage.
The h200-1920 server is equipped with 224 logical CPU cores on unknown number of physical CPU core(s) running at max. 3 Ghz, 1920 GiB of memory, 8.08 TB of nvme ssd storage, and 8 Hopper H200 GPUs. Additional block storage can be attached as needed.
The h200-1920 server is offered by OVHcloud, founded in 1999, headquartered in Hauts-de-France, France. For more information, visit the OVHcloud homepage.