Recent Discussions
Reading/writing region files from database
Open in DiscordUnanswered
Asiatic Lion posted this in #questions
14 messages
0 views
Asiatic LionOP
i have become very curious about whether or not this is feasible and if its worth it. We are working to switch our infrastructure to K8s completely, however the issue that arises with this is that we cant feasibly store things like 500gb+ worlds inside of a docker image. I did a little bit of research and it has been done before, more as a PoC: https://gist.github.com/HeathLoganCampbell/bc0e7ec8d7fc8d27f4b427268627cb93 but it would be interesting to see something like this using the linear v2 format.
My question is this: is it really worth it? We're aiming to have our Survival instances (overworld, end and nether are split) have their world data stored elsewhere so that we have this flexibility. But I'm not exactly sure whether this is a good idea, since we're aiming to have 500+ players, hopefully 1000, in production.
My question is this: is it really worth it? We're aiming to have our Survival instances (overworld, end and nether are split) have their world data stored elsewhere so that we have this flexibility. But I'm not exactly sure whether this is a good idea, since we're aiming to have 500+ players, hopefully 1000, in production.
@Asiatic Lion i have become very curious about whether or not this is feasible and if its worth it. We are working to switch our infrastructure to K8s completely, however the issue that arises with this is that we cant feasibly store things like 500gb+ worlds inside of a docker image. I did a little bit of research and it has been done before, more as a PoC: https://gist.github.com/HeathLoganCampbell/bc0e7ec8d7fc8d27f4b427268627cb93 but it would be interesting to see something like this using the linear v2 format.
My question is this: is it really worth it? We're aiming to have our Survival instances (overworld, end and nether are split) have their world data stored elsewhere so that we have this flexibility. But I'm not exactly sure whether this is a good idea, since we're aiming to have 500+ players, hopefully 1000, in production.
My question is this: is it really worth it? We're aiming to have our Survival instances (overworld, end and nether are split) have their world data stored elsewhere so that we have this flexibility. But I'm not exactly sure whether this is a good idea, since we're aiming to have 500+ players, hopefully 1000, in production.
Asiatic LionOP
There are ways to get around this, I know, but in general deploying a container that's very large in size won't exactly be quick
Connecticut Warbler
https://github.com/openebs/mayastor why not smth like this
instead of having it in the docker image
Asiatic LionOP
having it on a database means that we have the flexibility to, if we ever reach the limits, just have the array rebuild itself by replacing the drives
which now that i think of it isnt exactly an advantage cause you can just do this on the main machine lo
but i guess if you have more than 1 gamemode using this system, itll be easier since you only have to do it for one machine
i dont know
really theres no advantage to this apart from being able to make large gamemodes stateless, so they can run on any machine if something idk explodes or whatever
and it looks impressive on a dev blog
what else
Doesn't SlimeWorldManager store in a DB? It's intended for finite size worlds like for minigames, but that might be some inspo.
Asiatic LionOP
from what I remember linear is somewhat similar to slime in concept
Loading...
Loading...