chronological order


log in

Advanced search

Questions and Answers : Wish list : chronological order

Author Message
Profile Levi
Send message
Joined: 3 Jun 99
Posts: 14
Credit: 1,940,937
RAC: 2,683
United States
Message 1037451 - Posted: 30 Sep 2010, 16:51:49 UTC
Last modified: 30 Sep 2010, 16:54:03 UTC

Over the 11 years I have been shareing I have had to wait for my wingman up to 50 days. The last one to do this was a month or so ago. I kept checking the other user progress. They had like 1400+/- I noticed that the WU I was waiting on was 20+ pgs down . Getting to the page I noticed that the other comp was processing newer wu's ahead of the one I was looking for. I also noticed they ended up with many timed outs. Which was also the one I was waiting on. It got assigned to someone else & about 5 days later I finally got credit for it.
I would like to request a chrono lock on wu's so they are processed in the order they are received, of course allowing for the quickies.

something like
if p=1 then run pwu
if p=0 then run chronowu

sorry haven't studied cl's since FORTRAN IV,cobol and basic

please
____________

Profile Gundolf Jahn
Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 354,909
RAC: 21
Germany
Message 1037456 - Posted: 30 Sep 2010, 16:57:46 UTC - in response to Message 1037451.

The symptoms you describe point to ghost units. So, the host probably wasn't able to process the task, since it hadn't received it.

Gruß,
Gundolf
____________
Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13304
Credit: 27,835,289
RAC: 16,155
United States
Message 1037458 - Posted: 30 Sep 2010, 16:59:32 UTC - in response to Message 1037451.

Processing in chronological order has proven to be inefficient in scheduling for multiple projects with differing deadlines.

In fact, it's likely that the ones that timed out on the other user's machine with ealier deadlines were in fact "ghost" workunits that didn't exist when the server thought they did. No amount of "in order" scheduling will fix that.

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 23702
Credit: 493,107
RAC: 127
United States
Message 1037613 - Posted: 1 Oct 2010, 0:30:45 UTC - in response to Message 1037458.

Processing in chronological order has proven to be inefficient in scheduling for multiple projects with differing deadlines.

In fact, it's likely that the ones that timed out on the other user's machine with ealier deadlines were in fact "ghost" workunits that didn't exist when the server thought they did. No amount of "in order" scheduling will fix that.

Within a project the default order is the order received though. It is extremely likely this is a ghost WU.
____________


BOINC WIKI

Questions and Answers : Wish list : chronological order

Copyright © 2014 University of California