| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: GPU: New option "Allow research to run on my CPU?" Yes/ No |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 50
|
|
| Author |
|
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: 
|
I think it would be nice to specify GPU for some projects but not others too. (It might be simpler to put another check box on the same line as the project name, and label it "GPU Only", but that is another matter.)
But the different projects take different hardware support, with CEP2 and now HCC-GPU being the most obvious examples. You will probably need to tailor the projects you work on to the hardware you have, and will need as much flexibility as possible. Otherwise, you will lose people who are forced to make a global choice one way or the other. |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
!
----------------------------------------[Edit 1 times, last edit by skgiven at Jul 18, 2012 8:48:23 PM] |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
Just create the HCC GPU project and be done with it.  Just my opinion but WCG is going to run off a GPU cliff they have not yet even seen. It is also unlikely they will change direction. Time will tell but keeping CPU and GPU seperate solves a lot of problems without special configuration code for each science. The error rate for the last Beta's is rather scary too. They are still a long way from having a production application.   [Edit 1 times, last edit by Dataman at Jun 30, 2012 1:58:33 AM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Just create the HCC GPU project and be done with it. Just my opinion but WCG is going to run off a GPU cliff they have not yet even seen. It is also unlikely they will change direction. Time will tell but keeping CPU and GPU seperate solves a lot of problems without special configuration code for each science. The error rate for the last Beta's is rather scary too. They are still a long way from having a production application. Good perspective DM. It seems to me as though the error rate is more specific to a certain setup than to the app itself. Maybe I was just lucky with the last run of betas but I had no error/invalid tasks and every resend I received that was marked error/invalid was successfully finished on my crunchers. 
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges:
|
Just create the HCC GPU project and be done with it. Just my opinion but WCG is going to run off a GPU cliff they have not yet even seen. It is also unlikely they will change direction. Time will tell but keeping CPU and GPU seperate solves a lot of problems without special configuration code for each science. The error rate for the last Beta's is rather scary too. They are still a long way from having a production application. Good perspective DM. It seems to me as though the error rate is more specific to a certain setup than to the app itself. Maybe I was just lucky with the last run of betas but I had no error/invalid tasks and every resend I received that was marked error/invalid was successfully finished on my crunchers. Yes. I have not had any problems either. But when I look at the error rate of ohers that run the same cards as I do the error rate is way too high . Granted a lot of it is because some just do not know what they are doing yet (meaning no disrespect). Still too high nonetheless. Oh well, no matter what happens I am confident WCG will make GPU work and the ensuing process will be "interesting" to watch.  I am just concerned that a bad GPU roll out could impact the HCC project as a whole. Better to keep them seperate.Thanks for your perspectives skgiven and nanoprobe.  I would say that this is just my two cents worth but I only have one cent left in my bank account.  [Edit 1 times, last edit by Dataman at Jun 30, 2012 3:42:24 AM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
I would say that this is just my two cents worth but I only have one cent left in my bank account With your electric bills I can understand that.  I shudder to think what my next one will look like.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges:
|
It will only be sane to create an HCC GPU project, otherwise madness will surely entail. I think there was an earlier posting somewhere that when the beta is over, they intend to go all-GPU. That is fine with me, but I am not sure that everyone who wants to do GPU-crunching is really prepared for it. They will find their desktops unusable for stretches of time unless they use a dedicated card (and probably a CPU core to go with it), and those who do overclocking will see high error rates, if not outright crashes. Hopefully that will all be compensated for by the much higher throughput that a GPU provides, but there could be a transition period where people are being educated as to what works and what doesn't. They will in practice probably need to provide both CPU and GPU versions until they get over the hump. [Edit 1 times, last edit by Jim1348 at Jun 30, 2012 10:34:50 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
HCC on CPU is *not* going to be stopped, if that was being suggested. Both will run in tandem to the end of HCC1. The fastest majority will continue their CPU crunching no doubt.
------------------------------------------//-- edit: insert "on CPU" [Edit 1 times, last edit by Former Member at Jun 30, 2012 10:51:09 AM] |
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
HCC on CPU is *not* going to be stopped, if that was being suggested. Both will run in tandem to the end of HCC1. The fastest majority will continue their CPU crunching no doubt. Then I too hope that HCC on GPU will be made a totally separate, opt-in science when it comes on line.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Let's work with wot we have:
1. You have to opt for GPU receipt (Yes) 2. Then you opt for HCC (Tick) 3. Then you opt for No CPU (No) Voila, only HCC on GPU. Inverse: No, Tick, Yes. Both: Yes, Tick, Yes (it's a tick tack toe with only winners). This can be done in 4 device profiles, so full control exists. (+there being the WCG exclusive of being able to create as many profiles as you can, serious hand on required though) Have a device you don't want GPU specifically, set that in the cc_config.xml with <no_gpus>1</no_gpus>. You can even config which display card GPU jobs are to run if multiple are in the system. What we have now is a working situation for HCC. When the second GPU project comes... well that *is* so far away. The one solution I've not worked out yet: CPU for other WCG sciences, except for HCC and HCC only on GPU. Any volunteers who worked this out? [It's probably too simple to see :?] --//-- |
||
|
|
|