Is Pregen on internal server supposed to be this slow?
I'm wondering if there are any settings I can turn on to speed it up, I have C2ME, lithium, faster random, noisium, modern fix.
Thank you.
17 Replies
Solution
4096 chunks is huge, yes, this is expected
4096 is overkill in almost all scenario's
The LOD database will be hundreds of gigabytes large
would chunks also use a ton of storage?
A 4096 radius would
i’m thinking of generating to that far on jj thunder
big ssds exist for a reason i suppose
DH doesn't save normal chunks, if that's what you mean
no i just mean if they’re all saved
every chunk
When generation mode set to Internal Server, then yes.
i have like a couple million chunks rendered (using jjthunder to the max datapack) and i’m at 30gb of storage including world and LODs
radius of like 400
so that checks out
30 GB with 400 chunks? I probably should check mine as I'm at around 870.
i’m using lz4 compression tho that’s prob why
if i use lzma2 do clients receive LODs faster bc of the smaller file size?
i doubt anyone has tested that
i doubt no one has tested that
Okay well thank you guys, I was doing it for epic terrain. Will it be faster if I switch to the LOD gen instead of IS
/generators
- FEATURES: Complete generation of all LODs with mostly correct structures and trees. Does not save vanilla chunks, and is much faster than INTERNAL_SERVER unless C2ME is installed.
- INTERNAL_SERVER: Generates and saves both DH LODs and vanilla chunks, has 100% correct LODs, because it also saves vanilla chunks it takes the most amount of drive space. Generation speed will suck unless C2ME is installed.
- PRE-EXISTING: generates LODs for all existing vanilla chunks.
alright thank you!