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 |
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1670 Status: Offline Project Badges: |
I'd observed an interesting behavior:
----------------------------------------
Does exist a "protection mechanism" ? Cheers, Yves |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Yes, though you don't mention the BOINC version, once the client knows what the science app usage profile is, it will not try to start more than fit in what
----------------------------------------1) you've permitted BOINC to use 2) what's really available. Latter meaning that if you've specified 3GB RAM and 10 GB disk usage and X % Swap, but there only being 1GB Disk really free, only X% of that is considered. Similar there's the idle and use % on RAM. How to force this to try suspending all Ready to Start tasks except that BETA job, then suspending a running BETA task (LAIM ON else it unloads) which should launch the RtS BETA. Then suspend whatever science that 4th task is running concurrent. Some kind of notice should appear in the message log, but if all flags are disabled, there might not be. If still nothing happens, try switching LAIM OFF... you can loose a few hours work with that as the checkpoints CAN be far apart. BUT, though it might puzzle, accept it. These BETA jobs have a 5 day deadline if original and if in deadline threat, the client switches into EDF mode and reorgs. Note that on past clients the events could be that it will try a whole series of the RtS jobs to see if there's one that fits within the limits so the idle core is used, but that was only resulting in a visious circle of ever more jobs sitting in memory where they would stay until first checkpoint. Broadly, how it works, not necessarily to the dotted 'i' exact.
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All! |
||
|
X-Files 27
Senior Cruncher Canada Joined: May 21, 2007 Post Count: 391 Status: Offline Project Badges: |
Techs,
----------------------------------------Any news on the beta? Are we good for production or we'll have a 2nd round of beta? |
||
|
evilkats
Senior Cruncher USA Joined: May 4, 2007 Post Count: 162 Status: Offline Project Badges: |
I still have 2 repair WU crunching on 2 different hosts. It will be days before all repair jobs are returned by other members. I have not had any problems with this BETA, so I hope that this BETA run will be considered successful.
----------------------------------------[Edit 1 times, last edit by evilkats at Sep 21, 2010 1:53:27 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
[14:51:41] Starting job 12,CPU time has been restored to 9999.040096.
Application exited with RC = 0x1 [16:25:19] Finished Job #12 [16:25:19] Starting job 13,CPU time has been restored to 15506.343399. [16:25:19] Skipping Job #13 [16:25:19] Starting job 14,CPU time has been restored to 15506.343399. [16:25:19] Skipping Job #14 [16:25:19] Starting job 15,CPU time has been restored to 15506.343399. [16:25:19] Skipping Job #15 called boinc_finish [14:28:12] Starting job 15,CPU time has been restored to 22088.867994. Quit requested: Exiting [15:36:06] Number of jobs = 16 [15:36:06] Starting job 15,CPU time has been restored to 22088.867994. [17:00:13] Finished Job #15 called boinc_finish Can someone explain what happened in these instances: 1. Application exited with RC = 0x1 2. Quit requested: Exiting I saw each of these messages in multiple work units. |
||
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 200 Status: Offline Project Badges: |
How about these as an odd pair of stats:?
----------------------------------------BETA_ E200365_ 914_ A.24.C19H12N2OS2.146.0.set1d06_ 1-- 625 Valid 15/09/10 19:18:39 17/09/10 03:06:16 5.47 124.3 / 191.7 BETA_ E200365_ 914_ A.24.C19H12N2OS2.146.0.set1d06_ 0-- 625 Valid 15/09/10 19:18:37 17/09/10 16:28:26 12.00 48.6 / 36.0 |
||
|
anhhai
Veteran Cruncher Joined: Mar 22, 2005 Post Count: 839 Status: Offline Project Badges: |
JSYKES, if you look, you will see that the 2nd person finished the WU at 12 hrs, well not really finished but stopped. For this project the WU have a threshold of 12 hrs to do work, after 12 hrs it gets upload and verified. The WU that did more work is the on harvard cares about.
----------------------------------------Now since the 2nd person didn't really finished the WU, instead he did say 5 out of 15 jobs, while the 1st person finished the entire WU, you won't see the two getting the same amount of credits. However, the fact that the 1st person got 50% more credits then he asked for is kinda strange. |
||
|
boulmontjj
Senior Cruncher France Joined: Nov 17, 2004 Post Count: 317 Status: Offline Project Badges: |
Pretty good. Yesterday's stats proofed better than the 7850 I'd calculated to validate... Run Time (y:d:h:m:s) - Day 6:248:11:19:04 Meaning there are some 1800 still out there plus any repairs. You will get my 4 last Beta on monday before the dead line as there are running on one of my PC at work but without Internet connexion. I'll take them back home to send result on monday evening. |
||
|
Somervillejudson@netscape.net
Veteran Cruncher USA Joined: May 16, 2008 Post Count: 1065 Status: Offline Project Badges: |
8 work units and ran between 10 and 12 hours.
|
||
|
nasher
Veteran Cruncher USA Joined: Dec 2, 2005 Post Count: 1422 Status: Offline Project Badges: |
oh i am sure there will be straggler beta's for a few more days cause i am sure there will be some re sends... just hopeing whoever gets the re sends gets them back quick
---------------------------------------- |
||
|
|