HB368rs_v5 is a HBv5 family [RDMA capable] [Premium Storage capable] [Intel processor] 368 vCPUs server offered by Microsoft Azure with 368 vCPUs, 448 GiB of memory and 15.9 TB of storage. The pricing starts at 3.659 USD per hour.
A high-density compute instance featuring 368 dedicated vCPUs, massive local storage, and RDMA networking for parallel clustered workloads.
Compute OptimizedStorage & Database
Microsoft Azure HB368rs_v5 is a high-density compute instance from the HBv5 family, built on the x86_64 architecture and managed via the Microsoft Hyper-V hypervisor. It features 368 dedicated vCPUs powered by an Intel processor, paired with 448.0 GB of system memory. This allocation yields a low memory-to-core ratio of 1.22 GB, prioritizing raw parallel processing power over memory capacity. The instance includes 15851 GB of local storage, supports Premium Storage, and features RDMA capabilities for low-latency cluster networking. It does not contain any GPU accelerators. This hardware profile is designed for highly parallelized, compute-intensive workloads such as engineering simulations and high-performance computing clusters where massive local storage and rapid node-to-node communication are required, while the low memory-per-core ratio represents a deliberate tradeoff to optimize compute density and cost efficiency.
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 KiB, 8 conn/vCPU), 20% Static web RPS (64 KiB, 8 conn/vCPU), 20% Static web throughput (256 KiB, 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.
HB368rs_v5 is a HBv5 family [RDMA capable] [Premium Storage capable] [Intel processor] 368 vCPUs server offered by Microsoft Azure with 368 vCPUs, 448 GiB of memory and 15.9 TB of storage. The pricing starts at 3.659 USD per hour.
The HB368rs_v5 server is equipped with 368 logical CPU cores on unknown number of physical CPU core(s), 448 GiB of memory, 15.9 TB of storage, and no GPU. Additional block storage can be attached as needed.
The pricing for HB368rs_v5 servers starts at 3.659 USD per hour, but the actual price depends on the selected region, zone and server allocation method (e.g. on-demand versus spot pricing options): currently, we track the prices in 24 regions and zones every 5 minutes, and the maximum price stands at 25.742 USD.
The HB368rs_v5 server is offered by Microsoft Azure, founded in 2010, headquartered in Washington, United States. For more information, visit the Microsoft Azure homepage.
The HB368rs_v5 server is available in 24 availability zones of the following 4 regions: Central US (US), East US (US), South Central US (US), Sweden Central (SE).
