| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Stop TB
Thread: Using Scheduled boinccmd to get HSTB Work |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 158
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
With average 5000 units returned, it probably means roughly the same available. Those are not sufficient for everyone who wants some, especially if you take account of the number of threads each cruncher has. Mike This is nothing compared to the African Climate project that they had about 10 years ago... |
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
I have been able to receive a steady flow of work since May 15 and my 3 queues have managed to stay topped-off at 4 days with no observed problems. Therefore I just adjusted the queue size down to 2 days. If new work units are dependent on returned work that should [imperceptibly] help the flow.
----------------------------------------(<<<I remember the African Climate project. I was only able to crunch 15 days work of work!) Cheers   |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges: 
|
Is this still a sustainable strategy in 2018? Seems like there's about 1600 WUs per day, so slim pickings. I just finished getting Gold badges on every current project except for HSTB (and Beta) and want to focus 100% on HSTB. Even a Bronze badge!
----------------------------------------Currently all crunchers are empty and request work maybe once per hour on their own. I haven't yet set up the scheduled task for xx:03 and xx:33 yet.
[Edit 1 times, last edit by hchc at Mar 12, 2018 7:44:29 AM] |
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 771 Status: Offline Project Badges: 
|
With so few units likely only to get some at xx:03 and xx:33.
----------------------------------------Suggest for now set profile to 1.2 days, update, change selection to include other project(s), wait until filled to that level. Then set to only HSTB and 2 days, update. That may get you some but asking at about above times increases chances greatly. Paul.
Paul.
|
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges:
|
I have 2 4-core computers that I can keep a 2-day queue topped off. The WUs run about 24-36 hrs on them I have one 12-core computer that eats through the work faster than it can get them, so I have it running FAHB as well. The scheduled request for work is running on all of them. It works (currently).
----------------------------------------Cheers |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges:
|
I've since implemented the Windows Scheduled Task on 3 of my Windows boxes and have had pretty good success. I'm a 'Nix n00b, so I haven't set up a CRON job on my Debian Linux dual-core box yet, but it gets a few HSTB jobs every now and then using its built-in scheduler.
----------------------------------------Here are the Sent Times for the last 43 HSTB Work Units I've received (all times UTC): 3/7/2018 19:18 3/7/2018 19:21 3/7/2018 19:49 3/7/2018 19:50 3/7/2018 20:19 3/7/2018 20:19 3/7/2018 21:47 3/8/2018 8:18 3/8/2018 14:16 3/8/2018 17:32 3/9/2018 0:17 3/9/2018 0:20 3/9/2018 0:20 3/9/2018 8:18 3/9/2018 8:20 3/9/2018 8:21 3/9/2018 8:21 3/9/2018 14:17 3/9/2018 14:19 3/9/2018 20:17 3/9/2018 20:17 3/9/2018 20:18 3/10/2018 3:17 3/10/2018 3:18 3/10/2018 3:19 3/10/2018 9:17 3/10/2018 9:17 3/10/2018 9:47 3/10/2018 9:49 3/10/2018 9:49 3/10/2018 10:19 3/10/2018 15:16 3/10/2018 15:16 3/11/2018 21:17 3/11/2018 21:17 3/11/2018 21:18 3/11/2018 21:20 3/11/2018 21:46 3/11/2018 21:46 3/11/2018 21:47 3/11/2018 21:49 3/12/2018 3:17 3/12/2018 3:17 Interestingly, even though the Scheduled Task updates at xx:03 and xx:33 (as well as xx:05, xx:35, xx:07, xx:37), most of my HSTB WUs actually were sent at different times, such as xx:17 and xx:47...
[Edit 1 times, last edit by hchc at Mar 12, 2018 7:43:14 AM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges:
|
Is there an easy way to accomplish this in Linux? I'm a beginner. I'm looking into CRON, but it seems to be more of a learning curve to set up repetition.
----------------------------------------
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I suspect it is rather easier than you have grasped. Take a look at https://en.wikipedia.org/wiki/Cron
|
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges:
|
I suspect it is rather easier than you have grasped. Take a look at https://en.wikipedia.org/wiki/Cron You're correct. All I had to do was edit / etc /crontab as superuser and added: 03 * * * * boinc boinccmd --project http://www.worldcommunitygrid.org update for each instance I wanted the command to run.
|
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges:
|
To anyone reading this in 2018 or later, looking back on the last couple hundred HSTB work units I've received, setting the scheduler to :17 and :47 is vastly superior to :03 and :33. Most of my work units have been sent at :17, :19, :47, and :49, so setting the scheduler to update at :17/:47 will automatically try again after two minutes.
----------------------------------------
[Edit 1 times, last edit by hchc at Mar 23, 2018 7:15:20 PM] |
||
|
|
|