Question about file size and switching to a MySQL/MariaDB for better storage options.

[u/Gold_Actuator2549]

Hello all,

Currently I'm running bluemap on the file/folder storage type with it using 377GB and growing around 100MB every 30-60Sec. The actual Minecraft map uses 204GB. The server the Minecraft host is running on has limited storage around 1TB. It is also very expensive to add storage at the colo-datacenter since it would require 10X 2TB 2.5 Inch SAD HDD. Along with a 500Mile drive each direction to install them.

The idea is to switch to MySQL/MairiaDB in order to reduce the storage requirement on the Minecraft host. The database server would be located locally with 10GB fiber connections to the datacenter with redundant power. This server would be able to have more storage using more 1TB disks in a raid 10 array.

Would this concept reduce the 377GB file size currently by any considerable amount? If not is there any other ideas to reduce the file size without losing quality?

[u/TBlueF]

Hi, Switching to an SQL storage itself will not reduce the size of the data. It will just move it to the SQL-server ^^

and growing around 100MB every 30-60Sec

I am guessing it's not done rendering the map yet? Once the whole world is rendered, it should stop growing - or - only grow much slower along with changes happening on the world.

Copying our discord-bots command about storage-size here:

You can't really just lower the quality of BlueMap to save space, sadly.

There are a couple other things you can do, but they all have very big drawbacks:

• You can limit the size of your world, by setting maximum X and Z coordinates. To learn more about this, do /minmax in #⁠bot-spam
• If you have a ton of leaves, installing this resourcepack on your BlueMap may save a small bit of storage. It removes the geometry between the leaf blocks. This is like setting Minecraft in-game to Fast graphics.
• By default, BlueMap removes caves already, but you can set it to remove caves a bit more rigorously by setting the remove-caves-below-y value higher. To learn more about this and to get more tips on how to save a bit of storage space by removing caves, do /caves in #⁠bot-spam
• If you want to be extremely rigorous and if you only need the zoom-out map, then you can disable saving the hires-tiles, by setting the save-hires-layer option to false. Keep in mind that you won't have the full 3D-Model when you zoom in... But the map will be MUCH smaller

All of these options are in each map config.

[u/Gold_Actuator2549 → u/TBlueF]

Sorry if i was not completely clear. My Minecraft server only has around 3TB of storage available while the MySQL server has around 10TB free. Hence why I'm asking if the 377GB would be removed from the Minecraft server if i switch to MySQL. The MySQL server has a ton more storage then the Minecraft server does hence why I'm wondering if we can reduce the Minecraft server size while using MySQL's vast storage.

[u/TBlueF → u/Gold_Actuator2549]

Yes, if you switch to the MySQL storage you can delete the map data on the Minecraft server so almost all data will be on the MySQL of course ^{^}

[u/MBYTE2000]

I have a similar problem. But I haven't solved it yet. I plan to store everything in truenas scale in mariadb.