My brother-in-law has set up a small Minecraft server where he, his brother (my other brother-in-law) and I paddle around a bit. Now he said to me that you can overload the server if you discover the world too much, while I'm wondering if that is possible? Because the card is actually already loaded? My pc doesn't crash either when i explore the world in offline mode (single player). So can you discover the world causing a server to crash?
(Sorry for my bad German.
Yes you can if the server has too little RAM. 😉
Yes it is quite possible you can also have a server (please do not do it, because you can get into legal trouble) smeared if you bombard it with requests. Depending on how Minecraft is structured, this could even be the case when exploring the world, depending on whether only individual seeds or actually the entire world is loaded.
You see that more often in big youtuber projects on minecraft servers if 100 people walk in different directions then they can also lag and that can lead to a crash with bad server settings C
The world must also be generated in the background.
If you generate too many chunks at once (that means you walk around a lot and let the world generate it), the server is overloaded. Of course, it depends on the hardware. This doesn't happen with your own PC (at least most of the time), because it doesn't have to process multiple players at the same time, nor does it have to generate and load as many chunks in multiple worlds.
Most of the time, the server does not crash, but there can be performance drops.
With many Minecraft server implementations (spigot, notchian or similar) only one thread is used. You have to imagine it like a worker: one thread = one worker. Each worker can only work on one task at a time. So if this worker (the thread) is already working on a task (generating the chunks), he must first complete it before he can continue with other tasks (for example, perceive the broken blocks by players, or process the written in the chat of players) . The other processes suffer as a result and are initially put into the background.
This problem can be solved by using server software that generates the chunks asynchronously or which is directly multi-threaded (e.g. Paperspigot or Minestom).
That doesn't necessarily have to be due to the RAM
