24 hr turn-around too short for dail-up

Message boards : Number crunching : 24 hr turn-around too short for dail-up
Message board moderation

To post messages, you must log in.

AuthorMessage
[B^S] RicketyCat
Avatar

Send message
Joined: 25 Apr 05
Posts: 3
Credit: 6,166
RAC: 0
Message 1534 - Posted: 10 Aug 2005, 23:06:25 UTC
Last modified: 10 Aug 2005, 23:07:56 UTC

Dail-up users (like me) might access their connections once per day, but not necessarily every 24 hours.

The problem occured today: I downloaded some work units and then logged off. I did not come back online and missed the return window by 9 minutes.

Result: wasted time and heat on my CPU for 6 units that I missed the return window of by a very short margin.

Possible solution: make the window every 36 to 48 hours to alleviate dail-up users aggravation. Aggravation like this might make some dail-up users skip a project like this.

Edit: I just checked my account info. and credit was granted for the missed units. I'm not sure how long the grace period is, though.
ID: 1534 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
John McLeod VII

Send message
Joined: 3 Mar 05
Posts: 51
Credit: 79,519
RAC: 0
Message 1535 - Posted: 11 Aug 2005, 0:27:42 UTC - in response to Message 1534.  

Dail-up users (like me) might access their connections once per day, but not necessarily every 24 hours.

The problem occured today: I downloaded some work units and then logged off. I did not come back online and missed the return window by 9 minutes.

Result: wasted time and heat on my CPU for 6 units that I missed the return window of by a very short margin.

Possible solution: make the window every 36 to 48 hours to alleviate dail-up users aggravation. Aggravation like this might make some dail-up users skip a project like this.

Edit: I just checked my account info. and credit was granted for the missed units. I'm not sure how long the grace period is, though.

Depends on the settings of the project and the speed of return of the other results.

If the project sends more copies of the WU than it needs for validation, then a late result has a very low chance of having credit granted. If the project sends exactly the number of copies of the WU that it needs for validation, then a slightly late result is racing to beat the replacement copy upload and report. The replacement copy has a new deadline and it will get credit if it makes it in before its deadline. The replacement copy is created and sent only after a result is late (or if there is a verification failure).

So, there is no simple answer. It would still probably be a great idea to increase the deadline to 30 hours to give some leeway for modem users.


BOINC WIKI
ID: 1535 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Steve Cressman
Avatar

Send message
Joined: 27 Mar 05
Posts: 142
Credit: 3,243
RAC: 0
Message 1537 - Posted: 11 Aug 2005, 2:50:23 UTC

From what I see it looks like we get just under 28 hours to do a burp unit not 24 hours.

Win98SE XP2500+ Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.
ID: 1537 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : 24 hr turn-around too short for dail-up