Not sure if this should be a "Realms" issue or "PocketEdition/Win10" issue.
Longer version of issue in the Minecraft Forums. Here is the shorter compact version:
TLDR - Realms larger than certain point become too laggy/unresponsive to play on PE Realms.
Here is the slightly longer version:
This is now the second time our Realm world has gotten larger than 1GB (previously was 1.98GB at the end of season 1), and has gotten to the point of instability not allowing play often for more than 10-20 minute without it crashing. We will be reseting again after only 5-6months, to start season 3 due to this once 1.1 comes out.
There are time where the realm will be stable for hours, and then just stop working. From our testing it doesn't seem to be specific chunks that are effected, certain players, or items. There doesn't even seem to be certain times of the day that are better than others. Players will be unable to log in, get disconnected (as a group), have chunks that won't load, blocks that won't update... The issue just seems to get worse and worse as time goes on. Usually when small updates happen (1.0.3, .4, .5, etc) it gets better for a short time, but then returns after a few hours to a day.
I've downloaded this world and although slow on my local computer I've never had crashes, or ejections in any of the areas. Different tools I've run on the downloaded don't seem to come up with anything either that should be causing issue. Only thing I can think of is Realms can't handle world sizes over a certain limit, although have never found any official documentation supporting this. Anecdotally, I have been able to confirm that once the realm gets to roughly 1GB it can no longer be uploaded, as we used to try to check if there were issues or cheating going on by uploading the backup to a second realm.
I can upload the backup here if that would be helpful, or provide a link to our gDrive that has the file. Also I can give the realm's Creator info or transaction number if it's better to se the world live in action. Any information would be appreciated as seems we have to reboot the word every 5-6 months.
Comments
migrated
migrated
Thanks for the additional information.
There aren't any server logs I can find (or at least that I have access to) so it's difficult to determine exact causes. Would love more information or resources to find out more information about the accuses of these disconnects and lag spikes.
I've checked the other bug reports as well, and they seem to be related to LAN games or single player games, so perhaps this stands out as it's running on Mojang's own Realm servers. And as such they will have access to things on the back end that might be able to determine a good course of action.
migrated
Also if we are suggesting possible fixes (if it is indeed a size issue), perhaps some way to reset "unaltered" chunks. That is chunks that have been loaded, but not modified past the initial seed generation. That way if someone goes exploring you could essentially "erase" those chunks form the database and greatly reduce the overall size of the world.
migrated
This may be specifically a PocketEdition/Win10 Realms issue as I am not having the problem with the java version. My Realms world is well over 3 GB, and while I am experiencing lag (enough to induce headaches due to a couple of massive redstone sorters and contraptions) that lag diminishes as I move away from the spawn chunks (but never vanishes). I also never have a problem with the Realms crashing.
I have reached the point where I can download the world, but I can no longer upload it as it has become too large (mainly due to our exploration of the closest 7 Woodland Mansions, with one return through the nether, and an exploration of a dozen or so end cities).
[Mojang] Mega_Spud (Jay)
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
For any account related queries, please contact Mojang Customer Support directly.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
migrated
This has happened to me as well. The server I owned had a map with a file size of over 60 gb. The server was using bds aswell which didn't help it. Finally in 1.13 it refused to even load the world on the server and on 1.12 it would for reason load but not save any progress. It's truly sad that bedrock can't even handle 1/10 of a terabyte size world.
migrated
this issue is still present, our realm is just under 3gb and completely unplayable im including the join code as this is an ongoing issue and i have nearly 300 very dissapointed soon to be former players.Â
Elysium V2 Code: tacpIthBPPM if it says need permission, you put the code in wrong 🙂(thats a capital i after the p)
Since the vast majority of realms die out from inactivity owing to grief 99% of realms will never grow to the size that yours has. For this reason I don't believe this will ever be a priority for Mojang to tackle. With that said you are correct, the crashes are clearly owing to high file size. My own suspicion is that it has to do with autosave. You probably noticed that around 1.3 Gb you begin to get lag spikes every 20-30 seconds...you can almost set your clock by them. I believe the server is trying to do an autosave at this time. At around 1.5 Gb the autosaves begin to take long enough that I believe they are overlapping? Crashes become very common around this stage. At 1.6 Gb the game will crash within 1 min of restarting from the previous crash making the game completely unplayable. The only course of action at this point is a reset.
My Suggestions:
#1 Offer a higher tier of realms with better hardware to handle a growing realm. I would be willing to pay $50-75 a month for such a service especially if we could add another 5 or so players.
#2 Alternatively Mojang could release DS software as they do for java so we can run our own servers.
#3 A temporary fix but they could add a Reset The End and Reset The Nether button to shrink file size for awhile.
You are not alone, there is another bug report here describing this issue MCPE-12347