Skip to content

Add Memgraph on Arm install guide#3312

Open
Sabika-Tasneem wants to merge 2 commits into
ArmDeveloperEcosystem:mainfrom
Sabika-Tasneem:main
Open

Add Memgraph on Arm install guide#3312
Sabika-Tasneem wants to merge 2 commits into
ArmDeveloperEcosystem:mainfrom
Sabika-Tasneem:main

Conversation

@Sabika-Tasneem
Copy link
Copy Markdown

Adds an install guide for running Memgraph on Arm.

The guide covers:

  • Installing Memgraph with Docker
  • Installing Memgraph with native Linux packages
  • Verifying the installation with mgconsole
  • Running basic Cypher queries
  • Optionally using MAGE for graph algorithms

The guide uses the latest Memgraph 3.10.1.


## How do I increase the memory map area limit?

Memgraph allocates many small memory mappings, and on larger graphs the default Linux limit (`vm.max_map_count = 65530`) can be hit. This typically surfaces as a hung transaction, `munmap` errors, or `bad_alloc` crashes. Memgraph recommends roughly one memory map area per 128 KB of system RAM. The full table and background are in the [system configuration docs](https://memgraph.com/docs/database-management/system-configuration#increasing-memory-map-areas).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our guidance on this actually changed recently to 1 per 64 kb

Comment on lines +195 to +205
For an 8–32 GB host, `262144` is the recommended starting value. Set it for the current session:

```bash { target="ubuntu:latest" }
sudo sysctl -w vm.max_map_count=262144
```

To persist the change across reboots, add it to `/etc/sysctl.conf` or a drop-in under `/etc/sysctl.d/`, then reload:

```bash { target="ubuntu:latest" }
echo 'vm.max_map_count=262144' | sudo tee -a /etc/sysctl.conf
sudo sysctl -p
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The number used by default is now 524288

@jasonrandrews
Copy link
Copy Markdown
Contributor

Let me know when this PR ready for technical and editorial review and we will move to the publishing phase.

@Sabika-Tasneem
Copy link
Copy Markdown
Author

Let me know when this PR ready for technical and editorial review and we will move to the publishing phase.

@jasonrandrews The PR is final and ready for technical and editorial review. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants