Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 1.resource-preparations.md #1303

Merged
merged 1 commit into from
Apr 27, 2022
Merged

Update 1.resource-preparations.md #1303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 23 additions & 26 deletions docs-2.0/4.deployment-and-installation/1.resource-preparations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
Expand Down