summaryrefslogtreecommitdiff
path: root/docs/Memory-Usage.md
diff options
context:
space:
mode:
authorYehonal <yehonal.azeroth@gmail.com>2020-05-14 16:55:38 +0200
committerGitHub <noreply@github.com>2020-05-14 16:55:38 +0200
commitf09028eed1c07f3241dbf1dc74ea8f33dd7531c7 (patch)
tree8c5a4c07b8dc9ce70817dee61c1db8925b283c57 /docs/Memory-Usage.md
parentc2a2465d22ee5055120de2e133f96bf4629fb1db (diff)
downloadwiki-f09028eed1c07f3241dbf1dc74ea8f33dd7531c7.tar.gz
wiki-f09028eed1c07f3241dbf1dc74ea8f33dd7531c7.tar.bz2
wiki-f09028eed1c07f3241dbf1dc74ea8f33dd7531c7.zip
Update Memory-Usage.md
Diffstat (limited to 'docs/Memory-Usage.md')
-rw-r--r--docs/Memory-Usage.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/Memory-Usage.md b/docs/Memory-Usage.md
index ae5479c..a258485 100644
--- a/docs/Memory-Usage.md
+++ b/docs/Memory-Usage.md
@@ -12,3 +12,11 @@ AzerothCore is based on SunwellCore (a fork from TC). SunwellCore was a public s
| >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.
+
+That's mean that eventhough you've few players online, if they explore the entire maps they won't be unloaded from the RAM.
+It's an architectural choice granting "high performances" on heavy usage.
+
+We can also try to explain you it with a draw
+
+
+![ram](https://i.imgur.com/X3GBBbD.jpg)