| 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: 52
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Spot on, KWSN - A Shrubbery.
----------------------------------------Yet to see an actual proposal how then to do this, of course, there also having to be drawn in the BETA test criteria... no half measure. But, after nearly 650,000 years doubt something in achievement criteria will be changed [ACAH was a special case for exception]. GPUs is just another [albeit much faster] resource being tapped into. Edit: And why bring it up when it's already been mentioned a dozen times... the certificates which will have levels all the way to well above 2000 years [I'd consider IBM themselves to be out of contention]. No idea what the waiting is on... it's extreme silence in that privileged CA room on the front of peek info. Maybe this time it got shifted silently to 2013... maybe on the 8th anniversary in November. Most certainly consider that this will put a silencer on the bigger badge story [for a while of course]. [Edit 1 times, last edit by Former Member at Sep 11, 2012 6:34:36 AM] |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges:
|
This argument is no different than the dynamic that has been occurring since the launch of WCG. An i7, or more specifically one hyperthreaded half of one core, performs far more calculations per hour than my 486-66 that first crunched the grid and yet it is rewarded with the same amount of run time per work unit. There are multiple metrics for a reason. Run time counts run time. Points count points. Never the 'twain shall meet. Nothing else to say, just "Agree" Cheers ![]() Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006 ![]() |
||
|
|
mikey
Veteran Cruncher Joined: May 10, 2009 Post Count: 826 Status: Offline Project Badges:
|
Spot on, KWSN - A Shrubbery. Yet to see an actual proposal how then to do this, of course, there also having to be drawn in the BETA test criteria... no half measure. But, after nearly 650,000 years doubt something in achievement criteria will be changed [ACAH was a special case for exception]. GPUs is just another [albeit much faster] resource being tapped into. Edit: And why bring it up when it's already been mentioned a dozen times... the certificates which will have levels all the way to well above 2000 years [I'd consider IBM themselves to be out of contention]. No idea what the waiting is on... it's extreme silence in that privileged CA room on the front of peek info. Maybe this time it got shifted silently to 2013... maybe on the 8th anniversary in November. Most certainly consider that this will put a silencer on the bigger badge story [for a while of course]. THANK YOU for the sneak peak into the inner sanctum thinking!!!!! It will be a welcome addition to many! ![]() ![]() |
||
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges:
|
Currently badges are awarded based upon run-time. With the advent of GPU crunching, the credits will rise dramatically but the run time increase will be minimal, compared to the credit rise. Are there any plans to look again at the criteria for badge awards? ![]() It may work itself out, if you can run more than 1 WU at a time. ![]() |
||
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges:
|
Currently badges are awarded based upon run-time. With the advent of GPU crunching, the credits will rise dramatically but the run time increase will be minimal, compared to the credit rise. Are there any plans to look again at the criteria for badge awards? ![]() It may work itself out, if you can run more than 1 WU at a time. ![]() Or not... Since the GPU WU is also taking a CPU to run, why isn't the run-time for both (ie. if you are running GPU WUs 24/7, shouldn't run-time equal about 24 hours for the GPU and 24 hours for CPU)? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi BladeD,
When HCC started running on the GPU, one post mentioned that on one system, the HCC task ran on the CPU for 20 seconds of setup, then ran on the GPU for 40 seconds, then ran on the CPU for 40 seconds to create the result to send back. In all, 100 seconds on the system. I think that they do not run simultaneously so 100 seconds would be reasonable for badge time. The real payoff is in points. Lawrence |
||
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges:
|
It locks up the CPU for the WHOLE 24/7 and no other WUs can run!
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
[ot]Experiment with a tool called Process Lasso if so inclined [I've done it quite extensively a few years back]. This one allows to "play" with affinities and automate assignments. E.g. how about setting the HCC science to only use the highest core and force the key system functions on others.[/ot]
Think the BOINC wider world concensus was to count elapsed time for GPU tasks... wallclock time from start to finish so to speak. You want the 100 seconds the CPU was allocated *plus* the 40 seconds on GPU?... No, those who'll want it all want both the CPU and GPU full time since the GPU is reserved too so to speak... but how that than works when a GPU can do multiple tasks... crunch and still uninterruptedly use the computer and watch streaming video? Let me take a very far roundabout tour away from that thought process. I'll go watch Walter Matthau and Jack Lemmon's grumpy old man: Max: If I die today, I die a happy man. John: You die today, I'm taking your motor. » |
||
|
|
Movieman
Veteran Cruncher Joined: Sep 9, 2006 Post Count: 1042 Status: Offline |
Points/Credits are cross-project brag rights, doing the time is the method at WCG to show off in the left forum margin. So here comes Scribe, who's done 1.5 years of HCC on CPU and 10 days on GPU, which is at it's 18 times faster, gives the CPU equivalency right of 180 CPU days. So really, you want the cake and eat it too. I got the opposite out of his comments, he thinks it is WRONG to do it the same as other projects. If you crunch a gpu unit and it takes 6 seconds, okay you got 6 seconds towards your badge, the idea is you can crunch thousands of those 6 second units in a day as compared to three 8 hour units from another project using your cpu. Having more and or faster gpu's is just like having more and or faster cpu's, more work done in a day and more total credits but not more credits per unit. I currently have a little bit over 20 cpu cores here at WCG, but I don't get any more credits per unit than the next person, I get more total credits per day as a result of more resources allocated here. Sure I finish more units per day on my AMD 6 core cpu than I do on my Intel dual core pc, but that is just a function of the AMD 6 core being significantly faster and more efficient. Agreed, someone buy Mikey a nice dinner! IF any badges are to be added I'd like to see them for time on the project such as 5 years,10 years,20 years etc.. ![]() [Edit 1 times, last edit by Movieman at Oct 14, 2012 6:29:17 PM] |
||
|
|
Bugg
Senior Cruncher USA Joined: Nov 19, 2006 Post Count: 271 Status: Offline Project Badges:
|
Bottom line is badges here are awarded based on the TIME spent crunching via whichever processing unit is doing the work, NOT the credits received for doing said work. Personally, I say if ya don't like it, then why the heck are you here? It is how it is, and there's very very few that see any issue with it. :)
----------------------------------------![]() i5-12600K (3.7GHz), 32GB DDR5, Win11 64bit Home |
||
|
|
|