| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: CEP2 beta for windows - Version 6.25 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 311
|
|
| Author |
|
|
rainforest1155
Cruncher Joined: Mar 28, 2007 Post Count: 6 Status: Offline Project Badges: 
|
I have 4 beta WU right now and two are currently running. But the other two that aren't running are already showing in my task manager as a process even though in BOINC they show as "ready to start":
http://dl.dropbox.com/u/283274/sc2/20100915151103-00246x1503201015.jpg http://dl.dropbox.com/u/283274/sc2/20100915151141-00247x1541201015.jpg |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
rainforest1155, see reply above to piroque. 1 Task has 2 processes, 1 not using time.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
mwgiii
Advanced Cruncher United States Joined: Aug 17, 2006 Post Count: 131 Status: Offline Project Badges: 
|
Norton 360 quarantined the two tasks I had running as a virus during an automatic background virus scan.
----------------------------------------  [Edit 1 times, last edit by mwgiii at Sep 15, 2010 1:23:58 PM] |
||
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges: 
|
In Linux I see 3 or 4 processes but only ever one clocking time. One of them seeds the 16 jobs that a task is comprised of. similar to linux the time does not run beyond the segment. When a checkpoint is written a new process gets launched, that bit taking a portion of the efficiency out as observed by several. edit: as you see two of each, one having a constant PID and the other changing at checkpoint. Makes monitoring performance over the full task run difficult. Process Explorer only shows the data for the current job/segment. After 30 minutes, the utilization is leveling in the high 80s/low 90s. Still lower than normal, but better than 49%. |
||
|
|
rainforest1155
Cruncher Joined: Mar 28, 2007 Post Count: 6 Status: Offline Project Badges:
|
Yes, just figured that out myself when taking a closer look at the processes. Thanks for the quick reply! I scanned the thread before posting but couldn't find it mentioned.
|
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1405 Status: Offline Project Badges: 
|
I returned 4 BETA's:
----------------------------------------BETA_ E200361_ 244_ A.24.C18H12N4SSe.28.3.set1d06_ 1-- 918492 Pending Validation 15/09/10 06:30:29 15/09/10 13:30:17 6.23 92.2 / 0.0 BETA_ E200360_ 882_ A.24.C18H12N4S2.51.2.set1d06_ 0-- 1020031 Pending Validation 15/09/10 05:45:57 15/09/10 13:39:12 6.71 132.4 / 0.0 BETA_ E200360_ 854_ A.24.C18H12N4S2.46.4.set1d06_ 1-- 1020031 Pending Validation 15/09/10 05:42:34 15/09/10 13:10:20 6.06 119.7 / 0.0 BETA_ E200360_ 850_ A.24.C18H12N4S2.46.0.set1d06_ 1-- 1020031 Pending Validation 15/09/10 05:42:07 15/09/10 13:10:20 6.26 123.5 / 0.0 Upload files 22MB took 8 minutes on 45.4 KB/s Is seems that those tasks run faster on systems with a FSB of 1066 or 1333. [Edit 1 times, last edit by Crystal Pellet at Sep 15, 2010 1:57:30 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Download a couple of HPF2 jobs... that will pump it up. Download speed is highly affected by many short files which really never get to reach max speed, so by forcing a few jobs to come that are known to have bigger downloads, BOINC will adjust, temporarily. Mine is measured 266kB presently off from a recent mix of C4CW and HPF2. FYI, I downloaded beta's without issue. All of a sudden, this message started "9/15/2010 6:21:32 AM World Community Grid Message from server: The Clean Energy Project - Phase 2 requires 128.00 kbps download bandwidth. Your computer has been measured at 107.49 kbps. " I have tried your process, but it has not worked. I have a 52MB cable internet connection. This should not be an issue. Considering others are also having problems, I think it is boinc miss reading our systems. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
In Linux I see 3 or 4 processes but only ever one clocking time. One of them seeds the 16 jobs that a task is comprised of. similar to linux the time does not run beyond the segment. When a checkpoint is written a new process gets launched, that bit taking a portion of the efficiency out as observed by several. edit: as you see two of each, one having a constant PID and the other changing at checkpoint. Makes monitoring performance over the full task run difficult. Process Explorer only shows the data for the current job/segment. After 30 minutes, the utilization is leveling in the high 80s/low 90s. Still lower than normal, but better than 49%. Have to resign to the thought that my duo is not a racehorse. 82-83% after 6 hours. I'm now going to pause one and see if that betters the efficiency v.v. any resource and i/o competition wait states.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Rilian, I have the same problem, and my 4Mb ADSL link is not recognized as fast enough (probably due to the previous WU mix that was downloaded). What changes did you make to client_state.xml to get the Betas downloaded? I really need some help here please
|
|||
|
||||
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
NixChix, presume you meant the Progress percent... whilst typing slow and checking things, the Elapsed time counting started immediate, and after about 4.5 minutes the CPU time counter started too combined with little % progress steps. Did notice that during the model setup the system got slow responsive, so think that I will allow the 2 to run concurrent for a little and observe impact... . No, I did mean CPU time. My client (6.2.28) only has CPU time. CPU time stayed blank for much longer than I am used to. I didn't time it then, so I just started 2 beta WUs still in my queue. It took 2:00 for the first and 1:45 for the second before the CPU time started counting up. Perhaps it was the setup time as Sek stated, but I hadn't expected it not to be recorded as part of the CPU time. I also tested suspending and resuming. One job went from 1 hour 35 minutes back to 6 minutes. The second went back to 00:06:44 after being at 01:24:48. Ouch! Cheers   |
||
|
|
|