From d4fbaf006b9151b4f8a0c8c7ba7b6562ab3d2306 Mon Sep 17 00:00:00 2001 From: "abby.huang" <78209557+abby-cyber@users.noreply.github.com> Date: Wed, 27 Apr 2022 10:57:28 +0800 Subject: [PATCH] Update 1.resource-preparations.md (#1303) --- .../1.resource-preparations.md | 49 +++++++++---------- 1 file changed, 23 insertions(+), 26 deletions(-) diff --git a/docs-2.0/4.deployment-and-installation/1.resource-preparations.md b/docs-2.0/4.deployment-and-installation/1.resource-preparations.md index eda99392591..4c006f9cef6 100644 --- a/docs-2.0/4.deployment-and-installation/1.resource-preparations.md +++ b/docs-2.0/4.deployment-and-installation/1.resource-preparations.md @@ -2,7 +2,29 @@ This topic describes the requirements and suggestions for compiling and installing Nebula Graph, as well as how to estimate the resource you need to reserve for running a Nebula Graph cluster. -## Requirements for compiling the Nebula Graph source code +## About storage devices + +Nebula Graph is designed and implemented for NVMe SSD. All default parameters are optimized for the SSD devices and require extremely high IOPS and low latency. + +- Due to the poor IOPS capability and long random seek latency, HDD is not recommended. Users may encounter many problems when using HDD. + +- Do not use remote storage devices, such as NAS or SAN. Do not connect an external virtual hard disk based on HDFS or Ceph. + +- Do not use RAID. + +- Use local SSD devices. + +## About CPU architecture + +!!! enterpriseonly + + Nebula Graph {{ nebula.release }} Enterprise Edition can be run or compiled directly on ARM architectures (including Apple Mac M1 or Huawei Kunpeng). Contact inquiry@vesoft.com for business supports. + +!!! note + + Starting with 3.0.2, you can run containerized Nebula Graph databases on Docker Desktop for ARM macOS or on ARM Linux servers. + +## Requirements for compiling the source code ### Hardware requirements for compiling Nebula Graph @@ -225,31 +247,6 @@ Users can estimate the memory, disk space, and partition number needed for a Neb Users can decrease the memory size occupied by the bloom filter by adding `--enable_partitioned_index_filter=true` in `etc/nebula-storaged.conf`. But it may decrease the read performance in some random-seek cases. -## FAQ - -### About storage devices - -Nebula Graph is designed and implemented for NVMe SSD. All default parameters are optimized for the SSD devices and require extremely high IOPS and low latency. - -- Due to the poor IOPS capability and long random seek latency, HDD is not recommended. Users may encounter many problems when using HDD. - -- Do not use remote storage devices, such as NAS or SAN. Do not connect an external virtual hard disk based on HDFS or Ceph. - -- Do not use RAID. - -- Use local SSD devices. - -### About CPU architecture - -!!! enterpriseonly - - Nebula Graph {{ nebula.release }} Enterprise Edition can be run or compiled directly on ARM architectures (including Apple Mac M1 or Huawei Kunpeng). Contact inquiry@vesoft.com for business supports. - -!!! note - - Starting with 3.0.2, you can run containerized Nebula Graph databases on Docker Desktop for ARM macOS or on ARM Linux servers. - -