| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Unité Beta volatilisée --- Beta unit vaporized |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 17
|
|
| Author |
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
The micro workunits described above were due to a poor algorithm chosen to create child workunits when the parent workunit was going to take longer then the max limit set for the workunit. We were concerned this might happen but we decided to try it and see what happens.
We are modifying our plan to do the following: Each workunit will be assigned a time such as 6 hours. When 6 hours is reached, the workunit will check to see if it has computed 60% or more of the positions required for the workunit. If it has, then the workunit will continue running. If it hasn't, then the workunit will end gracefully and be returned to the server (and will then be chopped into additional workunits to complete the original set of work). If the workunit reaches twice the limit, then it will stop and return what it has to the server (and the remaining work will be sent out in additional workunits). We will divide the remaining working into X additional workunits of size Y. Y will be determined such that 95% of computers will be able to finish 60% of the work by the 6 hour time limit set for the workunit. We are modifying the HCMD2 application in order to accommodate this behavior. We are also modifying the validator and assimilator as well. |
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1671 Status: Offline Project Badges: 
|
Hello Kneed,
----------------------------------------Warm thank for this detailed explanation. The realization should be impressive, especially on the validator side. I wish that it will run as expected without too high risk of result loss. Cheers, Yves |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Maybe I don't have understand everythings, but,
for some people, you must know, that, when you send result, it doesn't appear immediatly in your list, you must wait for the update of the website (each 12h) to see them. After if, it's not this case, don't take car of this message :D ------ Peut être que je n'ai pas tout compris, mais, Pour certaines personnes, vous devez savoir que, quand vous renvoyez des résultats, ceux-ci n'apparraissent immédiatement dans votre liste. Il faut attendre que le site se mette à jour (toutes les 12H) pour les voir. Si je me suis planté dans ma réponse, et que ça n'a aucuns rapport, veuillez ne pas en tenir compte :D |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Maybe I don't have understand everythings, but, for some people, you must know, that, when you send result, it doesn't appear immediatly in your list, you must wait for the update of the website (each 12h) to see them. After if, it's not this case, don't take car of this message :D ------ Peut être que je n'ai pas tout compris, mais, Pour certaines personnes, vous devez savoir que, quand vous renvoyez des résultats, ceux-ci n'apparraissent immédiatement dans votre liste. Il faut attendre que le site se mette à jour (toutes les 12H) pour les voir. Si je me suis planté dans ma réponse, et que ça n'a aucuns rapport, veuillez ne pas en tenir compte :D hmmm, yes for the My Grid, My Statistics that is true. For the Result Status page it could even take up to 24 hours, the maximum time BOINC will wait to report a result if it has no other reason to communicate with the servers. PS: When you see a very big Beta disappear without a trace you've incurred a Vapo-Rex. This reply brought to you in Frenglish.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks Sekerob for the answer.
But, I don't understand something. What do you want to say with : This reply brought to you in Frenglish. I think it's a joke, but I don't understant it  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The micro workunits described above were due to a poor algorithm chosen to create child workunits when the parent workunit was going to take longer then the max limit set for the workunit. We were concerned this might happen but we decided to try it and see what happens. We are modifying our plan to do the following: Each workunit will be assigned a time such as 6 hours. When 6 hours is reached, the workunit will check to see if it has computed 60% or more of the positions required for the workunit. If it has, then the workunit will continue running. If it hasn't, then the workunit will end gracefully and be returned to the server (and will then be chopped into additional workunits to complete the original set of work). If the workunit reaches twice the limit, then it will stop and return what it has to the server (and the remaining work will be sent out in additional workunits). We will divide the remaining working into X additional workunits of size Y. Y will be determined such that 95% of computers will be able to finish 60% of the work by the 6 hour time limit set for the workunit. We are modifying the HCMD2 application in order to accommodate this behavior. We are also modifying the validator and assimilator as well. Is this going to be tested in Beta, or will it be immediately implemented in the HCMD2 WU's? The reason I ask, is that I am still getting HCMD2 WU's that are less than 3 hours long. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=25621
----------------------------------------Since this announcement, 22,000 work units went through the beta test channel ;>)
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|