(1.20.1) After updating Distant Horizions recently, memory allocation seems to not work correctly
I was running a modpack (gravitas2) from some months ago, 0.6.0 containing version 2.1.2-a of Distant Horizions, I use a 7800X3D and set the generation option to 'agressive' whilst allocating 20GB for the client. This worked splendidly. Full CPU utilization and RAM utilization.
Upon updating to 0.7.1 of the pack, containing 2.3.2-b of Distant Horizions, allocation seems to stop at 10GB's, well short of the amount allocated, changing XMS to 20000 insteada of the default 512 doesn't seem to help, garbage collection happens at 40 - 50% and performance is attrocious.
Any idea what's going on? I can load up the old version of the pack again and all works well as it did before, do you think this is a DH issue? The discord for Gravitas2 pointed me towards yall.
Sorry for no logs or anything, but I'm not sure what I should be looking for - you can point me in the right direction!
modpack in question: https://www.curseforge.com/minecraft/modpacks/all-the-mods-gravitas2
This relates to Singleplayer.
Thanks.
CurseForge
All The Mods - Gravitas²
Gravitas is back, and GregTech came too
146.1K Downloads | Modpacks
9 Replies
First off, memory management has been greatly improved compared to everything prior. This means Distant Horizons can now operate with a much lower memory footprint.
Second off, forcing the memory allocation too high (since the bar has been moved down) can cause performance degradation. Consider reverting your memory settings back to your previous config and inspect for performance difference in that state.
Hey thanks for the quick reply - I've played that modpack for half a year now with the aformentioned setting for distant generation set to 'agressive' and around 19GB allocated. It maxed out the CPU and memory was fully saturated prior to this problem. It worked really well. Now the CPU never gets properly utilized with terrible FPS as well, it seems no matter the setting, 'balanced', 'agressive' and 'I paid for the whole CPU' never comes close to maxing out the 16 threads as it did before on the CPU I have. I presumed this is surely a memory allocation mishap / misbehavior.
I never saw memory go above 40-50% utilization. I will try with about half the memory allocated and I'll post my findings.
Thanks for the reply again!
Memory clearing is handled by GC not DH
What are your GC/JVM tuning flags?
None, I'm using prismlauncher, the only args I use are for the RAM allocation.
tried with 12 / 14GB allocated as opposed to 19GB as I usually do, no change. RAM is still not being used up (goes up to 70%) and then cleanup happens, it seems distant horizions is not even generating anymore at some point - CPU is idle with 'agressive' option on. This is a fresh install of the mentioned client, no memory args, running with 14GB allocated via prism launcher.
https://i.imgur.com/xwY2cal.png
https://i.imgur.com/rc0MgtG.jpeg
https://i.imgur.com/rc0MgtG.jpeg
Memory hovering around 50 to 75% should be ideal usage, but Distant Horizons stalling after a while isn't. It also seems like there's overdraw issues as seen in the last image.
I don't do Forge, so I can't really help much. Will need someone else to come by and help.
It's been a long time since I've posted this thread. I'd like to make anyone aware that is having the same issue - it was a setting in DH that was enabled by default (I was using the modpack Gravitas2), the setting in one of the top settings in DH and was set to 'pre-existing chunks only'. Change that and it will start generating. Apologies if I wasted anyone's time, as it was my own fault. (I assume modpack creators did this, as previous versions didn't need me to change this setting). Thanks again for maintaining and developing DH!
The default mode in DH is Features, so this is probably the fault of the modpack creator