summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorBarbz <BarbzYHOOL@users.noreply.github.com>2020-10-03 21:57:35 +0200
committerGitHub <noreply@github.com>2020-10-03 21:57:35 +0200
commite5b94610af6a765a2d038e1aecc9465bf12c0a9d (patch)
treee9eec3101fc831d9ffe984e9676715c977b134ad /docs
parentc77a71d0df28da5cf6d462027738fd2f49dc5283 (diff)
downloadwiki-e5b94610af6a765a2d038e1aecc9465bf12c0a9d.tar.gz
wiki-e5b94610af6a765a2d038e1aecc9465bf12c0a9d.tar.bz2
wiki-e5b94610af6a765a2d038e1aecc9465bf12c0a9d.zip
fix: Broken english in Memory-Usage.md
- TODO: rename this horrible file name
Diffstat (limited to 'docs')
-rw-r--r--docs/Memory-Usage.md7
1 files changed, 2 insertions, 5 deletions
diff --git a/docs/Memory-Usage.md b/docs/Memory-Usage.md
index 08f2572..760bdaf 100644
--- a/docs/Memory-Usage.md
+++ b/docs/Memory-Usage.md
@@ -13,10 +13,7 @@ AzerothCore is based on SunwellCore (a fork from TC). SunwellCore was a public s
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 event hough you've few online players, if they explore the entire maps, those maps 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
-
+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)