You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did a new install of 3.2.0.1 today and whatever modpack I tried to install would cause the wabbajack client to become unresponsive after a few seconds. My specs are:
5950x 16 (32) cores
64GB 3600 DDR4
Gen4 nvme (~6500MB/s write speed)
500mb fibre download
Task manager showed none of these were being taxed although the client was using 16GB Ram.
The config file had all the "MaxTasks" values set to 32 and I confirmed on the discord that this was tied to the number of logical cores the CPU has.
Dropping this down to 6 for all values made a huge difference, the client stayed responsive, only used 2GB ram and it kept running at ~62MB/s download.
I think this value needs capping quite low rather than being tied to the number of logical cores, if I can hit max speed with 6 downloads there is no way I need it to try and do 32 simultaneous downloads.
The text was updated successfully, but these errors were encountered:
I did a new install of 3.2.0.1 today and whatever modpack I tried to install would cause the wabbajack client to become unresponsive after a few seconds. My specs are:
5950x 16 (32) cores
64GB 3600 DDR4
Gen4 nvme (~6500MB/s write speed)
500mb fibre download
Task manager showed none of these were being taxed although the client was using 16GB Ram.
The config file had all the "MaxTasks" values set to 32 and I confirmed on the discord that this was tied to the number of logical cores the CPU has.
Dropping this down to 6 for all values made a huge difference, the client stayed responsive, only used 2GB ram and it kept running at ~62MB/s download.
I think this value needs capping quite low rather than being tied to the number of logical cores, if I can hit max speed with 6 downloads there is no way I need it to try and do 32 simultaneous downloads.
The text was updated successfully, but these errors were encountered: