Short Deadlines

Message boards : Number crunching : Short Deadlines
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Reeltime
Project donor

Send message
Joined: 3 Jun 08
Posts: 20
Credit: 52,234
RAC: 0
Message 8386 - Posted: 3 Jun 2008, 14:46:15 UTC

Is it normal for this project to have a 28 hour deadline?


Seems a bit short to me
ID: 8386 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
noderaser
Project donor
Avatar

Send message
Joined: 28 Mar 06
Posts: 516
Credit: 1,567,702
RAC: 0
Message 8388 - Posted: 4 Jun 2008, 2:03:35 UTC

Yes, to make the delivery of the rendered output faster, the deadlines are very short. You will still get credit for completed work that is sent in after the deadline, however.
Click here to see My Detailed BOINC Stats
ID: 8388 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile [AF] Rosalie Mignon

Send message
Joined: 11 Sep 07
Posts: 3
Credit: 7,353
RAC: 0
Message 8589 - Posted: 11 Aug 2008, 3:38:54 UTC

Hello,

I think the deadline is to short with the work you send now, I have a Q6600 with 4Go memory and can only run 2 wus as at time, the two others are waiting for memory, before the wu requested less memory.
ID: 8589 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
noderaser
Project donor
Avatar

Send message
Joined: 28 Mar 06
Posts: 516
Credit: 1,567,702
RAC: 0
Message 8590 - Posted: 11 Aug 2008, 5:46:10 UTC

Bottom line: Don\'t worry about the deadline.
Click here to see My Detailed BOINC Stats
ID: 8590 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Geoffrey Crick

Send message
Joined: 7 May 05
Posts: 2
Credit: 5,152
RAC: 0
Message 8768 - Posted: 22 Oct 2008, 12:45:18 UTC

The problem with short deadlines is that the client downloads the work units and immediately goes into finish nearest deadline first mode, thus making in not very friendly in the community of boinc projects.

Geoffrey
ID: 8768 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4574
Credit: 2,100,463
RAC: 8
Message 8769 - Posted: 22 Oct 2008, 16:43:06 UTC - in response to Message 8768.  
Last modified: 22 Oct 2008, 16:58:42 UTC

The clientside scheduler is a two-step scheduler - when more work is needed it first decides whether your resource share should allow it to even ask for more work for a given project. Then it uses a multiple of weights to figure out which workunit to run first. At least that\'s how I understand the code for it.

In other words, this does not give BURP (nor any other project) an unfair advantage. You fully control which project gets what percentage of your CPU power. The only difference is that when you allow BURP to run it will attempt to run that workunit to completion as quickly as possible.
ID: 8769 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Odd-Rod

Send message
Joined: 7 Aug 06
Posts: 10
Credit: 127,709
RAC: 12
Message 8770 - Posted: 22 Oct 2008, 17:59:21 UTC - in response to Message 8769.  
Last modified: 22 Oct 2008, 18:00:33 UTC

Geoffrey said:
The problem with short deadlines is that the client downloads the work units and immediately goes into finish nearest deadline first mode, thus making in not very friendly in the community of boinc projects.

In the short term that\'s true, but Boinc\'s Long Term Debt (LTD) system means that it won\'t download BURP WU\'s until it\'s allowed the other projects to get their resource share. So the other projects will get their share while BURP gets none for a while.

Janus said:
In other words, this does not give BURP (nor any other project) an unfair advantage. You fully control which project gets what percentage of your CPU power. The only difference is that when you allow BURP to run it will attempt to run that workunit to completion as quickly as possible.


One problem with short deadlines is something I\'m experiencing as I type this. If my host crunched 24/7 there would be no problem, but since I used my pc for several hours with no crunching taking place, I now have a WU which will probably miss the deadline. This could happen to any host which does not crunch 24/7.

Regards
Rod
ID: 8770 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Speedy

Send message
Joined: 25 May 06
Posts: 208
Credit: 676,104
RAC: 0
Message 8773 - Posted: 22 Oct 2008, 20:44:03 UTC - in response to Message 8386.  

Is it normal for this project to have a 28 hour deadline?

Yes this is normal. Don\'t worry about the deadline, you will still get credit for the task
Have a crunching good day
ID: 8773 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Geoffrey Crick

Send message
Joined: 7 May 05
Posts: 2
Credit: 5,152
RAC: 0
Message 8784 - Posted: 25 Oct 2008, 0:37:28 UTC - in response to Message 8770.  

Geoffrey said:
The problem with short deadlines is that the client downloads the work units and immediately goes into finish nearest deadline first mode, thus making in not very friendly in the community of boinc projects.

In the short term that\'s true, but Boinc\'s Long Term Debt (LTD) system means that it won\'t download BURP WU\'s until it\'s allowed the other projects to get their resource share. So the other projects will get their share while BURP gets none for a while.

And what would happen if all the projects decided to set short deadlines just so that they were processed quickly?

Janus said:
In other words, this does not give BURP (nor any other project) an unfair advantage. You fully control which project gets what percentage of your CPU power. The only difference is that when you allow BURP to run it will attempt to run that workunit to completion as quickly as possible.

...
Regards
Rod

Geoffrey
ID: 8784 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Short Deadlines