chore: file naming standard (#517)

* A

* file naming standard
Fixes #491

* Revert "A"

This reverts commit 1c225fed753554098069597a2bbcbe08213b76a1.

* rename

* Revert "rename"

This reverts commit 65fd916faf8530ce258cc2b475c93971468680fe.

* Revert "file naming standard"

This reverts commit 6ca5a703a9e9d59f9c773029e4c04bfd012b6abb.

* bye

* Hi

* Create the-staging-branch.md

* 1

* Delete how-to-create-a-PR.md

* Create how-to-create-a-pr.md

* werafgt

* Update the-modular-structure.md

* wef

1 files changed, 25 insertions, 0 deletions

diff --git a/docs/memory-usage.md b/docs/memory-usage.md
new file mode 100644
index 0000000..8a2b9da
--- /dev/null
+++ b/docs/memory-usage.md
@@ -0,0 +1,25 @@
+---
+redirect_from: "/Memory-Usage"
+---
+
+# Memory Usage
+
+### AzerothCore Memory Usage
+
+AzerothCore is based on SunwellCore (a fork from TC). SunwellCore was a public server with 4000 players online and they made sure their core could handle that amount of players easily. Reading data from the ram is much faster than reading from the hard disk (there are entire systems based on this principle). That's one of the reason there is a bigger ram usage.
+
+#### RAM Requirements
+
+| Number of players | Minimum RAM requirement |
+|-------------------|-------------------------|
+| 1-5               |   4 GB                  |
+| 10                |   6 GB                  |
+| 100               |  16 GB                  |
+| >100              | >16 GB                  |
+
+We recommend at least 16 GB as the server will gradually cache the world maps as the players explore them which finally takes up to at least 11 GB of RAM usage.
+
+It means that even though you have few players online, when they explore any map, it will never be unloaded from the RAM until reboot. So after enough time, all the maps will be loaded, taking up more RAM.
+It's an architectural choice granting "high performance" on heavy usage.
+
+![ram](https://i.imgur.com/X3GBBbD.jpg)