Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: Settings that might make me miss out on Betas? |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 15
|
Author |
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: |
The last round of Betas that were issued came and went and I am not sure that I got any which made me wonder....
----------------------------------------Are there any settings, such as number of days cache, which would automatically stop me from getting these units. I would love to progress that particular badge to the next level (at least) and want to give myself the best possible chance. |
||
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
The only setting that concerns beta units is that you choose to participate. The remainder involves mostly luck and timing.
----------------------------------------I do anticipate some additional settings being implemented for the HCC GPU betas, but at this point no one can say (with any accuracy) what they might be. Betas are assigned to all machines equally. There is no requirement for being reliable, fast, or any such measurement. Occasionally, they will release a round for a particular operating system; this would be announced if those conditions were present. If you're willing to research the best ways to get beta results, that topic has been thoroughly addressed in the forum. Distributed computing volunteer since September 27, 2000 |
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: |
Many thanks and Ni to you Sir Knight.
----------------------------------------My concern was that setting a large cache might mean that results would automatically be returned more slowly (unless the priority system catches them) and that such would be undesirable for the science/beta team. I will wait in line... There is no need to chase these |
||
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: |
actually yes, if you have a large cache it will prevent you from getting a beta. This is because betas have a deadline of 4 days or less, so if you already have 4 days of work, you can forget about getting a beta.
----------------------------------------edit: spelling [Edit 1 times, last edit by anhhai at Jan 17, 2012 11:10:53 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
In Russian that would be "Njet".
----------------------------------------There's a Beta FAQ in Start Here for the interested. --//-- [Edit 1 times, last edit by Former Member at Jan 17, 2012 11:25:50 PM] |
||
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
actually yes, if you have a large cache it will prevent you from getting a beta. This is because betas have a deadline of 4 days or less, so if you already have 4 days of work, you can forget about getting a beta. edit: spelling Not sure I agree with your reasoning here. As long as the client is asking for work, the project will send it. If the unit won't finish in the allotted time then it will trigger high priority mode. Betas have a very high priority in the scheduler. If they're available when the client requests work, they should be first in line to be sent. Distributed computing volunteer since September 27, 2000 |
||
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: |
Not sure I agree with your reasoning here. As long as the client is asking for work, the project will send it. If the unit won't finish in the allotted time then it will trigger high priority mode. Betas have a very high priority in the scheduler. If they're available when the client requests work, they should be first in line to be sent. KWSN - A Shrubbery, If you don't believe me you can run a simple test if you are not currently crunching HCC. Download 7 days of work (non-HCC or else, you will cause problems for yourself), then modify your profile to only accept HCC. Now increase your cache and look at your message window. It will tell you that while there is work, you can't download it because you won't finish it in time. This is the same as for betas, I know because I had it happen to me. I had to delete some of my WUs to free up some space |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Let us not forget the need to assess the chances of a receiver to first catch the ball relative to the defense, and next the chances for a touchdown after the reception of the ball. A 4-day cache for a 4-day deadlined WU presents a tough defense coverage for any receiver cruncher. This cruncher will not likely get the ball thrown to him regardless of how much of a superstar receiver the cruncher is, or how much of a super-accurate passer the quarterback scheduler is. Instead, those receivers who are wide open will likely get the beta ball, and with that, a very likely touchdown, and with that win game after crunch after game after crunch after crunch. Because the OP's query is how to increase the chances of getting the beta ball, a low cache setting is just about right on the
; |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not sure I agree with your reasoning here. As long as the client is asking for work, the project will send it. If the unit won't finish in the allotted time then it will trigger high priority mode. Betas have a very high priority in the scheduler. If they're available when the client requests work, they should be first in line to be sent. KWSN - A Shrubbery, If you don't believe me you can run a simple test if you are not currently crunching HCC. Download 7 days of work (non-HCC or else, you will cause problems for yourself), then modify your profile to only accept HCC. Now increase your cache and look at your message window. It will tell you that while there is work, you can't download it because you won't finish it in time. This is the same as for betas, I know because I had it happen to me. I had to delete some of my WUs to free up some space Yes, but that is for work the client ''has'', not for what it wants to receive, anhhai. As long as the client is not in an alert / hi priority state of processing on all cores/threads, work will be fetched of any deadline denomination! So the proposition of not getting beta on a high cache will still get the Russian answer. Beta FAQ, last paragraph, first line. (Why do we write them?) --//-- [Edit 1 times, last edit by Former Member at Jan 18, 2012 7:33:24 AM] |
||
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: |
SekeRob, yes, I know I read your FAQ before posting the second time. However, from my experience, even if none of my WUs are in the hi priority state, I will not be able to get new betas if the schedulers thinks that I will not finish the work on time. This usually happens on my older machines. It doesn't really matter, since most ppl who are trying to get betas have tons of way around it.
---------------------------------------- |
||
|
|