| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: new CEP2 beta started |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 32
|
|
| Author |
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges: 
|
Eventhough on first appearances, only 1 WU/2 cores seemed to be possible, I'm thinking that this isn't now the case - as I've just had these two lines come up in my messages log;
----------------------------------------22/09/2010 01:34:24|World Community Grid|Message from server: No work sent 22/09/2010 01:34:24|World Community Grid|Message from server: Beta - The Clean Energy Project - Phase 2 requires 128.00 kbps download bandwidth. Your computer has been measured at 126.89 kbps. Yes, I know how to "modify" my system to allow it to get past that check - although the 2 Beta WU's that I've currently got, last checkpointed some 2+ hrs ago...  |
||
|
|
nasher
Veteran Cruncher USA Joined: Dec 2, 2005 Post Count: 1422 Status: Offline Project Badges: 
|
heck its a beta i dont care if i only get 1 per system or whatever i am happy to get any
---------------------------------------- |
||
|
|
codes
Advanced Cruncher Joined: Oct 20, 2009 Post Count: 142 Status: Offline |
We have started another 5000 workunits for this beta test. However, we have changed it so that each user can only have n/2 cores in use for this beta test. I've gotten 1 so far. "Please sir, may I have some more."  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Wouldn't it be useful to adopt this n/2 cores feature for production? No manual check for too many CEP2 WUs running concurrently would be necessary anymore!
|
||
|
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: 
|
Wouldn't it be useful to adopt this n/2 cores feature for production? No manual check for too many CEP2 WUs running concurrently would be necessary anymore! Nah, most of use have some cache. So we want to have more then n/2 cores worth of CEP2 WU. However, I personally would only want a few to run at the same time. Once it goes into production, I won't race to get the badge, I will let WCG set how many I do, but I will check to prevent too many being done at once (maybe even limit to 3 at a time (out of 16 cores)).  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Wouldn't it be useful to adopt this n/2 cores feature for production? No manual check for too many CEP2 WUs running concurrently would be necessary anymore! Nah, most of use have some cache. So we want to have more then n/2 cores worth of CEP2 WU. However, I personally would only want a few to run at the same time. Once it goes into production, I won't race to get the badge, I will let WCG set how many I do, but I will check to prevent too many being done at once (maybe even limit to 3 at a time (out of 16 cores)). Why do you want to have enough CEP2 WUs in cache if you want to limit the number of running WUs manually? :-) I have a cache setting of 0,1%, so it makes no difference for me. But it could save me time if I don't have to look for too many running CEP2 WUs. But I admit that all badge hunters wouldn't be too happy with it... ;-) |
||
|
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges:
|
I have cache set at 1 day, I also have all 7 projects selected, and combine with the fact that I doubt that CEP2 WU will be highly weighted (especially since the WU take longer to process then others) it will be unlikely that more then 3 or 4 will be run at the same time. I just have to check once a day or so to make sure it doesn't become overloaded. For the betas, I have 5 or 6 running at the same time without too much problem.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I know it may sound silly but maybe they want to see if limiting the number of concurrently running CEP jobs will help with some of the problems detected in first beta................ i know testing software with beta releases, just plain silly .................
|
||
|
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges:
|
fredski, it was mention in another thread that they are trying to figure out why some WU die soon after starting. Limiting the number of concurrently running CEP2 WU would reduce the memory constraints and that is what they believe is the cause of the problem
---------------------------------------- |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
fredski, you are warmest I think. I've been running CEP2 from start on Linux and found the efficiency substantially better if suspending anything more than 2 concurrent on the quad, so I run Water/CEP2 mix, with a little micromanaging. Received one of these beta's whilst ashleep and it has only a 12 minute gap after 5:58 hours between elapsed and cpu time... and that's on my crawling duo laptop. If such a feature would be automated to never allow a client to have more than n / 2 cores, it would though have adverse effects for reporting will take longer, so a fetch call would be delayed, plus they'd be sitting in back of queue, which then is promoted to be short and frankly don't know how to force backfill but to set CEP2 only... very counter productive to those that come to WCG purely for CEP2. No, the client needs to learn the opti trick, and talk of development in that direction is underway... a kind of "optimize efficiency" discussed on WCG forums too.
----------------------------------------PS, this is still version 6.25, so I've added that to the post title!
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|