| 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 Started Jan 30, 2012 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 206
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Highest VM seen so far after 2:15 hours is 38MB and Working RAM 40MB. Complying to Checkpoint-Write to Disk settings.
--//-- |
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
Here are results from the first set of 4 run on my Phenom II X4 910e:
----------------------------------------BETA_ SN2S_ AAB22884_ 0000001_ 0546_ 0-- kate-amd64 Pending Validation 2/9/12 03:29:59 2/9/12 08:50:58 5.29 140.6 / 0.0 BETA_ SN2S_ AAB22884_ 0000001_ 0323_ 1-- kate-amd64 Valid 2/9/12 03:29:59 2/9/12 08:50:14 5.28 140.4 / 107.4 BETA_ SN2S_ AAB22884_ 0000001_ 0498_ 0-- kate-amd64 Pending Validation 2/9/12 02:51:55 2/9/12 08:44:57 5.68 151.1 / 0.0 BETA_ SN2S_ AAB22884_ 0000001_ 0431_ 1-- kate-amd64 Pending Validation 2/9/12 03:29:24 2/9/12 08:33:56 4.98 132.6 / 0.0 It looks as if run times will be about 10-11 hrs on AMD E-350 Zacate and 25-27 hrs on Intel Atom. Virtual memory is between 23 MB and 27 MB and working memory between 21 nd 24 MB on the running WUs I just looked at. For example, I'm running 4 Betas + a PrimeGrid GPU WU on an Atom with just 1.5 GB of RAM (the rest dedicated to the ION), and there's a little RAM unused.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BETA_ SN2S_ AAB68717_ 0000000_ 0107_ 1 5.28 hours 44 tasks
BETA_ SN2S_ AAB68717_ 0000000_ 0157_ 0 5.27 hours 48 tasks BETA_ SN2S_ AAB68717_ 0000000_ 0697_ 1 4.94 hours 84 tasks Interesting! |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
I saw no problems on this run. I have not seen any in 6+ hours, are we finished except for resends?
----------------------------------------  |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges:
|
I have seen a few intervals between checkpoints to exceed 30 mins - with one (there may have been more) going over 75 mins. This may cause an issue or two for those who've got slower machines...
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Agree, but what is the solution when we know that intermediate saving, in the middle of a fold or docking, is prohibitive in the amount of data that needs saving, risking user impacting? [not to speak of cases that resetups on resume brings possible result variations with it and quorum problems]. Same as with GFAM/DSFL, the techs are learning how many of the ligands to put in a job for them to run fairly regular durations [which are then having a variable number of jobs content in the package]. Beyond that, we'll have to just make sure volunteers understand and educate as best as possible... hibernation instead of power down, reading checkpoint progress [using <checkpoint_debug> logging for best opportune moment, mainly directed at those who run their devices part time et cetera.
In a long distant future the system will be fitted with a skill to assign the heavies to the heavies and the lights to the lights, but opposed to a certain smartphone available today, this smart assignment future ain't here yet. --//-- |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges:
|
Obviously, when all the results are 'back at base', the techs should (I would have thought), be able to work out what the percentage of 'long checkpoint intervals' is and be able to weigh-up as to whether it'll really be an issue or not...
----------------------------------------Personally, I'm not too bothered about long intervals between checkpoints, but others might be... Edit: For reference, the WU which I'm seeing long checkpoint intervals, is BETA_SN2S_AAB22884_0000001_0780_1-- So far, it's been processing for 13:32:11, with an elapsed time of 13:58:51 and is at 55.357%, with another 10:16:59 estimated time to complete. At the moment, there have been 15 checkpoints in this run... [Edit 2 times, last edit by gb009761 at Feb 9, 2012 4:51:25 PM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Any more betas coming?
----------------------------------------
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.
  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Had 85 hours completed this round where needing 83.5 to reach Ruby... took ''just'' 6.5 years of BOINCing.
 The test itself was straight forward... Pretty much identical to GFAM/DSFL, cept where the prediction was for larger memory use, these ran considerably slimmer than the other 2 VINA sciences in production... slightly less efficient. On Linux was used to seeing 99.2% for the VINA's, where these Betas were in the 98.4-98.6%. not biggy, but 99+ is the bar.  --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It looks as if run times will be about 10-11 hrs on AMD E-350 Zacate and 25-27 hrs on Intel Atom. Virtual memory is between 23 MB and 27 MB and working memory between 21 nd 24 MB on the running WUs I just looked at. Runtime on all of my machines so far (P3/1.4, P4/2.0 and P4/2.6HT) have been around 12 hours, which is a nice size. Memory usage <28 MB. |
||
|
|
|