| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Drug Search for Leishmaniasis Forum
Thread: Welcome to the Drug Search for Leishmaniasis (DSFL) project |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 106
|
|
| Author |
|
|
alver
Senior Cruncher Joined: Nov 30, 2007 Post Count: 245 Status: Offline Project Badges: 
|
Excellent to see a new project start - it seems like a long time since the last one. Also pleased to see it's a 'small molecule drug discovery' one - my favourite type. I'll be in with 13 cores (100% for a while at least), just as soon as I reach 10Y on HFCC, which should be by the end of next week. Looking forward to starting. Good work everyone.
---------------------------------------- (previously known as 'proxima' on SETI, UD, distributed folding, FaD, and Rosetta) |
||
|
|
jimolson3
Cruncher Joined: Nov 23, 2005 Post Count: 2 Status: Offline Project Badges: 
|
Can I ask a dumb question? I have been crunching for years, but have never uncovered the ability to order the computing of tasks. smeyer55 indicated:
Mine are due the 10th and are estimated at 7hours run time. Pushed them up so they are running. The first one took about 1/2 hour to get to 9% done. I generally don't care about order, but sometimes my tasks get close to report deadline and I want to get them done before they expire. BOINC seems to pick the tasks at random, and definitely not by report deadline. Thanks! |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Can I ask a dumb question? I have been crunching for years, but have never uncovered the ability to order the computing of tasks. smeyer55 indicated: I have seen this situation come up and I do two things to help insure the WUs are executed in the order I want:Mine are due the 10th and are estimated at 7hours run time. Pushed them up so they are running. The first one took about 1/2 hour to get to 9% done. I generally don't care about order, but sometimes my tasks get close to report deadline and I want to get them done before they expire. BOINC seems to pick the tasks at random, and definitely not by report deadline. Thanks! First, I keep the "Additional work buffer" days set to a small enough value (one I feel comfortable with) to allow me to access all of the WUs in the queue relatively easily. Second, when I see WUs I want to have executed more quickly, I suspend all those "Ready to start" that are before the one I want to run immediately and then I suspend one of the ones "Running". This will cause the one I want to run to start immediately. I then go back to the WUs I suspended and "Resume" those WUs. Note that all of the things I listed in the second item must be done in the correct order. If there is more than one you want to start running, then you will need to suspend as many running WUs as needed to get the ones you want to run running. |
||
|
|
jimolson3
Cruncher Joined: Nov 23, 2005 Post Count: 2 Status: Offline Project Badges:
|
Can I ask a dumb question? I have been crunching for years, but have never uncovered the ability to order the computing of tasks. smeyer55 indicated: I have seen this situation come up and I do two things to help insure the WUs are executed in the order I want:Mine are due the 10th and are estimated at 7hours run time. Pushed them up so they are running. The first one took about 1/2 hour to get to 9% done. I generally don't care about order, but sometimes my tasks get close to report deadline and I want to get them done before they expire. BOINC seems to pick the tasks at random, and definitely not by report deadline. Thanks! First, I keep the "Additional work buffer" days set to a small enough value (one I feel comfortable with) to allow me to access all of the WUs in the queue relatively easily. Second, when I see WUs I want to have executed more quickly, I suspend all those "Ready to start" that are before the one I want to run immediately and then I suspend one of the ones "Running". This will cause the one I want to run to start immediately. I then go back to the WUs I suspended and "Resume" those WUs. Note that all of the things I listed in the second item must be done in the correct order. If there is more than one you want to start running, then you will need to suspend as many running WUs as needed to get the ones you want to run running. dkt - Makes sense to me. I'll follow your suggestions. However, I'm guessing that following #1 will likely make #2 less necessary. I had cranked up my queue in the past when I was expecting intermittent connectivity and didn't want to run out of work. Thanks so much for the quick response!!  |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
jimolson3, welcome to the forum, albeit after 6years. Glad to hear you at least read some threads in that time.
I find setting a "switch between applications every" to a high number (990), forces running tasks to continue running to completion, usually. So if you force a task to start, it should also complete  PS. Remember to resume tasks  Good luck, |
||
|
|
mfbabb2
Senior Cruncher USA Joined: Feb 18, 2011 Post Count: 361 Status: Offline Project Badges: 
|
Boinc Manager will start tasks in a FIFO (first-in, first-out) order unless a dead-line will be missed, then it goes into panic mode. It will also partially start several about to be overdue tasks and cycle between them (assuming you will get credit if just a bit late, so as not to be server aborted for past due and not started).
----------------------------------------This is my experience and is not to be taken as Boinc Gospel.
Murphy
 |
||
|
|
|