-
Notifications
You must be signed in to change notification settings - Fork 81
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update 1.resource-preparations.md (#1303)
- Loading branch information
1 parent
e2c3d2c
commit d4fbaf0
Showing
1 changed file
with
23 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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 [email protected] 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 [email protected] 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. | ||
|
|
||
|
|
||
|
|
||
| <!-- | ||
| ## Optimize the configuration for HDD | ||
|
|
||