| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: BOINC fetched too many FAAH WUs on wrong assumption of CPU time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
Recently, many FAAH WUs that took only about 20% of the usual time were sent out - see post in Known Issues: "Temporary No Work Available Messages on BOINC" - knreed, 08/02/20.
More recently, my instance of BOINC downloaded about 80 WUs to maintain my 3-day queue, assuming that they'd take about 1hr20 each. However, the ones crunching now are taking 4 - 6 hrs each, and some will not be crunched before their return deadline. Will the FAAH WCG operators be extending the deadline for such WUs, or will you just allow them to time out? In a case of really good timing, I will shortly have house guests staying in my computer room so the machine will be off overnight for the first time in over 1 year. Normally for such an event, I'd click on "No new tasks", but it's already too late because the queue is already too long. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Suggest you make an educated guess of what you can finish before power down and abort the rest. This way they return immediately back to the scheduler pool for redistribution. No reason to feel bad about it, in fact, overall it speeds up the project rather than having them expire or get a 'too late' and risk of no credit.
----------------------------------------Yes the size change caused havoc and it takes a few days for the systems to adjust again to new average flop counts (the servers keep track from the returned work and feed that into the headers of new work submitted).
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|