You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: community/RAM.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,13 @@ nav_order: 16
8
8
# BlueMap and RAM
9
9
{: .no_toc }
10
10
11
-
BlueMap generally does not *need* a lot of memory.
12
-
In fact, it has been proven to work with just 512MB!
11
+
BlueMap generally does not *need* a lot of memory.
13
12
14
-
The more render-threads you have assigned (in `core.conf`), the more RAM BlueMap will need.
13
+
In fact, BlueMap has been proven to work with just 512MB of assigned memory!
15
14
16
-
However, this does not mean that BlueMap won't use more RAM if it is available.
15
+
The more render-threads you have assigned (in `core.conf`), the more RAM BlueMap will need, so you can lower the amount of used memory by lowering the amount of threads.
16
+
17
+
However, this does not mean that BlueMap won't use more RAM *if it is available*.
17
18
18
19
So do not be alarmed if you notice that BlueMap seems to be using a lot of RAM.
19
20
This is actually perfectly normal and should not be an actual problem.
0 commit comments