| 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 2011/07/22 |
| No member browsing this thread |
|
Thread Status: Locked Total posts in this thread: 296
|
|
| Author |
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: 
|
These betas don't seem to like AMD processors, at least not my Phenom II X4 910e. Of 7 completed, 3 invalid, 2 valid, 2 PV. This machine has no issues with other sciences. No problems on my AMD's (Phenom I and Athlon II) 12 valids and 11 pending validation.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These betas don't seem to like AMD processors, at least not my Phenom II X4 910e. Of 7 completed, 3 invalid, 2 valid, 2 PV. This machine has no issues with other sciences. No problems on my AMD's (Phenom I and Athlon II) 12 valids and 11 pending validation. Similar problem on my X6: of 4 completed (and all four inconclusive) 2 invalid and 2 valid... besides this beta test it hasn't returned invalid jobs for months now. Still 6 betas to crunch on this machine, and hoping for the best. ;-) No problems yet on all other Intel computers. |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges:
|
I retested the suspend behaviour on Linux again between checkpoints 4 and 5.
----------------------------------------I created the situation that I had 2 tasks of another project running high priority and 1 BETA_BETA_ace80 "Waiting to run". The BETA wasn't waiting really. It crunched on together with the other 2 HP-tasks battling for CPU-time between 0 and 100%. This went on until the BETA reached his checkpoint at 62.5%. |
||
|
|
genes
Advanced Cruncher USA Joined: Jan 28, 2006 Post Count: 132 Status: Offline Project Badges: 
|
I had two units run on the Q6600:
----------------------------------------BETA_ BETA_ ace80_ 0000000_ 3121_ 1-- and BETA_ BETA_ ace80_ 0000000_ 4931_ 1-- Both finished without incident in about 4.9 hours, 3121 has validated, 4931 is waiting for a wingman to finish. I checked the reported CPU times against what was measured for each step, and they add up properly. Couldn't check the elapsed time, since the units ran while I was away. [Edit 1 times, last edit by genes at Jul 30, 2011 11:55:39 AM] |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
From the 48 BETA_ BETA’s that came my way I only saw 8 on my Ubuntu system :(
No Errors, Inconclusive’s or Invalids on any other system, so far, but one Inconclusive and one Invalid on my Ubuntu system. This Inconclusive first checkpointed at 21min on an i7-2600K, but some checkpoints were at about 6min, explaining the general runtime variety: <core_client_version>6.10.59</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [08:19:10] Number of tasks = 8 [08:19:10] Starting job 0,CPU time is 0.000000. [08:19:10] ZINC04733788.pdbqt size = 35 6 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [08:41:17] Finished Job #0 cpu time used 1322.470000 [08:41:17] Starting job 1,CPU time is 1322.470000. [08:41:17] ZINC04733788.pdbqt size = 35 6 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:03:31] Finished Job #1 cpu time used 1331.060000 [09:03:31] Starting job 2,CPU time is 2653.530000. [09:03:31] ZINC04733788.pdbqt size = 35 6 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:25:34] Finished Job #2 cpu time used 1319.810000 [09:25:34] Starting job 3,CPU time is 3973.340000. [09:25:34] ZINC04733788.pdbqt size = 35 6 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:47:28] Finished Job #3 cpu time used 1310.990000 [09:47:28] Starting job 4,CPU time is 5284.330000. [09:47:28] ZINC04750576.pdbqt size = 24 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:54:42] Finished Job #4 cpu time used 432.260000 [09:54:42] Starting job 5,CPU time is 5716.590000. [09:54:42] ZINC04750576.pdbqt size = 24 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [10:00:35] Finished Job #5 cpu time used 351.930000 [10:00:35] Starting job 6,CPU time is 6068.520000. [10:00:35] ZINC04750576.pdbqt size = 24 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [10:06:53] Finished Job #6 cpu time used 376.680000 [10:06:53] Starting job 7,CPU time is 6445.200000. [10:06:53] ZINC04750576.pdbqt size = 24 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [10:12:33] Finished Job #7 cpu time used 339.060000 10:12:33 (28959): called boinc_finish </stderr_txt> ]]> Project Name: Beta Test Created: 07/29/2011 18:54:05 Name: BETA_BETA_ace80_0000000_3926 Minimum Quorum: 2 Replication: 3 Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit BETA_ BETA_ ace80_ 0000000_ 3926_ 2-- 612 Valid 30/07/11 08:47:33 30/07/11 11:05:13 2.04 43.8 / 42.7 BETA_ BETA_ ace80_ 0000000_ 3926_ 1-- 612 Invalid 29/07/11 21:42:11 30/07/11 08:46:48 1.15 44.7 / 42.7 BETA_ BETA_ ace80_ 0000000_ 3926_ 0-- 612 Valid 29/07/11 21:42:10 30/07/11 01:03:42 2.46 41.7 / 42.7 Result Log Result Name: BETA_ BETA_ ace80_ 0000000_ 3926_ 1-- <core_client_version>6.10.59</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [08:28:54] Number of tasks = 8 [08:28:54] Starting job 0,CPU time is 0.000000. [08:28:54] ZINC04744273.pdbqt size = 28 4 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [08:40:04] Finished Job #0 cpu time used 666.440000 [08:40:04] Starting job 1,CPU time is 666.440000. [08:40:04] ZINC04744273.pdbqt size = 28 4 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [08:51:12] Finished Job #1 cpu time used 665.880000 [08:51:12] Starting job 2,CPU time is 1332.320000. [08:51:12] ZINC04744273.pdbqt size = 28 4 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:02:29] Finished Job #2 cpu time used 674.670000 [09:02:29] Starting job 3,CPU time is 2006.990000. [09:02:29] ZINC04744273.pdbqt size = 28 4 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:13:41] Finished Job #3 cpu time used 667.180000 [09:13:41] Starting job 4,CPU time is 2674.170000. [09:13:41] ZINC04939896.pdbqt size = 27 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:21:44] Finished Job #4 cpu time used 480.760000 [09:21:44] Starting job 5,CPU time is 3154.930000. [09:21:44] ZINC04939896.pdbqt size = 27 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:29:45] Finished Job #5 cpu time used 478.840000 [09:29:45] Starting job 6,CPU time is 3633.770000. [09:29:45] ZINC04939896.pdbqt size = 27 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:37:43] Finished Job #6 cpu time used 476.270000 [09:37:43] Starting job 7,CPU time is 4110.040000. [09:37:43] ZINC04939896.pdbqt size = 27 3 ../../projects/www.worldcommunitygrid.org/beta13.target_ace.pdbqt size = 4660 0 [09:45:43] Finished Job #7 cpu time used 477.560000 09:45:43 (28971): called boinc_finish </stderr_txt> ]]> |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges: 
|
I checked the reported CPU times against what was measured for each step, and they add up properly. genes,Haven't you forgotten the CPU time of the last job (job #7 for an ace80 beta WU)? When I compare the CPU times shown in the Result Status page against what is reported in the Result Log of each WU it matches the CPU time at the start of the last job, not that time plus the CPU time of the last job as it should.  ---------------------------------------- [Edit 1 times, last edit by JmBoullier at Jul 30, 2011 1:38:50 PM] |
||
|
|
Jason1478963
Senior Cruncher United States Joined: Sep 18, 2005 Post Count: 295 Status: Offline Project Badges:
|
I seem to have had better luck with windows machines running these. The Ubuntu machines I'm running seemed to have efficiency issues according to BOINC view. This could be related to the work units not responding to BOINC manager. They also seem to be coming up invalid or inconclusive with a few valid even on stock CPU settings.
---------------------------------------- |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
Are there any more betas coming or are we done for now?
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
Especially now in this beta there most (all?) problems seems to be OS-specific, I'll include the very important info about OS at the start:
----------------------------------------OS: win2008-R2 BOINC v6.12.33 cpu: i7-920 at 2.67 GHz. I checked the reported CPU times against what was measured for each step, and they add up properly. I've only finished 5 tasks on same computer, with efficiencies between 96.8% - 99.0%, something that's completely normal for this computer since example the 243 DDDT2 in last rain was 73.0% - 99.0% with average 95.6%. Looking more closely on the log on the other hand, revealed a small disrepancy between the log and the reported cpu-time. The disrepancy varied between 0.03 s and 0.86 s for these 5 tasks, so it's really insignificant. Still, since there is a disrepancy, it seems it doesn't correctly report-back the final cpu-time, so instead the last report of cpu-time that happens once per second is used instead as the final. If this small bug isn't fixed, on average there'll be a disrepancy of 0.5 seconds per task. As for other info that can be interesting, the shortest time between checkpoint was 19 minutes, longest 65 minutes. Smallest variation between checkpoints for a single task was 1.31x, longest was 2.23x. Couldn't check the elapsed time, since the units ran while I was away. As long as your BOINC-client is v6.6.xx or later, info about elapsed time, cpu-time and some other things for all non-erroring WCG-tasks is saved in job_log_www.worldcommunitygrid.org.txt, located in your BOINC data-directory.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
Iâm not sure what is going on. Somehow I thought we were going to get the 4 different batches we had in the previous test (ace80, tk, etc.) but all I saw was ace80. Apparently LINUX has some problems. There will be retesting I am certain but I hope they clue us into the âplanâ.
----------------------------------------The only errors I had were 4 wuâs that errored when one of my machines BSODâed. It appears to be fatal as it is now unstable. I keep getting the âWindows has recovered from an unexpected problemâ message and then a blue screen memory dump. I suppose this is to distinguish from expected Windows problems.  I saw some rather high temps yesterday as the processors ran in the 99.95% range. I hope it is not a memory failure as I hate having to test it one stick at a time. It will have to wait to next week as "she who must be obeyed" has other plans for me this weekend.   [Edit 1 times, last edit by Dataman at Jul 30, 2011 3:26:24 PM] |
||
|
|
|