| 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 Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 152
|
|
| Author |
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: 
|
BETA Test 7.21
----------------------------------------9999979 & 9999985 still restart after 3 mins, even after a reinstall of SW. Win7SP1 64bit & BOINC 6.10.58 Upgraded to BOINC 7.0.64 (x64) still get same problem, of WU restarting after 3 mins. Patrick  [Edit 3 times, last edit by pcwr at Nov 4, 2013 9:36:27 PM] |
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
I just got some. I have 1 job that seems to be stuck at the 9 second point, even though the task has been running for 20 minutes.
----------------------------------------Mars World Community Grid 7.21 Beta Test BETA_BETA_9999984_0315a_1 00:19:00 (00:00:09) 0.8% 0.50% 09:37:58 01d,23:38:39 Running [0] 00:00:09 11/4/2013 10:50:14 AM While I was writing this it seems to have just restarted, or something. The task runing time started over, while the CPU time has started accumulating. Mars World Community Grid 7.21 Beta Test BETA_BETA_9999984_0315a_1 00:03:55 (00:03:53) 99.36% 3.38% 08:22:10 01d,23:33:45 Running [0] 00:03:53 11/4/2013 10:50:14 AM Should I just kill this job or let it run? cheers   [Edit 1 times, last edit by NixChix at Nov 4, 2013 7:22:02 PM] |
||
|
|
themoonscrescent
Veteran Cruncher UK Joined: Jul 1, 2006 Post Count: 1320 Status: Offline Project Badges: 
|
Every Beta on 1 system has Errored out, most showing 51 minuets Elapsed Time / 27 minuets CPU Time... With "Maximum elapsed time exceeded" message?
----------------------------------------System: I7-3770k / 16gb Ram / Win7 Pro 64bit (a different system to ones mentioned previously). Every Beta on a 2nd System have all errored out as well, 3rd and 4th system look like they'll be going the same way.   [Edit 2 times, last edit by themoonscrescent at Nov 4, 2013 7:46:21 PM] |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
We have modified the limits for max allowed time. Due to the very short jobs that returned quickly (and before longer jobs were returned), BOINC determined that our estimated time was way too long and adjusted its estimate. As a result, the peak runtime for jobs was shortened as well. We have increased the max runtime by a factor of 10 which stop this error for newly issued jobs. This does indicate that at launch we will need to allow a very large range until we reach a steady state of long and short jobs being returned.
|
||
|
|
genhos
Veteran Cruncher UK Joined: Apr 26, 2009 Post Count: 1103 Status: Offline Project Badges: 
|
Got to 1hour 5mins with 17% done, restarted the client it the went back to 0.5% with 1hour elapsed (this time is connected to the localhost on the first restart attempt but I did leave it off for a minute before restarting the client, perhaps previous attempts were too quick after exiting the client?). It then got to 1hour 10mins elapsed before the progress updated from 0.5% to 14%.
----------------------------------------So when I restarted the client it loses the progress % and goes back to 0.5 but elapsed time seems correct for how long the unit has been crunched and then takes around 10minutes at 0.5% before it "catches up" with the correct progress %age. @herna - indeed it is odd and I've not seen any previous restart of the client do this. If I suspend the unit then it restarts from exactly where it left off as LAIM is on. The issue is if I close the whole BOINC client and then load it back up as it does when the computer starts up. |
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges:
|
A check of my other 2 systems shows that the latest beta jobs are using up CPU time, but appear to not be getting anywhere.
----------------------------------------Mars 7.21 Beta Test BETA_BETA_9999981_0913_0 00:39:50 (00:15:33) 39.0 0.50 10:19:20 01d,22:19:34 Running [1] 00:04:55 11/4/2013 9:54:00 AM Mars 7.21 Beta Test BETA_BETA_9999984_0326a_0 00:39:29 (00:15:09) 38.3 6.28 08:43:12 01d,23:15:47 Running [1] 00:04:19 11/4/2013 10:50:14 AM Mars 7.21 Beta Test BETA_BETA_9999984_0315a_1 00:21:53 (00:21:40) 99.01 20.73 05:04:18 01d,23:15:47 Running [1] 00:08:59 11/4/2013 10:50:14 AM Mars 7.21 Beta Test BETA_BETA_9999984_0039a_1 00:33:55 (00:09:37) 28.3 0.50 10:07:34 01d,23:19:13 Running [0] 00:09:37 11/4/2013 10:53:40 AM The Vault 7.21 Beta Test BETA_BETA_9999984_0869a_0 00:32:09 (00:29:34) 91.98 5.35 18:02:32 01d,23:18:25 Running High P. [3] 00:01:40 11/4/2013 10:52:53 AM The Vault 7.21 Beta Test BETA_BETA_9999985_0239a_1 00:35:09 (00:00:08) 0.4 2.91 19:31:45 01d,23:24:38 Running High P. [0] 00:00:08 11/4/2013 10:59:05 AM Venus 4 7.21 Beta Test BETA_BETA_9999983_0134_1 00:37:53 (00:33:18) 87.89 8.88 13:35:28 01d,22:59:37 Running High P. [3] 00:06:29 11/4/2013 10:33:55 AM Venus 4 7.21 Beta Test BETA_BETA_9999984_0967a_0 00:40:52 (00:00:06) 0.2 4.13 15:49:47 01d,23:18:53 Running [0] 00:00:06 11/4/2013 10:53:11 AM I just happen to be home at the moment, but I'll be leaving for work in 30 minutes. I'll just leave them running until I come back. Cheers [Edit 1 times, last edit by NixChix at Nov 4, 2013 7:40:20 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We have modified the limits for max allowed time. Due to the very short jobs that returned quickly (and before longer jobs were returned), BOINC determined that our estimated time was way too long and adjusted its estimate. As a result, the peak runtime for jobs was shortened as well. We have increased the max runtime by a factor of 10 which stop this error for newly issued jobs. This does indicate that at launch we will need to allow a very large range until we reach a steady state of long and short jobs being returned. Never would I have thought the BETA system had time enough to adjust the FPOPS for newly distributed work... thought all would have been build and locked before circulation. With this, you may have put your finger an the cause (as was qualified) 'repulsive' points problem [crap credit]. Last beta had a range of 6 to 71 per hours on the same device, no kidding... barely a dozen processed on that machine. To repeat the repeated: Credit New is 'incapable' of handling variable runtime properly [Have a look at CEP2 for a demonstration over the last few weeks]. A random number generator does a better job, at least if you run one 1000 times, you get a fairly even distribution. Edit: Ha Ha Ha, I take the 6 to 71 back and make it 4-71 per hour, for a device that in a period of stable runtime does about 35. BETA_ BETA_ 9999979_ 0493_ 1-- 2524499 Valid 11-04-13 21:27 04-11-13 20:10:56 2,95 16,1 12,6 2,96 4,27 < per hour How to stimulate cherry picking, or voting with feet. [Edit 2 times, last edit by Former Member at Nov 4, 2013 8:40:00 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Summing up:
- 2 Betas on Linux native installation: running fine, apart from a little inefficient. - 4 Betas on Win32 native installation: get stuck after a while, CPU time not changing, Task Mgr shows 100%. Maybe they got stuck when more RAM is used (opening browser), not sure. Tasks keep running after suspending, only halt when LAIM turned off as well. - 4 Betas on the same Win machine (while suspending Win CPU wus) running inside a Linux VM: no problems. |
||
|
|
genhos
Veteran Cruncher UK Joined: Apr 26, 2009 Post Count: 1103 Status: Offline Project Badges:
|
My "beloved" 9999980_0583_1 now seems to be stuck at 16.859%. It's been there for over 30minutes, elapsed time is still going up and the To Complete time is also just continually heading upwards. Task manager shows it is using 100% of its core.
----------------------------------------Another beta has completed in 24mins, this one seemed to just from around 10% to 100% reaching pass 471. |
||
|
|
slakin
Advanced Cruncher Joined: Jul 4, 2008 Post Count: 79 Status: Offline Project Badges: 
|
I just had my first of this batch that appeared to finish successfully, still waiting on wingman verification ..unfortunately it blew the completion times for all my regular task to pieces ..normally they take about 1 hours now some as high as 64 hours average around 44 hours..so I won't likely get any more BETA jobs, at least for awhile.
|
||
|
|
|