Last question in terminal (promise; at least for a while),
How do I lower the amount of days of work the client downloads, in terminal?
I'm only running a single/dual core, of 2Ghz, and it seems like it pre-loads enough tasks for at least 3 days.
I'd like to reduce that to 0.8 days.

How do I go about?

Last question in terminal (promise; at least for a while),
How do I lower the amount of days of work the client downloads, in terminal?
I'm only running a single/dual core, of 2Ghz, and it seems like it pre-loads enough tasks for at least 3 days.
I'd like to reduce that to 0.8 days.

How do I go about?

And not just do that in a browser at the project website? Computing Preferences is the normal place. Just change the number of days of primary cache you want.
https://setiathome.berkeley.edu/prefs.php?subset=global

Or navigate to the boinc folder and use your favorite editor and directly change the cache settings in the global_prefs.xml or the global_prefs_override.xml files.

Last question in terminal (promise; at least for a while),
How do I lower the amount of days of work the client downloads, in terminal?
I'm only running a single/dual core, of 2Ghz, and it seems like it pre-loads enough tasks for at least 3 days.
I'd like to reduce that to 0.8 days.

How do I go about?

And not just do that in a browser at the project website? Computing Preferences is the normal place. Just change the number of days of primary cache you want.
https://setiathome.berkeley.edu/prefs.php?subset=global

Or navigate to the boinc folder and use your favorite editor and directly change the cache settings in the global_prefs.xml or the global_prefs_override.xml files.

Thank you very much!
It seems that the stock settings are set to 1 + 1 day.
Because it's the first batch of WUs, I guess the estimate might have been off.