| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Community
Forum: Teams
Thread:  Join "MyOnlineTeam" Today - Chapter 41 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 490
|
|
| Author |
|
|
darth_vader
Veteran Cruncher A galaxy far, far away... Joined: Jul 13, 2005 Post Count: 514 Status: Offline Project Badges: 
|
Just noticed something else about DDDT2. BOINC defaults to switching between projects every 60 minutes. Normally, I wouldn't think that setting would matter if all you are running is WCG. It may be a result of me adding FreeHAL on my quad but I saw BOINC switch from once DDDT2 WU to another. With the infrequent checkpoints on the type A's, this switching may end up wasting a good bit of crunching time. If you've got an active WWWT2 type A WU, you can click on Advanced/Preferences and, in the Switch between Applications field, enter the estimated hours to complete times 3600 (to convert it to seconds). You'll see the WU running, high priority which means normally it will run until it finishes. Note that BOINC normally won't get new work during that time but you can just click on the clear button to go back to your normal settings. This may matter to those of you who prefer to try to squeeze out as much work from your machines as you can. Keith - do you have the box checked to keep the applications in memory when suspended? I think when that's checked, you don't have to go back to the previous checkpoint (I haven't verified this).Two of my DDDT2 WU have now validated. In both cases my machine claimed significantly less credits than my wingman: erlc_ d215_ ps0000_ 1-- 612 Valid 2/17/10 20:25:07 2/20/10 18:59:19 33.60 573.1 / 678.7 erlc_ d215_ ps0000_ 0-- 612 Valid 2/17/10 20:24:09 2/22/10 07:55:45 53.55 931.8 / 678.7 and erlc_ d205_ ps0000_ 1-- 612 Valid 2/17/10 20:22:26 2/20/10 07:39:06 33.40 569.7 / 569.7 erlc_ d205_ ps0000_ 0-- 612 Valid 2/17/10 20:22:23 2/20/10 08:46:56 37.30 1,014.5 / 569.7 I find the disparity quite interesting... as well as the fact that only a few minutes difference resulted in 100+ credits difference. - D Uh, those times are in hours. The first one is a 20 hour difference and just four in the second. - D |
|||
|
||||
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: 
|
snip .................................CONGRATULATIONS RT ON REACHING 33,000,000 MOT POINTS !!!............................... snip Thanks Friend. This cool weather lets me keep everything cranking. |
|||
|
||||
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18665 Status: Offline Project Badges: 
|
Just noticed something else about DDDT2. BOINC defaults to switching between projects every 60 minutes. Normally, I wouldn't think that setting would matter if all you are running is WCG. It may be a result of me adding FreeHAL on my quad but I saw BOINC switch from once DDDT2 WU to another. With the infrequent checkpoints on the type A's, this switching may end up wasting a good bit of crunching time. If you've got an active WWWT2 type A WU, you can click on Advanced/Preferences and, in the Switch between Applications field, enter the estimated hours to complete times 3600 (to convert it to seconds). You'll see the WU running, high priority which means normally it will run until it finishes. Note that BOINC normally won't get new work during that time but you can just click on the clear button to go back to your normal settings. This may matter to those of you who prefer to try to squeeze out as much work from your machines as you can. Keith - do you have the box checked to keep the applications in memory when suspended? I think when that's checked, you don't have to go back to the previous checkpoint (I haven't verified this).Two of my DDDT2 WU have now validated. In both cases my machine claimed significantly less credits than my wingman: erlc_ d215_ ps0000_ 1-- 612 Valid 2/17/10 20:25:07 2/20/10 18:59:19 33.60 573.1 / 678.7 erlc_ d215_ ps0000_ 0-- 612 Valid 2/17/10 20:24:09 2/22/10 07:55:45 53.55 931.8 / 678.7 and erlc_ d205_ ps0000_ 1-- 612 Valid 2/17/10 20:22:26 2/20/10 07:39:06 33.40 569.7 / 569.7 erlc_ d205_ ps0000_ 0-- 612 Valid 2/17/10 20:22:23 2/20/10 08:46:56 37.30 1,014.5 / 569.7 I find the disparity quite interesting... as well as the fact that only a few minutes difference resulted in 100+ credits difference. - D Uh, those times are in hours. The first one is a 20 hour difference and just four in the second. - D Oh I knew those two were yours. Granted credit is a different animal from claimed. Your two times are very close and so are the credits claimed. Granted is supposed to basically be an average of the two claimed values. However, if the difference between the two claimed is big enough, it says that something isn't right and different rules then apply. On the first WU, you claimed about 17 credits per CPU hour. The wingman claimed about the same. A simple average of the two would have given about another 70 credits so I wonder why you both got less than that. On the second WU, the wignman claimed almost double for about four more CPU hours. That's a big difference that must have been flagged in the algorithm. EDIT: From the BOINC Wiki, this is how claimed is figured: When your computer completes a result, BOINC determines an amount of claimed credit in one of two ways: In general, the claimed credit is the result's CPU time multiplied by the CPU benchmarks as measured by the BOINC software. NOTE: the BOINC software is not optimized for specific processors. Its benchmark numbers may be lower than those produced by other programs. Some applications determine claimed credit themselves, and report it to BOINC. This would be the case, for example, with applications that use graphics coprocessors or other non-CPU hardware. Claimed credit is reported to a project when your computer communicates with its server. The granted credit that you receive may be different from the claimed credit, and there may be a delay of a few hours or days before it is granted. This is because some BOINC projects grant credit only after results have been validated. The basic hourly claim the client submits with a Result to the project servers is the sum of Whetstone plus Dhrystone values of the last Benchmark divided by about 480 (it varies slightly with processor and OS). Thus for instance (2,000 Whetstone + 6,000 Dhrystone) / 480 = 16.66 hourly claim. This exact value will not always show on the results listing of projects. It is often substituted by their own pre-assigned credit value. EDIT2: More digging found this on credit granted on quorum of 2 projects in the FAQ as originally posted by Kevin: The way that credit is awarded in a quorum of two is that the two claimed credits are compared and if they are within 30% of each other, then they are averaged and the average value is granted. Over 85% of workunits have the granted credit determined this way. If the two claimed credit values are further then 30% apart, then the code looks at a field in the database which stores the recent average credit granted per second for each computer. Whichever computer's claimed credit per second for the workunit is closer to their recent average credit granted per second has its claimed credit used as the credit granted for the workunit. What we found was that there were a few computers that were extremely consistent about claiming very low so they always caused the workunit to check the recent average history. Because they were consistently claiming low and it was matching their average granted credit they were being selected as the credit to use for the granted credit. We determined that these computers were claiming low by looking at the history of computers they were paired with and seeing their history - and indeed those other computers had a much lower grant when paired with one of these computers. As a result, we are going to change how the 2nd part of the process works. Instead of selecting the credit that is closest to its history, we will average the recent average history's for the two computers. We have been simulating the impact of this for the past couple of days and it turns out that in a strong majority of cases the result cpu time * host recent average credit per cpu second is actually quite consistent between different computers even if their claimed credit are further apart. This is what we had hoped to see and as a result we will start to use this policy in the near future. ---------------------------------------- [Edit 2 times, last edit by keithhenry at Feb 23, 2010 1:19:08 PM] |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Arrrggghhhh -- snowing again!!!
Well, good morning anyway  |
|||
|
||||
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges:
|
Good Mornin from Texas.
---------------------------------------- Snowing here as well. Hum..I guess this means that the weatherman was right predicting this 2 days ago. They never used to be right. |
|||
|
||||
|
NiceMedTexMD
Veteran Cruncher United States Joined: Aug 17, 2006 Post Count: 929 Status: Offline Project Badges:
|
is there an estimate as to when the DDDT2 wu's will be mostly available for public consumption? :)
----------------------------------------Dr. Mike..  |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
is there an estimate as to when the DDDT2 wu's will be mostly available for public consumption? :) Dr. Mike -- from what I hear, DDDT2 is going to be pretty slow going for quite some time.Dr. Mike.. |
|||
|
||||
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18665 Status: Offline Project Badges:
|
MyOnlineTeam Daily Statistics for 02/23 - All Members:
----------------------------------------Team rank movement report =========================
Points milestones report ======================== hne12359 reached 25,000 points  Runtime milestones report ========================= No runtime milestones found.  Results returned milestones report ================================== No results returned milestones found. New members report ================== No new members found. Retired members report ====================== No new retired members found. For the week as a team: Statistics Total Run Time Points Results Team Records: Results Returned: 12/19/2007 2,522 Points: 05/06/2009 518,871 Runtime: 01/25/2006 1:123:00:53:34 Good crunching folks!!!!! |
|||
|
||||
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18665 Status: Offline Project Badges:
|
MyOnlineTeam Daily Statistics for 02/23 - Active Members
----------------------------------------Active team members report ==========================
Note: Active members are those who earned points in the prior 30 days. Top Twenty active members returning points today: 01: RT - 108,713 points 02: NiceMedTexMD - 46,023 points 03: Coingames - 44,408 points 04: marysduby - 42,046 points 05: parmesian - 35,202 points 06: Vuj - 25,239 points 07: brown chris - 19,247 points 08: keithhenry - 17,458 points 09: Dave Bell - 16,711 points 10: Bravehart - 14,048 points 11: darth_vader - 7,242 points 12: Rene Punt - 6,562 points 13: sulcata - 6,125 points 14: Blueprint - 5,840 points 15: Jockin - 4,503 points 16: Esteban69 - 3,507 points 17: Daeloan - 2,839 points 18: Sunny L. Kae - 2,567 points 19: harry_i_c - 2,321 points 20: imin - 2,251 points Total points returned today: 433,142 Active members returning points today: 37 Average points per member active today: 11,706.5405 |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
...................................CONGRATULATIONS hne12359 ON REACHING 25,000 MOT POINTS !!!................................. |
|||
|
||||
|
|