| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
medi
Cruncher Joined: Jun 11, 2006 Post Count: 3 Status: Offline |
Hi, I think I have a problem whit a WU. in two days the progress are only 4% and sometimes work restart from 0. why? and what can i do?
i hope you can understand me. if it could help you this is today's log of boinc. 22/08/2006 8.53.42||Starting BOINC client version 5.4.11 for windows_intelx86 |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Medi,
----------------------------------------IMHO, on reading your log is, that the FAAH never manages to reach a segment save point for the FAAH. 2 Options: 1. Set in the WCG BOINC profile a switch time to e.g. 12 hours.....it should be able to do 1 or more segments, if not the whole FAAH. 2. Obtain an alpha copy of the 5.5.x BOINC agent if existing for your OS. It considers segment save points (waits for it). My philosophy is that if u choose to run multiple projects, u can make it balance the time share over a longer period....BOINC will do it for u so at the end of the week, fortnight or whatever, each gets it's share according the weight u gave it ciao
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Aug 23, 2006 10:11:07 AM] |
||
|
|
medi
Cruncher Joined: Jun 11, 2006 Post Count: 3 Status: Offline |
but this is the first time that this problem occurs, with the same settings.
----------------------------------------moreover, it seems me that boinc agent before pausing a task to start another project waits for a checkpoint, but i'm not sure. i don't think it is better working such as an alphatester I can have much problems and losing my time to computing. well, maybe if the problem today is still present I will try with the first option. i have always completed a FAAH wu in 12hours thank you [Edit 1 times, last edit by medi at Aug 23, 2006 7:25:58 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Before version 5.5.x BOINC did not wait for a checkpoint. However, Sekerob's first option will accomplish the same thing. You also have a 3rd option, just abort the WU, it may be defective.
The techs can take note of the WU name and your computer ID from your log report and investigate further if they wish. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BOINC doesn't wait for a checkpoint. As you can see from the log, BOINC is switching religiously every hour. This is far too quick for some of the WCG projects, they checkpoint infrequently.
Set the timeslot to at least 6 hours, and you should be fine. A future version (now in alpha) takes the timeslot setting more as a guideline, and will run a work unit longer to reach a checkpoint if it can. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Medi,
----------------------------------------One more possible, call it option 4 (option 3 is printed in red ink ) ......there's a BOINC Profile setting to keep a WU in memory when paused......aside it could keep with the HDC WU 's up to 750mb in RAM/Virtual occupied, the hourly switching might not loose u the time. Other's use(d) it, but on mine the WU gets corrupted if e.g. the periodic benchmark kicks in. Can't find anywhere on this forum a discussion on BOINC's 'LTD' (Long Term Debt) and 'STD' (Shortest Term Debt) Work Scheduling . This is the accounting that BOINC performs for u over a longer period. If e.g. the 'Weight' of WCG is 25%, Rosetta 50%, SIMAP 25%, at the end of the week, each should have total hours close to 24*7*Weight. If for some reason, any project gets too much, it will stop that project for a while until it is in balance again with its weight. This can happen in situations of WU's that are close to deadline....they get first priority. There are FAAH's around that have no segments, thus even if interrupted at 99,999%, on restart it would go back to zero. On my machine a FAAH takes 7.5 to 8.5 hours CPU time, which translates somewhat less than 12 hrs in real life, hence that proposed wall-clock switch time of half a day. In Bocca Al Lupo Signed, The Trialist (Those who Try, Err, Those Trying a lot Err more.... There are Those that never Err) PS: The full explanation of LTD/STD here: BOINC Work Scheduler
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
medi,
Even the Pope kills a WU occassionally. For Sekerob a WU is a Sacred Cow that must never be killed. Set the work interval to 6 hours. If that does not cure the problem then step on an ant and kill the WU. It is not necessary to pray for forgiveness if you kill only 1. |
||
|
|
medi
Cruncher Joined: Jun 11, 2006 Post Count: 3 Status: Offline |
thanks to all.
I know how boinc sheuduling works, and this is the why I opened this topic. I haven't had problems such this and I never aborted o reported a WU after deadline. option 4 could be better than now but it could get slower performance, using too much swap file, and I can lose all data for shutting down my pc or a blackout. for the moment i'm going to try to suspend other projects and modify "switch time" to 720minutes (12 hours)to prevent future problems. I hope this can solve the problem (if there is one). I will give you more info if necessary when, and if, i will know much more than now. thanks to you all for the help |
||
|
|
|