| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: New Project Beta WUs |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 117
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Still nothing
What about this ; If enrolled in Beta and the machine asks for work, it checks first in the beta queue (if the beta feeder is activated by the techs I suppose). Thanks JP |
||
|
|
hunterkasy
Senior Cruncher USA Joined: Dec 8, 2008 Post Count: 300 Status: Offline Project Badges: 
|
I have 14 of the beta WU's on only 1 machine
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The deadline for my beta WU is 3 days. Why is my deadline so long when everyone else that posted WU details is showing a 1 day deadline? Result Name Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit BETA_ B200003955_ TrkB_ 0000_ 1-- In Progress 3/7/09 04:48:58 3/10/09 04:48:58 0.00 0.0 / 0.0 <-----mine BETA_ B200003955_ TrkB_ 0000_ 0-- In Progress 3/7/09 04:48:41 3/10/09 04:48:41 0.00 0.0 / 0.0 Sorry, it's a banana question; call it a forced ueber-hand to get some initial Beta back quickly. The first I received on the quad had 24 hours. The series of 7 received on the duo this morning, 12 hours after beta start, all have 3 days. Both run in high priority anyhow. No point in initially throwing many thousands of results into the beta queue and finding after the first few that it all crashes in large numbers and having to send cancel instructions to all the clients who talk to the server.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sek
----------------------------------------Could you please answer my above post Molte grazie JP [Edit 1 times, last edit by Former Member at Mar 7, 2009 9:59:34 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Still nothing What about this ; If enrolled in Beta and the machine asks for work, it checks first in the beta queue (if the beta feeder is activated by the techs I suppose). Thanks JP Don't know, call it 'Luck' or maybe you did not tick the Beta box for the correct device profile? If you did, all depends on the work generators and feeder timings and if a client contacts servers at 'Le moment suprême'.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What I did was exactly this ;
Tick the Beta box for the correct device profile ( default ) Supppose that is enough isn´t and no need to tick every profile. Those are with a tick for all Projects, etc etc |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Jean Pierre, how large is your work buffer?
|
||
|
|
hunterkasy
Senior Cruncher USA Joined: Dec 8, 2008 Post Count: 300 Status: Offline Project Badges:
|
I had to clear my work buffer in order to get beta's
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Logically, if the buffer is greater than the deadline, you should not be getting work for X or Y project. That's why machines with buffers over X days don't get the queue jumping rush/repair jobs.
----------------------------------------Now if that rule applies to Beta I'm not sure. At least I keep in Beta times a lowish queue. Flushing causes jobs to automatically be reissued at Does that make cents? Edit: Correction per below.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Mar 7, 2009 4:46:47 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sekerob, Kevin changed it to 33%, and up to 66% of the original deadline if the task is estimated to take longer than 33% of the original deadline. I imagine that initial tasks, having no previous work to estimate the time on, will be issued with 66% of the original deadline. This is consistent with the tasks I have looked at.
If the work buffer is too long, then beta tasks won't be sent. You will get other tasks, or see a message: Message from server: (won't finish in time) Computer on 99.7% of time, BOINC on 100.0% of that |
||
|
|
|