Justakiwi
Premium
join:2004-11-24
New Zealand
clubs:
|  [BOINC] R@H
I've just noticed that Rossetta@home hasn't been fetching any new work for days. I have no work left. I reset the project but it's made no difference. It's still doing absolutely nothing. I have it crunching 50% resource share with Seti.
Has anyone else got the same problem? 
--
"Stand up and walk out of your history" ~ Phil McGraw |
|
dandelion
Premium,MVM
join:2003-04-29
clubs: | Seems to be OK here, hope I'm looking at right place  |
|
mig
Premium,MVM
join:2000-10-26
Anytown, USA
clubs:
| reply to Justakiwi
Haven't had any problem getting work from the either. Sounds like what they call a Long Term Debt (LTD) problem that has to do with running multiple projects, "Suspending New Work" and the "No New Work" tasks in BOINC.
Here's a link that explains it Work-Fetch Policy and here's another link to a program BOINC Debt Viewer that lets you look at your debt value for each project. |
|
jons
Premium
join:2003-04-15
East Elmhurst, NY
clubs:
 ·Earthlink Cable Mo..
| reply to Justakiwi
I've had a similar problem with Rosetta in the past, and at a guess would assume something like what mig posted re:LTD sounds about right - though I haven't read about it and could be wrong! 
At any rate, I assume it's basically because my WUs from R@H have an earlier due date than the WUs I get from S@H. Though my BOINC program may be set to run Seti/Rosetta 50/50, it actually crunches the Rosetta WUs first (because of the earlier due date), and then has to make up for it later...
Is that what Long Term Debt it? Maybe I had better go visit the link... |
|
Justakiwi
Premium
join:2004-11-24
New Zealand
clubs:
| said by jons  :I've had a similar problem with Rosetta in the past, and at a guess would assume something like what mig posted re:LTD sounds about right - though I haven't read about it and could be wrong! At any rate, I assume it's basically because my WUs from R@H have an earlier due date than the WUs I get from S@H. Though my BOINC program may be set to run Seti/Rosetta 50/50, it actually crunches the Rosetta WUs first (because of the earlier due date), and then has to make up for it later... Is that what Long Term Debt it? Maybe I had better go visit the link... I checked out the Long Term Debt link, but I think it's going to take at least five more reads before I get my head around it 
I understand how WU will be pre-empted if there are other WU with earlier due dates, but obviously this debt thing is something entirely different. Would I not see some kind of message in my "messages" if this were a debt issue? As in something along the lines of "projected suspended" or something? I see no relevant messages at all.
I did have the machine shut down overnight a day or two ago while we were away for a couple of days - but I don't see that that should have affected anything. Seti picked up where it left off the moment I rebooted so I can't see why rosetta wouldn't have done the same.
I guess I'll just wait patiently and see whether it eventually kicks back in.
Thanks for your help!
--
"Stand up and walk out of your history" ~ Phil McGraw |
|
sortofageek
Premium,Mod
join:2001-08-19
Valhalla Dr
clubs:
·Comcast
Host:
Team Helix
Distributed Comput..
Linksys
Comcast HSI
Comcast Cable TV
edit:
July 14th, @01:35AM
|  quote:
I guess I'll just wait patiently and see whether it eventually kicks back in.
I can't help at this point, no experience. Hopefully mig or jons will be able to shed more light. I just wanted to say, I like your attitude. The race for the cures has always been a marathon, not a sprint.
--
Team Helix May 2006 Roll Call - Team Helix Forum - My Folding@Home Farm - Join Us? |
|
jons
Premium
join:2003-04-15
East Elmhurst, NY
clubs:
·Earthlink Cable Mo..
| reply to Justakiwi
said by Justakiwi :I checked out the Long Term Debt link, but I think it's going to take at least five more reads before I get my head around it I understand how WU will be pre-empted if there are other WU with earlier due dates, but obviously this debt thing is something entirely different. Would I not see some kind of message in my "messages" if this were a debt issue? As in something along the lines of "projected suspended" or something? I see no relevant messages at all. I guess I'll just wait patiently and see whether it eventually kicks back in. I don't claim to understand it completely, but I think I've worked out a way for my own head to make some sense of it! If my head is wrong, oh well... 
Anyway, say SETI and Rosetta are set to share BOINC 50/50. Maybe you have 5 WUs from each project lined up. For some reason, WUs from Rosetta seem to always be due much earlier than the ones from SETI. So all 5 are crunched and returned before the SETI ones (I guess that even though they are set to run 50/50, work due earlier gets a higher priority somehow).
Later on (in my case, at least), I won't get any work from Rosetta for awhile. I also tried resetting the project, etc. After a few days, more WUs for Rosetta come rolling in, and they're due before SETI again, so BOINC crunches mainly R@H for awhile...
Does that make sense? My brain's ok with it!  |
|
John Keck
Official Boinc-Er
join:2003-01-20
Vicksburg, MS
clubs:
| reply to Justakiwi
Nothing wrong with your explanation jons.
BOINC does give tasks extra processing time so that they are returned by the deadline. The long term debt tracks this and will prevent downloading from a project if it gets too far ahead of the other project(s). The best thing to do is let it work itself out, if you mess with it it almost always gets more out of whack.
Reducing your connect to setting will improve the odds that you will have tasks from both projects at the same time. It will take at least twice the longer setting before it settles out though. |
|
Justakiwi
Premium
join:2004-11-24
New Zealand
clubs:
| said by John Keck :Nothing wrong with your explanation jons. BOINC does give tasks extra processing time so that they are returned by the deadline. The long term debt tracks this and will prevent downloading from a project if it gets too far ahead of the other project(s). The best thing to do is let it work itself out, if you mess with it it almost always gets more out of whack. Reducing your connect to setting will improve the odds that you will have tasks from both projects at the same time. It will take at least twice the longer setting before it settles out though. Thanks people!
I just checked and we are back in business so I guess it must have been a debt issue as you both explained. I'm just curious though as to why BOINC doesn't present some kind of message to that affect. Something similar to the "computer is overcommitted" message you occasionally see.
John Keck what do you suggest as a sensible "connect to" setting? I used to have it set to 5 days but reduced it down to 3 yesterday. I've never really been too sure what's the best option with that. I actually tend to manually update every day anyway, just to get results reported more frequently, so I guess it really doesn't matter too much what my connect to setting is, in that case.
Thanks again for your help everyone!
--
"Stand up and walk out of your history" ~ Phil McGraw |
|
John Keck
Official Boinc-Er
join:2003-01-20
Vicksburg, MS
clubs:
| I recommend a maximum queue size of (0.45 * shortest deadline) divided by the number of projects. That formula does not work as well now that the SETI deadlines are all over the place though.
The other way to figure is take the longest time you expect a local outage to last and divide by the number of projects. For example I expect a worst case outage to be 3 days if it happens on Friday afternoon and fixed on Monday. If I am attached to 3 projects then I need a 1 day queue.
My personal queue is normally 0.1 days since I am attached to a minimum of 6 and a max of 15 projects on each host. It is currently set at 0.9 for testing purposes. |
|
