Patience is all you need to let the resource share balance out.
If you can't wait it out you can try resetting Einstein since it has no work. That should zero out the negative debt and let it get its 6 hour process time sooner.
Patients are for doctors... Now everything is happy.. The reset did it.
====================
So Dr. Wolf, took care of patient Einstein with a shot of......
Why doesn't this long term debt thing take into account projects such as Pirates@Home that does not have a steady supply of work? I don't want to leave Pirates incase there is some more work, but how do I get the long term debt worked off?
The BOINC client on this machine has ran out of work several times in the last couple weeks because of the new scheduling routine. I have tried resetting the projects, but that did not bring in new work. The only way I have found to get new work is to detach and then reattach.
The other problem I have seen on my work PC is that the scheduler only wants to work on the earliest deadline units. That effectivly means that it never works on the CPDN unit. I am going to suspend all of the other projects every weekend, just to get some work done on the CPDN. I would not want to come up on the deadline 10 months from now and have no way of getting it done in time.
I think they need to rethink the priority schedule routine.
Over in the SETI forums, John McLeod VII posted the following in a reply to a discussion of the scheduler.
Comment:
"I'm gradually liking it better and better, but I still have a problem with projects accumulating LongTermDebt when they don't have a WU on the client (for whatever reason). Seems to me that when this happens, when a flow of WUs does start again, those projects will get significantly more cycles (in order to "reduce the debt) than the ones that maintain a more or less constant flow of WUs, thus penalizing the ones that do maintain a flow."
"I know, I know, over weeks or months everything will balance out eventually, but if a project can't keep delivering WUs, why should it be rewarded when it finally does?"
"If I have mis-understood the way that the new scheduler works, I appologize."
And I will add my name to the request to create separate settings for "Connect Every" and "Cache Size" (Keep enough work for xx days of processing on my machine)."
John's reply:
4.43 or 4.44. I believe that I have addressed this in 4.44.
Over in the SETI forums, John McLeod VII posted the following in a reply to a discussion of the scheduler.
Comment:
"I'm gradually liking it better and better, but I still have a problem with projects accumulating LongTermDebt when they don't have a WU on the client (for whatever reason). Seems to me that when this happens, when a flow of WUs does start again, those projects will get significantly more cycles (in order to "reduce the debt) than the ones that maintain a more or less constant flow of WUs, thus penalizing the ones that do maintain a flow."
"I know, I know, over weeks or months everything will balance out eventually, but if a project can't keep delivering WUs, why should it be rewarded when it finally does?"
"If I have mis-understood the way that the new scheduler works, I appologize."
And I will add my name to the request to create separate settings for "Connect Every" and "Cache Size" (Keep enough work for xx days of processing on my machine)."
John's reply:
4.43 or 4.44. I believe that I have addressed this in 4.44.
Patience is all you need to
)
Patience is all you need to let the resource share balance out.
If you can't wait it out you can try resetting Einstein since it has no work. That should zero out the negative debt and let it get its 6 hour process time sooner.
Patients are for doctors... Now everything is happy.. The reset did it.
====================
So Dr. Wolf, took care of patient Einstein with a shot of......
Enjoy
Why doesn't this long term
)
Why doesn't this long term debt thing take into account projects such as Pirates@Home that does not have a steady supply of work? I don't want to leave Pirates incase there is some more work, but how do I get the long term debt worked off?
Einstein@Home
-99662.286048
Pirates@Home
142217.379764
ProteinPredictorAtHome
-42555.093717
The BOINC client on this machine has ran out of work several times in the last couple weeks because of the new scheduling routine. I have tried resetting the projects, but that did not bring in new work. The only way I have found to get new work is to detach and then reattach.
The other problem I have seen on my work PC is that the scheduler only wants to work on the earliest deadline units. That effectivly means that it never works on the CPDN unit. I am going to suspend all of the other projects every weekend, just to get some work done on the CPDN. I would not want to come up on the deadline 10 months from now and have no way of getting it done in time.
I think they need to rethink the priority schedule routine.
- Lee
Over in the SETI forums, John
)
Over in the SETI forums, John McLeod VII posted the following in a reply to a discussion of the scheduler.
Comment:
"I'm gradually liking it better and better, but I still have a problem with projects accumulating LongTermDebt when they don't have a WU on the client (for whatever reason). Seems to me that when this happens, when a flow of WUs does start again, those projects will get significantly more cycles (in order to "reduce the debt) than the ones that maintain a more or less constant flow of WUs, thus penalizing the ones that do maintain a flow."
"I know, I know, over weeks or months everything will balance out eventually, but if a project can't keep delivering WUs, why should it be rewarded when it finally does?"
"If I have mis-understood the way that the new scheduler works, I appologize."
And I will add my name to the request to create separate settings for "Connect Every" and "Cache Size" (Keep enough work for xx days of processing on my machine)."
John's reply:
4.43 or 4.44. I believe that I have addressed this in 4.44.
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=15215#118389
Over in the SETI forums, John
)
Over in the SETI forums, John McLeod VII posted the following in a reply to a discussion of the scheduler.
Comment:
"I'm gradually liking it better and better, but I still have a problem with projects accumulating LongTermDebt when they don't have a WU on the client (for whatever reason). Seems to me that when this happens, when a flow of WUs does start again, those projects will get significantly more cycles (in order to "reduce the debt) than the ones that maintain a more or less constant flow of WUs, thus penalizing the ones that do maintain a flow."
"I know, I know, over weeks or months everything will balance out eventually, but if a project can't keep delivering WUs, why should it be rewarded when it finally does?"
"If I have mis-understood the way that the new scheduler works, I appologize."
And I will add my name to the request to create separate settings for "Connect Every" and "Cache Size" (Keep enough work for xx days of processing on my machine)."
John's reply:
4.43 or 4.44. I believe that I have addressed this in 4.44.
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=15215#118389
I still don't have permission to add any extra settings.
BOINC WIKI