Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: New Set of Beta WU's - FAAH |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 484
|
Author |
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
Change the setting for number of CEP work units to greater than one, this will override the download speed check. Yes, even for Beta as it has been using the same setting for the CEP betas.
----------------------------------------Distributed computing volunteer since September 27, 2000 |
||
|
RyanChen
Cruncher Taiwan Joined: Jun 12, 2009 Post Count: 14 Status: Offline Project Badges: |
Change the setting for number of CEP work units to greater than one, this will override the download speed check. Yes, even for Beta as it has been using the same setting for the CEP betas. Thanks for your suggestion. But my profile setting is 8 and concurrently have 8 normal CEP2 wus in the cache. Is it the reason why I didn't get beta CEP2 cause the beta and normal CEP2 wus number count together? |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
A Shrubbery,
Not sure what's going on in there, but check your allowed BW settings in the preferences too. Maybe the override is not overriding all the way down to trickle and BOINC had a momentary lapse of reason which [many small files or enduring slow download on the qcaux files] causing the value to go below some secondary trigger??? Stopping BOINC and editing the client_state.xml [to be done with extreme care] allows for restoring the value to a more sane number. --//-- |
||
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: |
Thanks for your suggestion. Very likely!But my profile setting is 8 and concurrently have 8 normal CEP2 wus in the cache. Is it the reason why I didn't get beta CEP2 cause the beta and normal CEP2 wus number count together? It looks like the CEP-setting is even overriding the default beta setting of only 1 beta/host or at most 1 beta/core. See SekeRob who got 16 BETA-CEPs on 1 quad. Me too and on a single core machine I got 15 of them. Fortunately they are reduced to 2 hours runtime. |
||
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: |
It makes sense to apply the CEP2 options to CEP2 beta tests; there would be little point in running a CEP2 Beta on a system that gets switched off and on a lot, has little RAM, low bandwidth or does not use LAIM. There are plenty of people out there that have many-thread CPU's but are using Win x86 (with it's 3 to 3.5GB RAM limitation), so with 8 threads, and limited RAM we need to be able to control what we crunch, including Beta's.
Those with single cores that can select 16 tasks are lucky, for now; I can see this being changed at some stage. Just remember that if the tasks are much longer (say 12h on an average CPU) and the cutoff time is only a few days, Boinc will calculate that you won't be able to finish in time, and you won't. So don't expect 16 long CEP2 tasks with short deadlines, especially with a mix of other Betas. Picked up another 5 CEP2 Betas around 2.10 to 2.30 last night (UK here). On 4 different system too. These did not seem to jump to the top of the queue. On one system Boinc wanted to run normal CEP2 tasks due on the 22nd rather than the Beta due on the 16th. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"They did not seem to jump..." either they did or did not. Not sure how you can expect for a Beta with 4 days deadline (all 16 of mine had that) with standard client settings to be moved ahead of other tasks with 10 days deadline. Switch time assumed to be default 60 minutes and IIRC you running with small cache, there's no reason for the client to reschedule and continue on with FIFO [per active project]. Not even my 2 day deadline Beta's of previous last test did so with a 1 day cache setting.
--//-- |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not a drama with the 1 day cache pumped to 2 on the beta profile. The DCF will be shot for a little, but upon stocking fully, flipped profile back to the regular with 1 days as to prevent excess. And yes, they show to head for 2 hours after 20 minutes. --//-- I've got two of these CEP2 Beta jobs running now as well. They started out estimated at between 9 and 10 hours, but now they're down to 4 hours. (and they dropped another 20 minutes in the 2 or 3 minutes it took me to write this post) The 9-10 hour estimation seemed off to me to begin with, most of the CEP2 jobs I get are estimated at 8:43:21. |
||
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: |
Whoever is waiting for this task to validate might be waiting a while,
BETA_ E202697_ 603_ C.27.C22H12N4S.00241403.2.set1d06-- 201107120059210_ 1 Had to scavenge the system for parts (heatsink). Didn't know it had a beta Of course a lengthy wave of Betas might entice me to replace it ~~~ |
||
|
mfbabb2
Senior Cruncher USA Joined: Feb 18, 2011 Post Count: 361 Status: Offline Project Badges: |
There is supposed to be a wave of new Betas coming any time now <fingers crossed>.
----------------------------------------
Murphy
|
||
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: |
In about 30 minutes we will release one beta batch for each of the following projects simultaneously:
|
||
|
|