You said you were going to lower your queue size down to 2 days. Did you do that? Also, I've seen people claim that it could take as much as a week for things to stabilize after a change like that.
Quote:
Quote:
Quote:
Quote:
You might want to try a reset, or several times a reset, on the E@H project. This will bring the LTD to a value allowing Boinc to download fresh WU's.
Resetting worked, Thanks!
Be sure not to do a reset if you have still WU's or you will loose them. This workaround is only good if you don't have any WU anymore.
You said you were going to lower your queue size down to 2 days. Did you do that? Also, I've seen people claim that it could take as much as a week for things to stabilize after a change like that.
Quote:
Quote:
Quote:
Quote:
You might want to try a reset, or several times a reset, on the E@H project. This will bring the LTD to a value allowing Boinc to download fresh WU's.
Resetting worked, Thanks!
Be sure not to do a reset if you have still WU's or you will loose them. This workaround is only good if you don't have any WU anymore.
And is also defeats your resource shares.
Okay. Einstein has taken over again????
Did that & it completed aal the work units; would not download more until I reset the project 3 times, then it took over again on 2 PCs, WinXP & Win2K.
1. Don't set your "connect to xx days" too high, especially if participating in different projects.
A setting of 1.5 or 2 days works fine for me, running a and running S@H, LHC@Home and E@H.
2. Don't pannic when upgrading from an earlier version if in the beginning Boinc doesn't download WU's anymore the first days for a certain project. It will once everything is settle down. This can take one or 2 days.
The first time I used 4.45 I was impatient also, get rid of 4.45 and went to the earlier version. But came back to 4.45, had more patient and after some 2 days I saw the results.
Just let Boinc manage things, it will ! Trust the software, it is working great.
I know it has been stated in this post at least 3 times,but here we go again, there is nothing wrong with the way 4.45 works, just set the connect to to a resonable number sit back and let it do it's thing............The slower your computer the lower the connect to should be............
I know it has been stated in this post at least 3 times,but here we go again, there is nothing wrong with the way 4.45 works, just set the connect to to a resonable number sit back and let it do it's thing............The slower your computer the lower the connect to should be............
READ THE WIKI
I've read the Wiki, I've set my connect time to 2 days (for the last six months, (reasonable for an AMD64 3000) and I fully understand the concept of Short/Long term debt and the scheduler's rules of fetching WU's.
How come E@H receives 45hrs of work to be completed in 7 days when my resource is set at 8% (which is about 14hrs of 7 days)? This leads to overcommitment of boinc, ie panic mode, no work fetch (all projects) and earliest deadline first.
And why does this ONLY happens with E@H?
I agree that BOINC is 100% correct, however, I suspect there is a problem on the E@H server side that incorrectly calculates the number of WUs to be sent based on the processing time BOINC asks for.
Please see my detailed explanation of the problem at
If my memory serves me correctly, the scheduler underestimates the time needed to crunch a WU then calculating how many WU's to send out, at leas for some computers. Back in Jan-Feb i got to see the server side log for one of my work requests then investigating an other problem. The server thought that a WU would crunch in 28H then it in reality would take 40H on my PIII 450. If this is still true and also for faster computers I don't know. You can only get this information from the server log and should not be confused with the estimated time to completion seen on the client.
The next time you request work from the project, look at the message tab and see how many sec of work you requested and compare with the estimated crunch time for these WU's on the client. Don't forget that you always will get more work then requested, so also compare it with the estimated time for one WU less then you got.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
I know it has been stated in this post at least 3 times,but here we go again, there is nothing wrong with the way 4.45 works, just set the connect to to a resonable number sit back and let it do it's thing............The slower your computer the lower the connect to should be............
READ THE WIKI
I've read the Wiki, I've set my connect time to 2 days (for the last six months, (reasonable for an AMD64 3000) and I fully understand the concept of Short/Long term debt and the scheduler's rules of fetching WU's.
How come E@H receives 45hrs of work to be completed in 7 days when my resource is set at 8% (which is about 14hrs of 7 days)? This leads to overcommitment of boinc, ie panic mode, no work fetch (all projects) and earliest deadline first.
And why does this ONLY happens with E@H?
I agree that BOINC is 100% correct, however, I suspect there is a problem on the E@H server side that incorrectly calculates the number of WUs to be sent based on the processing time BOINC asks for.
Please see my detailed explanation of the problem at
I'll let it alone for 7 days and see, but I'm still not getting any work. The is something wrong with 4.45 & Einstein. Seti & Climate work fine!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
RE: RE: RE: You might
)
Okay. Einstein has taken over again????
You said you were going to
)
You said you were going to lower your queue size down to 2 days. Did you do that? Also, I've seen people claim that it could take as much as a week for things to stabilize after a change like that.
Jim
RE: You said you were going
)
Did that & it completed aal the work units; would not download more until I reset the project 3 times, then it took over again on 2 PCs, WinXP & Win2K.
Golden rules to continue
)
Golden rules to continue receiving WU's:
1. Don't set your "connect to xx days" too high, especially if participating in different projects.
A setting of 1.5 or 2 days works fine for me, running a and running S@H, LHC@Home and E@H.
2. Don't pannic when upgrading from an earlier version if in the beginning Boinc doesn't download WU's anymore the first days for a certain project. It will once everything is settle down. This can take one or 2 days.
The first time I used 4.45 I was impatient also, get rid of 4.45 and went to the earlier version. But came back to 4.45, had more patient and after some 2 days I saw the results.
Just let Boinc manage things, it will ! Trust the software, it is working great.
Greetings from Belgium
Thierry
This problem seems similar to
)
This problem seems similar to the "overcommitted" thread's problem at
http://einsteinathome.org/node/189289
I know it has been stated in
)
I know it has been stated in this post at least 3 times,but here we go again, there is nothing wrong with the way 4.45 works, just set the connect to to a resonable number sit back and let it do it's thing............The slower your computer the lower the connect to should be............
READ THE WIKI
Link to Unofficial Wiki for BOINC, by Paul and Friends
RE: I know it has been
)
I've read the Wiki, I've set my connect time to 2 days (for the last six months, (reasonable for an AMD64 3000) and I fully understand the concept of Short/Long term debt and the scheduler's rules of fetching WU's.
How come E@H receives 45hrs of work to be completed in 7 days when my resource is set at 8% (which is about 14hrs of 7 days)? This leads to overcommitment of boinc, ie panic mode, no work fetch (all projects) and earliest deadline first.
And why does this ONLY happens with E@H?
I agree that BOINC is 100% correct, however, I suspect there is a problem on the E@H server side that incorrectly calculates the number of WUs to be sent based on the processing time BOINC asks for.
Please see my detailed explanation of the problem at
http://einsteinathome.org/node/189289
If my memory serves me
)
If my memory serves me correctly, the scheduler underestimates the time needed to crunch a WU then calculating how many WU's to send out, at leas for some computers. Back in Jan-Feb i got to see the server side log for one of my work requests then investigating an other problem. The server thought that a WU would crunch in 28H then it in reality would take 40H on my PIII 450. If this is still true and also for faster computers I don't know. You can only get this information from the server log and should not be confused with the estimated time to completion seen on the client.
The next time you request work from the project, look at the message tab and see how many sec of work you requested and compare with the estimated crunch time for these WU's on the client. Don't forget that you always will get more work then requested, so also compare it with the estimated time for one WU less then you got.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
RE: RE: I know it has
)
I'll let it alone for 7 days and see, but I'm still not getting any work. The is something wrong with 4.45 & Einstein. Seti & Climate work fine!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Hi Gordon, Still the same
)
Hi Gordon,
Still the same problem for me as well. Read our disscussion at
http://einsteinathome.org/node/189616
V7