FAQ
Chunky is designed to automatically run as fast as possible by default given the server that it is running on. So if you want it to run faster, you need to use a faster server, which could mean either upgrading the hardware or software that it is running on. Here are a few things that are known to have the biggest impact on chunk generation performance:
- Use a fast CPU with plenty of threads available. If your CPU is slow, chunk generation will also be slow. Likewise if you don't have enough threads, it will also be slower, as on 1.16.3 the server can utilize about 4 threads per world being generated simultaneously.
- Use an SSD. Random read/write speeds are much better on SSDs, which greatly benefits chunk I/O.
- Give the server enough RAM. At least 2GB, but 4GB+ recommended. Shouldn't matter much past a certain threshold, you just need enough.
- Use server software that supports asynchronous chunk generation, like Paper. This can make a huge impact on servers using a CPU with plenty of available threads, as it will leverage them.
- Use Aikar's flags in your server startup script. The only things you should change unless you know what you are doing is the amount of memory and the name of the jar. These flags help with java memory garbage collection, and since chunk generation aggressively cycles through memory, this can be a huge help.
No, it does not. If a chunk is already generated, it will be skipped. Chunks are never deleted.
These are mostly harmless errors that can occur during chunk generation, which you can ignore. However, some of them may also be fixed by updating your server.
Only known to occur on very outdated builds of Paper 1.15. If you see this, you must update your server.
This error has been known to occur on Purpur servers. If you are using Tuinity or Purpur, be sure to update to the latest version, and if you are still getting the error, then report it to their respective issue trackers.
There are two main reasons why you could be getting this error. One is if you are not allocating enough memory to the server, in which case you just need to increase the amount. The other is if java memory garbage collection is not able to keep up with the rate that chunks are generating. You can usually tell if this is happening by looking at your server's timings report. If this is the case, you should try to use Aikar's flags (mentioned above) if you aren't already.
Some hosts will automatically kill servers that are utilizing too much CPU. This is a problem with the host, as high CPU usage during chunk generation is normal. The only solution to this problem is politely asking your host to remove the limitation, or switch to a better host.
This warning will show up if the generation task is not able to shut down and save quickly enough when the server is abruptly stopped. It is more likely to occur on low end systems, and the only solution is to pause your tasks with chunky pause and wait for them to stop fully before shutting down your server.
Chunky is partnered with Bloom Host who provide excellent high performance server hosting options. Click the banner below and use code CHUNKY for 25% off your server!
