| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Stop TB
Thread: Limited workunits for Help Stop TB |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 752
|
|
| Author |
|
|
toss
Senior Cruncher New Zealand Joined: Jan 3, 2007 Post Count: 220 Status: Offline Project Badges: 
|
FWIW
I have improved my success in grabbing a few work units after manual PC clock sync. My clock was about 30 seconds ahead and therefore I was asking for work just before 3 + 33 mins. |
||
|
|
Jack007
Master Cruncher CANADA Joined: Feb 25, 2005 Post Count: 1604 Status: Offline Project Badges: 
|
FWIW I have improved my success in grabbing a few work units after manual PC clock sync. My clock was about 30 seconds ahead and therefore I was asking for work just before 3 + 33 mins. I'm going to have an aneurism if my clock is off, thought it was automatic for last 10 years of so... checking now. TY for the heads up! Edit: Whew, says it is set to auto sync with 'time.windows.com'  [Edit 1 times, last edit by Jack007 at Sep 6, 2016 3:19:43 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My favorite is time.is/utc
|
||
|
|
geoff.andreychuk
Cruncher Joined: Nov 2, 2015 Post Count: 42 Status: Offline Project Badges: 
|
Does anyone know when we will stop seeing limited workunits for this task?
---------------------------------------- |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
In my not so humble opinion, it will always be 'limited', per half/whole hour/day, simply because of the dependencies... a batch/group of results is the build-base for generating the next batch. (The same applies to FAH2). If one if buffering up for 3 days, than that and/or the 10 days deadline, simply makes for slow returning, so that delays new work being generated.
----------------------------------------That said, there's still beta testing ongoing because of various bugs, so we've never got to where the 200*2 copies tasks per 30 minutes flow got going as the scientists wanted, still well below the 100 (9600 a day). [Edit 1 times, last edit by SekeRob* at Sep 6, 2016 10:17:27 AM] |
||
|
|
JimWork
Cruncher Canada Joined: Oct 11, 2005 Post Count: 35 Status: Offline Project Badges: 
|
Thanks for your 'modest' opinion.
 Your explanation made me realized that I'm part of the problem - hoarding WUs. I'll reset my draw of HSTB WUs to no more than what I can process in 2-3 days. |
||
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4883 Status: Offline Project Badges: 
|
Thanks for your 'modest' opinion. Your explanation made me realized that I'm part of the problem - hoarding WUs. I'll reset my draw of HSTB WUs to no more than what I can process in 2-3 days. Setting cache for this project is a moving target because of the huge variability in runtimes.
4849
|
||
|
|
Sandvika
Advanced Cruncher United Kingdom Joined: Apr 27, 2007 Post Count: 112 Status: Offline Project Badges:
|
In my not so humble opinion, it will always be 'limited', per half/whole hour/day, simply because of the dependencies... a batch/group of results is the build-base for generating the next batch. (The same applies to FAH2). If one if buffering up for 3 days, than that and/or the 10 days deadline, simply makes for slow returning, so that delays new work being generated. My workaround is to buffer 3 days and every third day to add Zika to my device profile for a few hours, then take it off again (I was doing this with OET previously). This means that most of the time my hosts are trying to get HST units but most of the time they are actually crunching Zika and I'm not resorting to manual updates. I'm getting a lot of reissued WUs. I'd recommend the project to release at random rather than predicable times because this would deter hoarding behaviour and people would process what they get rather than hoard and not be able to process them.   |
||
|
|
AnRM
Advanced Cruncher Canada Joined: Nov 17, 2004 Post Count: 102 Status: Offline Project Badges:
|
Your suggestion of a random release should have been done a long time ago. The 10 day return time seems excessive also. This is by far the most awkward project to run in my experience :(
|
||
|
|
rbotterb
Senior Cruncher United States Joined: Jul 21, 2005 Post Count: 401 Status: Offline Project Badges: 
|
I still manage to get some HST WUs, but it seems like I'll go upwards of a week at a time without anything, then happen to hit the right alignment of the stars and maybe get upwards of 6 in one shot. Now I'm also one of those crunching Zika WUs, and find if I build in a buffer of a day or two for Zika WUs, before going to HST only and put my queue for four days and do that for a few days to try and snag a few HST WUs, I can SOMETIMES get some HST WUs. I find that the 3/33 clock stuff only works part of the time since most of the time all I get in my logs is that nothing is available for extended periods of time.
At this pace I'll still likely to get to my Gold Badge sometimes in the next 30 days or so, but I'm thinking at this rate I may need to go well into next year to get my Ruby let alone other bigger badges. I guess this makes for a frustrating project to work on for some crunchers - I just try to keep focused on the fact that whatever I do managed to do in the end is to help find treatments and maybe even a cure to something that has be a massive problem for the human race for hundreds/thousands of years. |
||
|
|
|