RAM usage

Hans Kurel repo owner

The way this plugin works is by loading all creative block locations into memory (RAM) on startup, so it wouldn’t have to do that later. If there are a lot of blocks, then yes, it can take up a lot of space. They’re removed from the memory when their chunk gets loaded, so it should free up memory as more and more chunks gets loaded.

This, however, is only a problem for relatively large servers, which should have gigabytes of RAM to spare anyway. The other option would be to connect to an SQL server every time a block is broken, which is just terribly slow (but that’s exactly how some other plugins handle it, unfortunately).

I can see if there’s a way to use less RAM to store them, but I can’t promise anything. BTW, how many blocks do you have in the database?

2020-02-20T09:33:38+00:00

Comments (4)

Hans Kurel repo owner
The way this plugin works is by loading all creative block locations into memory (RAM) on startup, so it wouldn’t have to do that later. If there are a lot of blocks, then yes, it can take up a lot of space. They’re removed from the memory when their chunk gets loaded, so it should free up memory as more and more chunks gets loaded.

This, however, is only a problem for relatively large servers, which should have gigabytes of RAM to spare anyway. The other option would be to connect to an SQL server every time a block is broken, which is just terribly slow (but that’s exactly how some other plugins handle it, unfortunately).

I can see if there’s a way to use less RAM to store them, but I can’t promise anything. BTW, how many blocks do you have in the database?
- 2020-02-20T09:33:38+00:00
Former user Account Deleted reporter
6954469 blocks
- 2020-03-26T15:59:59+00:00
Hans Kurel repo owner
I’ll release an update soon where I’ve made some improvements. Make sure to take your memory measurements before and after the update to compare.
- 2020-03-30T09:16:34+00:00
Hans Kurel repo owner
- changed status to resolved
- 2020-03-30T15:58:16+00:00
Log in to comment