From a13b6c867fbe80b50674c6a959dd7a6873990a25 Mon Sep 17 00:00:00 2001 From: schmidt-scaled <82834682+schmidt-scaled@users.noreply.github.com> Date: Fri, 19 Jun 2026 16:59:29 +0300 Subject: [PATCH 1/2] Update hardware-requirements.md --- .../deployment-preparation/hardware-requirements.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/deployments/deployment-preparation/hardware-requirements.md b/docs/deployments/deployment-preparation/hardware-requirements.md index 93ddad7e..6921a437 100644 --- a/docs/deployments/deployment-preparation/hardware-requirements.md +++ b/docs/deployments/deployment-preparation/hardware-requirements.md @@ -219,7 +219,8 @@ A full list of the supported architectures can be found in the ### NVMe Capacity and Performance Guidance -NVMe devices must support 4KB native block size and are recommended to be sized between 1.9 TiB and 7.68 TiB. +NVMe devices must support 4KB native block size or devices with 512b native block size, which must support +4KB write atomicity, and are recommended to be sized between 1.9 TiB and 7.68 TiB. Large NVMe devices are supported, but performance per TiB is lower and rebalancing can take longer. Clusters are lightweight, and it is recommended to use different clusters for different types of @@ -247,8 +248,7 @@ once simplyblock's storage nodes are running. ### NVMe Formatting Prerequisites -It is required to [Low-Level Format Devices](../../reference/nvme-low-level-format.md) with 4KB block size before -deploying simplyblock. +Simplyblock does optionally low-level format NVMe devices with 4KB block size before deploying simplyblock. !!! warning Low-level formatting destroys all data on the device. Ensure to back up any important data before formatting, if @@ -269,8 +269,8 @@ bond over two ports of the NIC(s) or using SRV-IO must be created. ### Fabric and Protocol Notes -Simplyblock implements NVMe over Fabrics (NVMe-oF), specifically NVMe over TCP, and works over any Ethernet -interconnect. +Simplyblock implements NVMe over Fabrics (NVMe-oF), either NVMe over TCP or NVMe over ROcEv2, and works over any Ethernet +interconnect. Fabric transport layers can be mixed (e.g. cluster internal-traffic on NVMe over ROcEv2 and client to cluster over TCP). !!! recommendation Simplyblock highly recommends NICs with RDMA/ROCEv2 support such as NVIDIA Mellanox network adapters (ConnectX-6 or higher). @@ -305,5 +305,5 @@ The minimum required PCIe standard for NVMe devices is PCIe 3.0. However, PCIe 4 ### Hyperthreading -If 32 or more physical cores are available per storage node, it is highly recommended to turn off hyperthreading in the +If 32 or more physical cores are available per storage node, it is recommended to turn off hyperthreading in the BIOS or UEFI setup services. From 1d88d1c2990b4a9c2522338b5fd1aed0af22a91b Mon Sep 17 00:00:00 2001 From: noctarius aka Christoph Engelbert Date: Mon, 22 Jun 2026 08:07:29 +0200 Subject: [PATCH 2/2] Update NVMe requirements and formatting instructions Clarified NVMe device requirements and formatting prerequisites. Updated recommendations for NICs and hyperthreading settings. --- .../hardware-requirements.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/docs/deployments/deployment-preparation/hardware-requirements.md b/docs/deployments/deployment-preparation/hardware-requirements.md index 6921a437..6b52e2c4 100644 --- a/docs/deployments/deployment-preparation/hardware-requirements.md +++ b/docs/deployments/deployment-preparation/hardware-requirements.md @@ -219,9 +219,11 @@ A full list of the supported architectures can be found in the ### NVMe Capacity and Performance Guidance -NVMe devices must support 4KB native block size or devices with 512b native block size, which must support -4KB write atomicity, and are recommended to be sized between 1.9 TiB and 7.68 TiB. -Large NVMe devices are supported, but performance per TiB is lower and rebalancing can take longer. +NVMe devices must support 4KB native block size or devices that support 512b native block size with +4KB write atomicity. + +The NVMe devices are recommended to be sized between 1.9 TiB and 7.68 TiB. Large NVMe devices are supported, +but performance per TiB is lower and rebalancing can take longer. Clusters are lightweight, and it is recommended to use different clusters for different types of hardware (NVMe, networking, compute) or with a different performance profile per TiB of raw storage. @@ -248,7 +250,8 @@ once simplyblock's storage nodes are running. ### NVMe Formatting Prerequisites -Simplyblock does optionally low-level format NVMe devices with 4KB block size before deploying simplyblock. +Simplyblock can low-level format NVMe devices with 4KB block size before deploying simplyblock. This is an optional +step. Low-level formating can also be executed manually. !!! warning Low-level formatting destroys all data on the device. Ensure to back up any important data before formatting, if @@ -269,8 +272,8 @@ bond over two ports of the NIC(s) or using SRV-IO must be created. ### Fabric and Protocol Notes -Simplyblock implements NVMe over Fabrics (NVMe-oF), either NVMe over TCP or NVMe over ROcEv2, and works over any Ethernet -interconnect. Fabric transport layers can be mixed (e.g. cluster internal-traffic on NVMe over ROcEv2 and client to cluster over TCP). +Simplyblock implements NVMe over Fabrics (NVMe-oF), either NVMe over TCP or NVMe over RoCEv2, and works over any Ethernet +interconnect. The fabric transport layers can be mixed, like cluster internal-traffic on NVMe over RoCEv2 and client to cluster over NVMe over TCP. !!! recommendation Simplyblock highly recommends NICs with RDMA/ROCEv2 support such as NVIDIA Mellanox network adapters (ConnectX-6 or higher). @@ -306,4 +309,4 @@ The minimum required PCIe standard for NVMe devices is PCIe 3.0. However, PCIe 4 ### Hyperthreading If 32 or more physical cores are available per storage node, it is recommended to turn off hyperthreading in the -BIOS or UEFI setup services. +BIOS setup or UEFI services.