| 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: 47
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just today I was reading an article in Computer Power User (CPU) examining CUDA applications. It mentioned Folding@Home but concentrated on video programs. One application ran using only 13% of a CPU, but most used at least 60%. Conclusion - it will take a while before the commercial programmers learn how to make good use of CUDA. My take on this subject - until HCC or another project has a CUDA version of their project debugged and running well on a GPU, WCG will not be feeling any pressure. I expect that we will be able to move fast then. Until we reach that point, we can prepare in a slow and deliberate manner since speeding up will not accomplish anything without a project. Lawrence So, nobody is misled: GpuGrid uses 0-2% cpu and--I think--F@H is currently about the same. It's been that way for months. Aqua uses 7-8%, but their client is brand new and they are at the beginning stages. I don't know about seti, MW, etc. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I get that WCG is not currently supporting a CUDA aware version of BOINC because they are not hosting any projects that currently use CUDA. The issue I see is that people are told they have the wrong version (sometimes even when that has nothing to do with the issue at hand) if they are running a 64 bit version, CUDA aware version, or anything other than exactly what WCG's vision of what the BOINC world should be. Not everyone who crunches at WCG, only crunches for WCG. The point you have missed is that WCG has a supported version of BOINC. If you want to crunch for WCG, then you SHOULD use the supported version. If you choose to use another version, for any of many reasons, you may certainly choose to do so, but if you do, do not then harp at WCG or the CAs for support. As has been said elsewhere, please contact BOINC directly. At WCG, you can only be certain to get support for the WCG supported version of BOINC. Anything more is a gift of kindness to you and not something to be demanded or even expected. |
||
|
|
Steve WCG
Senior Cruncher Joined: May 4, 2009 Post Count: 216 Status: Offline |
The point you have missed is that WCG has a supported version of BOINC. If you want to crunch for WCG, then you SHOULD use the supported version. If you choose to use another version, for any of many reasons, you may certainly choose to do so, but if you do, do not then harp at WCG or the CAs for support. As has been said elsewhere, please contact BOINC directly. At WCG, you can only be certain to get support for the WCG supported version of BOINC. Anything more is a gift of kindness to you and not something to be demanded or even expected. You post implies that I harp/ demand / expect support for issues caused by unsupported versions. That simply is not true. I see the BOINC community as more diverse than just crunching WCG and was expressing my opinion in hope that it might open some people's minds to the possibility of expanding support to a 64 bit and/ or CUDA boinc managers. Disagreeing is fine but please don't tell me what I SHOULD do and the condescending remarks that give me permission to make my own choices are uneccesary. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I see the BOINC community as more diverse than just crunching WCG and was expressing my opinion in hope that it might open some people's minds to the possibility of expanding support to a 64 bit and/ or CUDA boinc managers. It certainly is diverse, but you are in the WCG forums not the BOINC forums. I was making the point that people are DEMANDING support by the WCG CAs for software that WCG does not support. They either need to convert to WCG supported software or contact BOINC for support. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ouch!!
Hopefully we are supporting all WCG members who crunch here. It is just that it can be frustating to find members using versions of BOINC that we have not debugged and which are mainly under developmwent to support CUDA features that we do not use here. Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well I haven't seen anyone that goes without help.
But if it's concluded that the error is because you have a newer version of boinc than WCG supports then the answer is going to be to regress or deal with it, because that's the only things that can be done. Well I could try to contribute to BOINC's code but i'm 14 so they wouldn't trust me anyways XD |
||
|
|
mikey
Veteran Cruncher Joined: May 10, 2009 Post Count: 826 Status: Offline Project Badges:
|
Well I haven't seen anyone that goes without help. But if it's concluded that the error is because you have a newer version of boinc than WCG supports then the answer is going to be to regress or deal with it, because that's the only things that can be done. Well I could try to contribute to BOINC's code but i'm 14 so they wouldn't trust me anyways XD Actually your age would hopefully have nothing to do with it, it should be your experience and knowledge and skills and abilities that keep you out or let you help! We were ALL 14 once, or will be soon for those still younger than that, and sometimes we old fogies forget what it was like to be young and full of energy!! ![]() ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ouch!! Hopefully we are supporting all WCG members who crunch here. It is just that it can be frustrating to find members using versions of BOINC that we have not debugged and which are mainly under development to support CUDA features that we do not use here. The point I made was phrased to be direct. I have watched these forums for a year and there are many posts that PROVE my point. It's enough work to help people who ARE using the supported versions and are having problems. How many seconds am I (a non-MS employee) going to spend to help a user install MS Office 2007 on a Windows 95 system? None, because it is not supported. The fact that you CAs give it a try shows just how talented you are and how much you care about all crunchers. |
||
|
|
SlumLord
Cruncher Joined: Jan 23, 2006 Post Count: 2 Status: Offline Project Badges:
|
So, nobody is misled: GpuGrid uses 0-2% cpu and--I think--F@H is currently about the same. It's been that way for months. Aqua uses 7-8%, but their client is brand new and they are at the beginning stages. I don't know about seti, MW, etc. Every Seti@Home unit that I've had (100's now) has used 0.08% CPU usage. |
||
|
|
xMD-Crusher
Cruncher Joined: Jun 8, 2009 Post Count: 4 Status: Offline |
On that note, why not give the other 99.92% of idle cycles to this project where we know for sure we will find answers to cures and other tangible issues. You know ET = Earthly Targets
![]() |
||
|
|
|