Message boards : BOINC client : Is there a way to limit work cache?
Message board moderation
Author | Message |
---|---|
Send message Joined: 22 Aug 07 Posts: 3 |
Is there a way to limit the amount of work in the work cache? The problem is that I run BOINC most of the time I'm home (12 hours a day) but it is possible that I'm unable to run BOINC for a week or something like that. (because I'm not home then) When I'm back home my computer has to hurry to get everything done in time. So, is there a way to limit my work cache to 1 or 2 WU's instead of 6 or more? |
Send message Joined: 16 Apr 06 Posts: 386 ![]() |
To shrink the amount of outstanding work by about 60%, try this: * View general preferences / * Edit / * Change 'connect to network' to 0.03 from 0.1, and also * Change 'Cache enough work' to 0.1 from 0.25, * Update preferences, then * Click 'update' on that project within the boinc manager. |
![]() ![]() Send message Joined: 30 Oct 05 Posts: 1239 ![]() |
Just because your connect to is that small doesn't mean you'll hammer the servers. Think about Einstein or Rosetta (with a run time pref of 24 hours). A connect interval like that will give you one WU/core at a time, but it'll take a fair number of hours to complete. Or if you run multiple projects. Personally I keep mine at .001 with no additional cache. But I also switch the computer back and forth between Vista and Ubuntu and I run multiple projects. So it's easy for me to run down what I have before switching over. It actually worked out well for me recently. I was in the hospital and my computers were off for 10 days. I ended up only having the 3 running WUs (2 on one and 1 on the other) going over deadline. Kathryn :o) |
Send message Joined: 22 Aug 07 Posts: 3 |
I see that ABC hasn't introduced Work Cache size yet. When I use local preferences it will override the preferences for the project, right? Then i'' use that instead. Thanks for the help :) |
![]() ![]() Send message Joined: 30 Oct 05 Posts: 1239 ![]() |
I'm not sure what you mean... The work request (in seconds) is made by the core client and the server sends back the correct number of work units based on a few different factors. ABC might have its own setup where it will only send so many work units on each request (I know Cosmology does this). It's been quite a while since I ran ABC, so I can't say for sure. What I do remember is that their run times can vary dramatically so your duration correction factor (the ratio of how long a unit took to how long it was predicted to take) can get screwed up and result in too many or too few work units being downloaded. Kathryn :o) |
Send message Joined: 22 Aug 07 Posts: 3 |
I mean "* Change 'Cache enough work' to 0.1 from 0.25", that is not implemented yet. And yes, also because of the very veriabele WU sizes this is very usefull. |
![]() ![]() Send message Joined: 30 Oct 05 Posts: 1239 ![]() |
Ah yeah. I think their backend is pretty old. But if you change it locally through the manager, it *should* work (in theory). Kathryn :o) |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.