World Community Grid - View Thread - New Project Beta test v6.05 Issues Thread

World Community Grid Forums

Category: Beta Testing

Forum: Beta Test Support Forum

Thread: New Project Beta test v6.05 Issues Thread

Quick Go »

No member browsing this thread

Thread Status: Active
Total posts in this thread: 62

[ ]

Author

This topic has been viewed 13650 times and has 61 replies

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: New Project Beta test v6.05 Issues Thread

14 returned and validated except 1 which is waiting on the wingman of course.

[Apr 13, 2012 11:48:12 AM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: New Project Beta test v6.05 Issues Thread

Got 10, all returned: 5 valid and 5 PV

i7 2600k @ 3.40Ghz:

BETA_ cfsw_ 0005_ 00005177_ 1--  605 Pending Validation 12/04/12 19:42:51 13/04/12 01:07:58  3,56 108,5 / 0,0 
BETA_ cfsw_ 0002_ 00002626_ 1--  605 Valid  12/04/12 17:59:46 12/04/12 23:15:05  3,55 117,3 / 105,3 
BETA_ cfsw_ 0001_ 00001434_ 1--  605 Valid  12/04/12 16:53:51 12/04/12 21:31:38  3,58 118,7 / 93,3 
BETA_ cfsw_ 0001_ 00001955_ 0--  605 Valid  12/04/12 16:51:10 12/04/12 21:56:34  3,58 129,8 / 108,0 
BETA_ cfsw_ 0001_ 00001547_ 1--  605 Valid  12/04/12 16:49:01 12/04/12 21:18:08  3,65 116,8 / 132,1 
BETA_ cfsw_ 0001_ 00001328_ 1--  605 Pending Validation  12/04/12 16:48:43 12/04/12 20:48:45  3,58 104,3 / 0,0 
BETA_ cfsw_ 0001_ 00001326_ 1--  605 Valid  12/04/12 16:48:24 12/04/12 21:56:34  3,57 132,1 / 117,7 
BETA_ cfsw_ 0001_ 00001681_ 1--  605 Pending Validation  12/04/12 16:38:17 12/04/12 21:56:34  3,60 132,0 / 0,0

Core 2 Duo @ 2.00Ghz:

BETA_ cfsw_ 0001_ 00001614_ 1--  605 Pending Validation  12/04/12 16:36:09 12/04/12 21:58:28  5,22 82,5 / 0,0 
BETA_ cfsw_ 0001_ 00001429_ 0--  605 Pending Validation  12/04/12 16:35:50 12/04/12 21:59:06  5,23 82,7 / 0,0

----------------------------------------
[Edit 1 times, last edit by Former Member at Apr 13, 2012 12:28:33 PM]

[Apr 13, 2012 12:27:43 PM]

BSD
Senior Cruncher
Joined: Apr 27, 2011
Post Count: 224
Status: Offline


Re: New Project Beta test v6.05 Issues Thread

I got 4, don't know if they are running properly. BOINC is set to use 100% CPU and all 4 tasks are similar to this:

CPU time: 00:00:19
Elapse time: 01:08:09
Fraction done: 0.000%

CPU Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz quad core with H/T on
4 GB RAM with 71% physical utilized
Hard drive is not thrashing

Guess these WUs are just slow at the start.

p.s. I did have TTrottle running and it was set to 100% CPU. I killed that app, maybe it was throttling incorrectly?

Edit: Other tasks have CPU and Elapse time close to each other, running with H/T on.

These completed successfully with similar times.

CPU time: 05:22:52
Elapse time: 06:30:30

Must of been the TTrottle slowing them down - erroneous isolated problem. blushing

[Apr 13, 2012 12:30:37 PM]

pramo
Veteran Cruncher
USA
Joined: Dec 14, 2005
Post Count: 703
Status: Offline
Project Badges:

20 year badge for Human Proteome Folding - Phase 2

14 day badge for Help Cure Muscular Dystrophy

45 day badge for Discovering Dengue Drugs - Together

2 year badge for Nutritious Rice for the World

14 day badge for The Clean Energy Project

20 year badge for Help Fight Childhood Cancer

180 day badge for Influenza Antiviral Drug Search

10 year badge for Help Cure Muscular Dystrophy - Phase 2

5 year badge for Discovering Dengue Drugs - Together - Phase 2

50 year badge for The Clean Energy Project - Phase 2

10 year badge for Computing for Clean Water

20 year badge for Drug Search for Leishmaniasis

10 year badge for GO Fight Against Malaria

10 year badge for Computing for Sustainable Water

100 year badge for Mapping Cancer Markers

50 year badge for Uncovering Genome Mysteries

50 year badge for Outsmart Ebola Together

20 year badge for FightAIDS@Home - Phase 2

10 year badge for Microbiome Immunity Project

5 year badge for Africa Rainfall Project

10 year badge for OpenPandemics - COVID-19


Re: New Project Beta test v6.05 Issues Thread

not quoting Ingleside's post because it's a mouse roll away, but I have a machine with 24 cores and it was full up before returning the first result. First betas for this app/project (though it did return 5 on April 3rd).

----------------------------------------

[Apr 13, 2012 12:31:37 PM]

KWSN - A Shrubbery
Master Cruncher
Joined: Jan 8, 2006
Post Count: 1585
Status: Offline


Re: New Project Beta test v6.05 Issues Thread

Shrubbery isn't right with his suggestion. I can speak out of experience.
The limit is 1 BETA per core and it doesn't matter whether returned tasks are validated or not.

Actually, there's 2 limits, it's the "good old" 1 BETA per core, there you in theory can get a new beta every time you finish an old beta.

But, you've also got the new limit of a daily quota per application per computer per core, and atleast for other WCG-applications this start at 2 but possibly the beta-application is limited to 1. Since it's per application, every time there's a new beta-application, the quota for the application starts with the default quota.

Since the quota only increases on validation, you can return 1 beta-result but not get any more beta's, due to no beta with the new application have been validated yet.

Now, as long as we're only talking of beta, in practice the supply << demand so chances are the only messages most will see is "no work available" and "there was work for other platform". So the quota starting on 2 or possibly 1 doesn't really matter.

Then the project is launched on the other hand, anyone trying to only run this project to quickly get a new badge, can initially be hit with the quota, and if haven't got any cache of other work can actually run-out of work before enough tasks starts getting validated.

This will be the same for any single-project-users if their projects application is upgraded.

In any case, 2 betas both returned & validated without any problems.

Thanks Ingleside, you explained it much better than I did. What I was initially referring to is after I returned my first result I was getting the message "this computer has finished a daily quota of 1". What I noticed later is that the first result had ended in error. This would have reduced the quota of 2 to 1 explaining the discrepancy.

----------------------------------------