Slow LOD load from server to client
Hi, I was able to get DH loaded on client side and server side. I used the pregen command to generate 150 chunk radius. It looked grate, but when I relog to get back into the server, it takes 5-10 minutes for my LOD distance to load all that again.
I thought once they were loaded, it would be pretty instant when logging back into a world. Is this assumption wrong?
I’m on a pretty old CPU for client side… sitting around 90% even though (I think) that the server already did all the generation. Is it just a bottleneck accessing the data?
8 Replies
Does the loading speed up if you increase the cpu load in DH's settings?
Client or server side? Server side is at max cpu load.
Client side, as I said, my CPU is at like 90% already
If the client already has all of the LODs stored in the local DB, client side DH CPU load is what will control the loading speed
Ok. I guess I was expecting once it was loaded once, the CPU wouldn’t need to do much. But even after waiting a while for LODs to load, then I relog, it takes about the same time to load those again
You can recude the CPU load in DH configm though it will make the LOD loading slower
I guess my question is this: is recalling the already loaded information supposed to be so CPU intensive? I thought it was just recalling it from memory, not loading it
What cpu are you using?
The LODs need to be read and decompressed, that process can use same amount of cores and threads as chunk generation
It should be a lot quicker then that initial generation though