| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: I keep getting tasks? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So, my computer run's around 7 tasks at once. Don't know why or how but it does. However, when i complete one or finish up something, world community grid keeps giving me more and more tasks and some of them have really short deadlines. I'm worried that eventually I'll have 100+ tasks to do. So, why do i keep getting tasks when i already have other tasks to do? How do i stop getting them? It's just too much.
|
||
|
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: 
|
You will find all of those settings in computing preferences which is in the tools tab in advanced view.
----------------------------------------Network usage tab has a minimum work buffer setting which if you set to say half a day will only allow you to get half a day of work sitting waiting to be done  |
||
|
|
noderaser
Senior Cruncher United States Joined: Jun 6, 2006 Post Count: 297 Status: Offline Project Badges: 
|
How many cores does your CPU have? WCG tasks are single-threaded applications, so you will get one task per CPU core. The BOINC manager should be capable of keeping a number of tasks ready for computing, according to your preferences, without having many go past their deadline--unless your up time suddenly changes and its calculations no longer reflect the actual amount of work your host needs.
---------------------------------------- |
||
|
|
CandymanWCG
Senior Cruncher Romania Joined: Dec 20, 2010 Post Count: 421 Status: Offline Project Badges: 
|
Hello warownslife and welcome to the forums.
----------------------------------------Before going into the Advanced view and Computing preferences like OldChap well suggested, I would rather start here, on the wcg site and go to Settings (top right side of the page), then Device manager, find the name of your machine and click on the name of the profile corresponding to that machine (probably "Default"). Once you get on that page, scroll down to "Cache" and set it to 0, if you don't wish to have any Work Units queued while your CPU is busy crunching. However, I would advise against that, because it may happen that the servers will be unavailable to download new work when your machine will finish its current tasks and then it will idle until the server is back online, so, you see, it would make sense to keep a cache of, say, 0.5 days. I would also mention that the server will normally not push more work onto your machine than it can handle, not even if you want it too (e.g. set the Cache to 100 days). So don't fret. The only scenario where I would understand you not wanting to keep any WUs queued is if you don't leave your machine on a lot and you are afraid that it will not complete those tasks on time. I hope this helps. Cheers!  Edit1: re-arranged my wording a bit Edit2: added "normally" Knowledge is limited. Imagination encircles the world! - Albert Einstein   [Edit 2 times, last edit by CandymanWCG at Oct 21, 2015 12:42:09 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
The client caches work scaled to the number of computing hours per day, an average of something like the last 10 days. The noted sudden change of up-time downward, will temporarily lead to having too much work to handle, but that will be rapidly scaled down, and slowly increased [defensive logic]. Any idle thread will though lead to immediate work requesting to re-occupy those idle threads. If jobs expire during power-off, no worries. New copies will be sent out to other machines and any redundant/expired copies will be cancelled automatically [before starting]. If a task was started before power-off, then when powering on has already expired, you'll get a red-line warning notice to cancel the job manually, in some situations even the server will tell the client on first re-connect to abort a task as 'no longer usable'.
BOINC is 12 years or so, rather mature it what it all takes care off, even a lot the user manages to configure 'too optimistic'. Sometimes something goes wrong, which often stems from using an old client that is not fully aligned with the project server side version, or a bug, but they are becoming rare [and no this comment is not an invitation for argument]. |
||
|
|
|