Open jtJava opened 5 months ago
Send the full spark report.
Send the full spark report.
This is with 200 worlds being cloned, first few clones take 30-50ish ms, then drop down to around 10 ms each https://spark.lucko.me/V2bJZvFVSB
I have noticed this as well. The Spigot Config part is easy to fix, but the paper config seems quite difficult (at least for me)
This should be able to be fixed by just grabbing a spigot and paper config from an already existing world if possible. If it's a clone, maybe in the template world the config can be saved for future clones. I did a lazy fix in my own fork and was able to drop world load times to 1-2 ms each
This should be able to be fixed by just grabbing a spigot and paper config from an already existing world if possible. If it's a clone, maybe in the template world the config can be saved for future clones. I did a lazy fix in my own fork and was able to drop world load times to 1-2 ms each
Caching the config is indeed a possible solution I didn't think of. I don't like using one from another world tho
Is your feature request related to a problem? Please describe. When loading worlds, a Spigot/Paper world config is generated, causing worlds to take 30ms+ to load
Describe the solution you'd like Some sort of config value or startup parameter that avoids the config generation