Personally, I have a always on connection. I have my connect every setting of 0.5 days. The only time I ran out of WU's was in the last couple of days when my router quit working. My laptop finished all 3 WU's it had. The other 2 computers still had WU's to work on, including CPDN.
Jim
Quote:
this makes no sence why would they design it this way.
now It shares set to connect 3.4 days, I think it should share anyway as long as there is enough time to crunch and then if time gets short use EDF.
OH well as long as it works I guess I can live with it.
thanks for the sugestions
There are a number of rules that determine when it does or does not go into that mode. I am not going to try to cover them here as all that is described in the Wiki. But, the rules work, and pretty well ... there are still a couple little things that catch some people and we won't see that fixed until the next release.
When I first started running the 4.4x versions it was hard to now want to jump in and try to push the CPU scheduler around. But patience, and a little time and I don't have any complaints. But, you have to give the system time to work down your current work, and then to start to schedule according to its rules. It takes at LEAST a week to sort itself out. Longer if you have longer connect intervals.
So, you will see it do Einstein@Home and run out of work, then it works on other projects until it starts to call work in ON ITS TERMS .... so, first you have to let it get stable, and then to start working by its rules, not the old rules.
Mine acted odd for at least 7 days ... but watching the boards and people telling other to be paitent I rode it out and it just works ... and I have 5 projects on most computers too ...
this makes no sence why would they design it this way.
now It shares set to connect 3.4 days, I think it should share anyway as long as there is enough time to crunch and then if time gets short use EDF.
OH well as long as it works I guess I can live with it.
thanks for the sugestions
Ok, think about a modem user for a few minutes that can only connect once every 7 days. They connect on the first day and get 7 days worth of work, and it had better have deadlines at least 7 days away or there is trouble. They connect 7 days later, and upload and download work. At this point, any work that has a deadline less than 7 days from now must be complete and ready to upload/return as it will be past deadline by the next connection. Therefore if any deadline for uncompleted work is less than 2* the connect time, it is nessecary that the scheduler enter EDF so that the work can be returned on time. It is not nessecary to limit work download in this case (with the exception that all work must have a longer deadline than the connect interval).
Thank you for explaining something that I couldn't. I understood in my own mind, but didn't have the information at the top of my head to explain it.
It's also frustrating to me that you (James) refused to listen to my advice, but when others said to reduce the time you did... it was my very first suggestion!!!!!!
Personally, I have a always
)
Personally, I have a always on connection. I have my connect every setting of 0.5 days. The only time I ran out of WU's was in the last couple of days when my router quit working. My laptop finished all 3 WU's it had. The other 2 computers still had WU's to work on, including CPDN.
Jim
Jim
James, There are a number
)
James,
There are a number of rules that determine when it does or does not go into that mode. I am not going to try to cover them here as all that is described in the Wiki. But, the rules work, and pretty well ... there are still a couple little things that catch some people and we won't see that fixed until the next release.
When I first started running the 4.4x versions it was hard to now want to jump in and try to push the CPU scheduler around. But patience, and a little time and I don't have any complaints. But, you have to give the system time to work down your current work, and then to start to schedule according to its rules. It takes at LEAST a week to sort itself out. Longer if you have longer connect intervals.
So, you will see it do Einstein@Home and run out of work, then it works on other projects until it starts to call work in ON ITS TERMS .... so, first you have to let it get stable, and then to start working by its rules, not the old rules.
Mine acted odd for at least 7 days ... but watching the boards and people telling other to be paitent I rode it out and it just works ... and I have 5 projects on most computers too ...
RE: this makes no sence why
)
Ok, think about a modem user for a few minutes that can only connect once every 7 days. They connect on the first day and get 7 days worth of work, and it had better have deadlines at least 7 days away or there is trouble. They connect 7 days later, and upload and download work. At this point, any work that has a deadline less than 7 days from now must be complete and ready to upload/return as it will be past deadline by the next connection. Therefore if any deadline for uncompleted work is less than 2* the connect time, it is nessecary that the scheduler enter EDF so that the work can be returned on time. It is not nessecary to limit work download in this case (with the exception that all work must have a longer deadline than the connect interval).
BOINC WIKI
Thank you for explaining
)
Thank you for explaining something that I couldn't. I understood in my own mind, but didn't have the information at the top of my head to explain it.
It's also frustrating to me that you (James) refused to listen to my advice, but when others said to reduce the time you did... it was my very first suggestion!!!!!!
(excuse my little GRRR)