| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: How can I force more beta units? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 83
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi all: I only receive 1 or 2 wu a week or less, even though many are available - how do I force the system to send me more - Is that even possible?
-- Mark Reiss |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The only thing, you can do, is to set your cache to a low number of days. Mine is at 0,5. ß-WU's have a short due time, so your client should be known as a "fast returner".
Also ß-work is not coming continously. There are a few tasks at the moment, but there are also periods, which last for weeks, where there is no ß-work at all. To gain your badge, the most importan thing is: be patient...!!!  |
||
|
|
gordoma
Veteran Cruncher Windsor, UK Joined: Jul 21, 2005 Post Count: 729 Status: Offline Project Badges: 
|
The only thing, you can do, is to set your cache to a low number of days. Mine is at 0,5. ß-WU's have a short due time, so your client should be known as a "fast returner". Is that still the case? I've noticed that I've been getting ß-WUs with a 2 day cache and it will run them as the next available WU whereever they are in my queue as they are set to high priority. On devices where I only run one project (unable to run HCMD2 on my Linux P3s at the moment, so only running FLU) I like to keep a reasonable cache in case the hopper of WUs temporarily runs dry at the point I try to download more work. When I put these devices back up to multiple projects then I was considering taking my buffer down to 0.1 days where it was before, but since the ß-WUs are taking priority, I wonder if there's any need. To be honest, I've been getting more ß-WUs since I set a 2-day buffer than I did at 0.1 days as I also set the "connect about every x days" option to do so more often - this seems to have had a better effect than lowering the buffer size. |
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1670 Status: Offline Project Badges: 
|
Hi,
----------------------------------------indeed I observed that the WU's cache size don't seem to have so a big importance. Sometime hosts with a larger cache (>.5 day) receive more beta WUs than hosts with a very short cache (<.5 day). Sometime beta WUs runs with high priority, sometime not (depending of the due date). Finally I assume that fetching beta WUs is very similar with the hope of winning by playing loto (there is anyway a huge difference: I enrolled my hosts to beta projects but I don't play loto  ).Cheers, Yves |
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1452 Status: Offline Project Badges:
|
why set 0.5 days?
----------------------------------------set 0.01 days, so every time your computer requests WU, it has a chance to get beta one, if exists. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Whether 2.01 or 0.01 days, the frequency of work requests does not change. Short jobs do promote more frequent requests for backfill of any size of cache and fast machines will be the ones that hit the servers more often.
----------------------------------------Beta work is the first thing checked if participation is activated, so it does not matter what project(s) are selected. And to repeat, no your client does not have to be a known reliable or fast returner. Anyone enrolled and not overrunning the daily quota gets them. Beta's generally have a short deadline, so they will jump queue anyhow even with bigger caches.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1452 Status: Offline Project Badges:
|
Whether 2.01 or 0.01 days, the frequency of work requests does not change. Short jobs do promote more frequent requests for backfill of any size of cache and fast machines will be the ones that hit the servers more often. yes but when Beta Test is announced, and you have 0.01 days queue, you can increase the cache size and catch some betas. Usually beta WUs have 2 days deadline, so if you sit on 2.01 days cache, you wont get a WU |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi all: I only receive 1 or 2 wu a week or less, even though many are available - how do I force the system to send me more You cant force the system to send you Beta WU unless there are Beta WU being distributed. We have gone for months at a time between Beta projects. Beta isnt like FA@H with 40,000 WU in the hopper. As suggested there are ways to increase your chances of getting a Beta WU but there are no guarantees. I had 8 C2D machines all identically configured and all reliable (no errors for over a month) and only 3 got a Beta WU. That is why it is hard to get a Beta Badge. Even if you have good timing and the right configuration, you still need some luck to get the right configuration at exactly the right time. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Whether 2.01 or 0.01 days, the frequency of work requests does not change. But if you have a 2.0 day buffer and the Beta WU is issued with a 2 day return, you are not going to get any Beta because your actual buffer is more likely 2.2 days |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
...I only receive 1 or 2 wu a week... I wish I received 1 or 2 beta wu a week  You should consider yourself lucky if you get that many  |
||
|
|
|