Uses too much memory about bluemap

[SjoerdHekking]

You can limit the maximum amount of memory allocated to BlueMap by setting JVM options. This can be done by editing the startup script or command used to run BlueMap. Add the -Xmx flag to specify the maximum heap size.

[ChicknTurtle]

ty!

[ChicknTurtle]

Where do I add the JVM arguments? I've looked through all config files for bluemap. I don't want to set max memory for the whole server, just the bluemap process.

[SjoerdHekking]

I wonder what model Mac you have (CPU core count etc.). If you wish to configure BlueMap in such a way it uses less performance from your mac, while you are also using it, you can tweak it via tips in this section . As for running the whole time, BlueMap updates whenever a world has been saved, I am not sure how often you save a world.

[ChicknTurtle]

Model Name: Mac mini
Model Identifier: Macmini9,1
Chip: Apple M1
Total Number of Cores: 8 (4 performance and 4 efficiency)
Memory: 16 GB

I have the render threads set to 1, but that is for cpu. I am more worried about the memory usage.

[TBlueF]

@ChicknTurtle Alright, so:
It's not possible to "limit" the RAM BlueMap uses separately to the rest of the server, that's not how Java-Heap works ^^
Also, did you do a Heap-Dump or how do you even know that bluemap is using more RAM than the server if it is running as a plugin on said server? ^^

To clear up a few things:

• Java reserves a specific amount of RAM for its Heap-Space. E.g. if you use -Xmx6G on your server Java will reserve up to 6GiB of RAM for heap-space and will usually not free this again during runtime. You should always only allocate as much RAM to your server as you can spare and expect this to always be used completely.
• BlueMap does run completely fine with very limited amounts of heap
• BlueMap does not hard-reserve huge amounts of ram while rendering and especially not when idle
• BlueMap 5.2 does keep a soft memory cache for chunks it loaded to optimize rendering speed. However this is a SOFT allocation, meaning that if the JVM ever is in need of more Heap, Javas GarbageCollector will clear up that cache automatically and reuse it for things that are more important. -> BlueMap only uses Heap-Space for caching chunks that is NOT needed by anything else.
• Unused heap-space is wasted heap-space.
• If your server lags it is most likely not due to bluemap using too much ram/heap.

If you still think bluemap is using up too much ram/heap and it's not the soft-cache but actually hard memory-allocation that prevents the server from getting its own share of ram, then please attach a HeapDump for me to analyze, or a link to where i can download it. Otherwise please close this issue :)