| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: New Beta starting Aug 5, 2011 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 94
|
|
| Author |
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
Did we transfer the time problem from Linux to Win7? Two hours into these two Beta's I see: Clock: 1:59 CPU: 1:43 Clock 2:01 CPU: 1:45 GPU's are not running. The last Beta there was only a few seconds difference.  Not here. 2 hours runtimes and a gap of less than 1 minute on the untouched Windows-machines and 3 minutes on Linux. Thanks for the info, CP.  I don't have anything to compare to as I only received 2 and they are both on the same machine. CPU shows only 85% use. Glad to see it seems not to be pervasive. |
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1452 Status: Offline Project Badges: 
|
got 1 on linux x64
---------------------------------------- |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Only 1 on the problematic Linux-box. Suspending OK. CPU last job included?? Other beta's on Windows XP32, Vista64 and W7-64. No problems so far. All results have 10 ZINC-targets each used for 4 tasks makes 40 jobs within 1 result. On Win-2.8GHz so far job duration varies from 107 seconds up to 713 seconds. Yup, that is the information that I will catch from the work units to help size and estimate work units. Thanks, -Uplinger |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges: 
|
Ubuntu 11.04 64-bit, BOINC 6.10.59 Finally it has speeded up after the first third:40 jobs per WU, thus checkpointing every 2.50 % ... Remains to check that the last job's CPU time is correctly accounted. But that will take about 4 hours. A little too long for a beta (for my taste).  Elapsed: 3:01:45 CPU time: 2:58:26 CPU time at checkpoint 39: 2:53:23. Things look good for me.  PS: Quad 6600 at 3 GHz |
||
|
|
pramo
Veteran Cruncher USA Joined: Dec 14, 2005 Post Count: 703 Status: Offline Project Badges:
|
Out of several, cpu vs elapsed time is from 40s to a minute and a half. others I've suspended.resumed with no problems,
----------------------------------------windows server 2003, xp, and 7(64bit)  |
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges:
|
1 minute difference in final CPU vs elapsed time out of 3 hrs 17 mins on AMD Phenom II (2.6 GHz) running Ubuntu 10.04.
----------------------------------------I've returned 2 betas, both PV; 4 more running on 3 different machines (all Linux). The one remaining thing I'm curious about with this batch is whether there is still a higher-than-normal proportion of inconclusives and invalids.  |
||
|
|
Bearcat
Master Cruncher USA Joined: Jan 6, 2007 Post Count: 2803 Status: Offline Project Badges:
|
I didn't receive any.
---------------------------------------- . Thought for sure my main cruncher that's connected 24/7 with .9 set for extras would get at least one. Running Ubuntu 64. What's the best settings to get betas? I seem to miss them most of the time. 
Crunching for humanity since 2007!
 |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges:
|
Finally it has speeded up after the first third: That's good, Jean. Not here. I've watched the CPU gradually sink to 69% and there is well over an hour between clock and CPU. I started both cards at MW and the 6 idle threads at Correlizer (BioMedical Genome Correlations) and the CPU sank to 65% (which I would expect starting the cards). These projects are running normally. I presume the Beta's will eventually complete. Not looking good here. |
||
|
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: 
|
I didn't receive any. . Thought for sure my main cruncher that's connected 24/7 with .9 set for extras would get at least one. Running Ubuntu 64. What's the best settings to get betas? I seem to miss them most of the time. Bearcat, How often does this system ask for work? Since the beta was so small, it may not have even ask for work during the beta or didn't ask too often. If you don't know, you can figure it out. Here is the information you need. How many cores are does that system have? What projects does the system crunch? How long does it normally take to complete these WU? Then you basically take the time to estimated time to complete the longest WU and divide it by how many cores the system have. If it is in the hours range, then it would be hard to get betas when only a small amount are release, unless you actively try or knew that betas were coming and changed your profile to only accept betas.  |
||
|
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
The one remaining thing I'm curious about with this batch is whether there is still a higher-than-normal proportion of inconclusives and invalids. Of 16 units: 4 pending, 2 valid, 1 inconclusive, 9 in progress. Not promising statistics so far, but too small of a sample to mean anything.  Distributed computing volunteer since September 27, 2000 |
||
|
|
|