Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 5541
|
![]() |
Author |
|
SNURK
Veteran Cruncher The Netherlands Joined: Nov 26, 2007 Post Count: 1217 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
My thinking would be that if you retain the daily export for 30 days and take the newest and one nearest the 30 day mark, take run time difference and divide by days between those 2 exports, you'd have a fair mean. For the starters you could accept to just use that formula or test join date against last export date to see if less than 30 days, and use that as an avarager... molto complicato ;? Either that, or keep stats for every day, and take the average of the last 30 'good' days (good being the days that the script succeeded in getting the data) and take average of that. This way there's a possibility to take the spikes out. Say: pick 30 days, take the 2 highest spikes and the 2 lowest spiks out, and devide the remainder by 26. Or something.. That's what I did way back when I created a signature only for myself, with the history available under my grid / my statistics history. As I commented in the ''Going under...'' and "Building 600 TFL machine" threads, [we] may have to review if to stick to the old 100 Cobblestones per GFL for performance indicating, or go the new BOINC 200 Cobblestones/GFL. For the moments the credits have though not at all doubled [to what SETI gives per second, but including their GPU credits] per the new server 7 credit system. We used to run 1.59 TFL per year and after few days on new system it's 1.806/year, so holding off for a little to maybe when we get GPU contributions running at WCG. Anticipating, but not overly, that this will lift credit substantially [not having been allowed to sniff the tech kitchen at all how the credits will be approached for that part. Time will though remain time as I understand 1 day GPU is 1 day runtime as clocked by the CPU elapsed, meaning the term Runtime has to remain and is not clean CPU time or GPU time [GPU's do not understand the time concept, which is why Elapsed it taken] Oops, that last statement surprised me. Do I understand correctly that for GPU work, all that's available will be elapsed time, not run time? Meaning that if you set the GPU to work only 50% on Boinc, it will still report a run time of 24 hours per day instead of 12? Then to GFL calculation. Do you know of any instance where 'our' GFLs have been compared to the real GFLs that a particular system is capable of. I suppose that the theoratical GFLs of a particular CPU can be found in some datasheet somewhere, or an application that tests and tells you the GFLs of your system. Of course Boinc has such a test if that's any good. Would be interesting to know if these values are close or way off. Perhaps that could bring us some closer to the multiplication value to settle for. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
marvey11,
----------------------------------------Thanks, but you missed to quote the last line I wrote in that post. Am aware of the possible caveats and tricks there are around. We'll have to work with the numbers the WCG stats produce and no other ;>) --//-- [Edit 2 times, last edit by Former Member at Mar 9, 2012 5:45:30 PM] |
||
|
SNURK
Veteran Cruncher The Netherlands Joined: Nov 26, 2007 Post Count: 1217 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Just did a test on my desktop that's running WCG 24/7 and not used otherwise.
----------------------------------------Boinc says it's running at 1052 Installed a LINPACK bases tool that runs a test to determine GFlops, and lo and behold, it tells me after several tests it's doing 10,64 GFlops. Suspiciously close (?). ![]() edit: points became credits, see post of SekeRob below. ![]() ---------------------------------------- [Edit 1 times, last edit by SNURK at Mar 9, 2012 3:11:41 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Points or credits? Suppose it's a good excuse to just leave the way we present the present performance alone :D
--//-- |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Snurk - you currently know the Total run time, and you also know how many projects have produced badges - so a/b give Runtime/Active Project. Or am I missing something?
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So what you want is if someone puts all his eggs into a single research basket and has 25 years, to show runtime/project of 25 years and another who spread the wealth around over 10 projects, with total 25 years shows 2.5 years.
Don't see that as being correct by any inter-sig comparative manor which obviously than also will substantially shake up the sig ranking list that SNURK maintains. --//-- |
||
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
Snurk, remember there will always be unsatisfied people. This is your baby and it's working just fine. Don't feel pressured to change anything you are not comfortable with. I'm with Sekerob, I see no reason to change how globes/runtimes/years are calculated.
----------------------------------------![]() Distributed computing volunteer since September 27, 2000 |
||
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2989 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Snurk, remember there will always be unsatisfied people. This is your baby and it's working just fine. Don't feel pressured to change anything you are not comfortable with. I'm with Sekerob, I see no reason to change how globes/runtimes/years are calculated. +1 Considering that there's now well over 600 people who've got these signatures, methinks you've already done a very good job - so, from my own perspective, don't change things just for the sake of change. Yes, change them if there's a considerable improvement or additional information that can be shown, but not to just try and please everyone - you'll (unfortunately) never achieve that... ![]() |
||
|
astrolabe.
Senior Cruncher Joined: May 9, 2011 Post Count: 496 Status: Offline |
If, by saying:
Well Snurk - it's in your hands amigo, and we'll abide by your decision. what you really mean is:Since you SNURK, have done all the work, including the design, programming and algorithms, such that the total responsibility for the design is totally yours to do with as you wish, AND our only choice is to either say a big THANKS for beauty of your work , or otherwise sit back and complain, criticize, nit-pick and gnaw; ![]() I agree |
||
|
astrolabe.
Senior Cruncher Joined: May 9, 2011 Post Count: 496 Status: Offline |
Hi Snurk - you currently know the Total run time, and you also know how many projects have produced badges - so a/b give Runtime/Active Project. Or am I missing something? What you are missing is that the design presents the Run Time per project, calculated on all projects. That is the design. That is what SNURK has decided to use. Asked and answered. |
||
|
|
![]() |