| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Conquer Cancer
Thread: It's as bad as the beta |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 96
|
|
| Author |
|
|
brown chris
Master Cruncher California - USA Joined: Nov 18, 2004 Post Count: 2556 Status: Offline Project Badges: 
|
I solved the lag problem by adding a second video card, connecting it to my monitor and excluded it from use.
----------------------------------------Here's my cc_config.xml file: <cc_config> <options> <exclude_gpu> <url>http://www.worldcommunitygrid.org</url> <device_num>1</device_num> <type>nvidia</type> <app>hcc1</app> </exclude_gpu> </options> </cc_config> And here is what the log file reports when BOINC manager starts: 10/13/2012 9:25:37 AM | | NVIDIA GPU 0: GeForce GTX 275 10/13/2012 9:25:37 AM | | NVIDIA GPU 1 (not used): GeForce 9800 GT 10/13/2012 9:25:37 AM | | OpenCL: NVIDIA GPU 0: GeForce GTX 275 10/13/2012 9:25:37 AM | | OpenCL: NVIDIA GPU 1 (not used): GeForce 9800 GT It's crunching away and I'm still able to use my computer without any lag. Several notes, though. The only card that would work in the second PCIE slot had to be an nVidia card. It's what I have in my primary slot and Windows wouldn't load another driver other than the nVidia driver. Also, a generic PCI card didn't work, either - even a hi-powered nvidia PCI card. Windows wouldn't load a driver for it. It's also crunching those WU's even faster (about 3.5 minutes instead of 4.5 minutes). I'm guessing it's because I'm not using it as a video card. I'm using Windows 8 and BOINC 7.0.31. Hope this helps!
BIG BANG THEORY: In the beginning there was nothing... which exploded
|
||
|
|
JacobKlein
Cruncher Joined: Aug 21, 2007 Post Count: 21 Status: Offline |
brown chris, thanks for trying to help. But you only found a workaround; you did not solve the problem. Excluding the GPU from crunching, whether it be via unchecking "Use GPU while computer is in use", or via cc_config.xml <exclude_gpu>, or via Activity->Suspend GPU, or via Tray->Right Click -> Snooze GPU... none are solutions.
I have 3 GPU's, and of course my beefiest one is the one I actually use as a display. I don't want it to be excluded at all! So, again, the problem is on WCG and IBM to fix. PS: You may not know this, but I'm the cruncher responsible for working with the BOINC developers (Dave, Rom, Charlie) to get that <exclude_gpu> option to even exist. :) I use it to tell BOINC to exclude my 2 non-display GPU's, since I run Folding@Home on those. That way, when I run a BOINC exclusive app (like a game), my 2 other GPUs can still crunch away. There was a time when I was going to allow those GPUs to run BOINC only for certain projects, but I decided my current setup is more productive, since an exclusive-app would stop crunching on all the GPUs. Fun eh? |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
You seem to be having us "try this and try that". I appreciate the help, but couldn't you actually try your solutions first? I mean, I see you pretty much copy/pasted a bunch of MilkyWay stuff, including a parameter list with tags in the wrong spot!, but now I'm thinking that parameter list includes parameters that are specific to the MilkyWay executable. Lets' set the record straight. I'm merely offering suggestions. I haven't tried them because I don't have the problem. I didn't copy and paste anything from Milkyway. Those files were for running more than 1 HCC task per GPU that I modified in the hope that it would help people. That tags were moved because they caused errors if put where the Milkyway tags were. If you don't want to "try this or that" then by all means don't. I'm not going to apologize for trying to help.
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.
----------------------------------------  [Edit 1 times, last edit by nanoprobe at Oct 13, 2012 6:24:18 PM] |
||
|
|
JacobKlein
Cruncher Joined: Aug 21, 2007 Post Count: 21 Status: Offline |
We are both frustrated. I appreciate your suggestions, but I would appreciate them more if they were tried for validity first. I'm sure you know the purpose of the <cmdline> tag, and I'm sure you know that you can't just move it around in hopes that things will work differently. Also, it's likely that the WCG executable has different command line arguments than the Milkyway executable, so I don't even see how the suggestion could have been helpful.
I'm not asking for an apology. I'm sorry for offending you. But if we are going to solve this, we can't just offer various untested solutions. Do you happen to have any other ideas on how to solve this, by chance? I'm stumped, all I have are workarounds with consequences. I wish we had someone from WCG giving us more information about the problem and potential solutions -- I believe WCG has to fix it. |
||
|
|
brown chris
Master Cruncher California - USA Joined: Nov 18, 2004 Post Count: 2556 Status: Offline Project Badges:
|
brown chris, thanks for trying to help. But you only found a workaround; you did not solve the problem. Excluding the GPU from crunching, whether it be via unchecking "Use GPU while computer is in use", or via cc_config.xml <exclude_gpu>, or via Activity->Suspend GPU, or via Tray->Right Click -> Snooze GPU... none are solutions. I have 3 GPU's, and of course my beefiest one is the one I actually use as a display. I don't want it to be excluded at all! So, again, the problem is on WCG and IBM to fix. PS: You may not know this, but I'm the cruncher responsible for working with the BOINC developers (Dave, Rom, Charlie) to get that <exclude_gpu> option to even exist. :) I use it to tell BOINC to exclude my 2 non-display GPU's, since I run Folding@Home on those. That way, when I run a BOINC exclusive app (like a game), my 2 other GPUs can still crunch away. There was a time when I was going to allow those GPUs to run BOINC only for certain projects, but I decided my current setup is more productive, since an exclusive-app would stop crunching on all the GPUs. Fun eh? Thank you JacobKlein for being responsible for working with the developers to get that exclusion in. It may just be a work-around, but I am able to use my computer and crunch those GPU's at full-speed. And just for the record, I did solve my problem.
BIG BANG THEORY: In the beginning there was nothing... which exploded
|
||
|
|
Movieman
Veteran Cruncher Joined: Sep 9, 2006 Post Count: 1042 Status: Offline |
Seems to me that there are solutions here but just that people don't like them.
----------------------------------------Plain and simple if you have issues, shut off the app when your using the PC, and it is solved. If that is too much of a pain simply don't use the GPU app and do what you've always done. Problem is solved. BUT what I don't think is fair is to say I'm not happy that this app is sucking up so much of my GPU resources that my system is unusable. That is what it's supposed to do, use the GPU and that it is doing..YOUR in control and tune the app to meet what you want..On/Off or don't use it at all, it's your choice. I would also agree after using a nVidia and a ATI based card on the same machine that the "lagging" effects are nuch greater with a nVidia card which also presents another option, try a ATI card if you have nVidia.. I'm using a 3 year old Saffire 5870 that is working superb and doing WU in 4 mins flat or .2-3 as shown in the web based WCG page. Best of luck to all.  |
||
|
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: 
|
brown chris, thanks for trying to help. But you only found a workaround; you did not solve the problem. Excluding the GPU from crunching, whether it be via unchecking "Use GPU while computer is in use", or via cc_config.xml <exclude_gpu>, or via Activity->Suspend GPU, or via Tray->Right Click -> Snooze GPU... none are solutions. I have 3 GPU's, and of course my beefiest one is the one I actually use as a display. I don't want it to be excluded at all! So, again, the problem is on WCG and IBM to fix. PS: You may not know this, but I'm the cruncher responsible for working with the BOINC developers (Dave, Rom, Charlie) to get that <exclude_gpu> option to even exist. :) I use it to tell BOINC to exclude my 2 non-display GPU's, since I run Folding@Home on those. That way, when I run a BOINC exclusive app (like a game), my 2 other GPUs can still crunch away. There was a time when I was going to allow those GPUs to run BOINC only for certain projects, but I decided my current setup is more productive, since an exclusive-app would stop crunching on all the GPUs. Fun eh? Thank you JacobKlein for being responsible for working with the developers to get that exclusion in. It may just be a work-around, but I am able to use my computer and crunch those GPU's at full-speed. And just for the record, I did solve my problem.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
But you only found a workaround; you did not solve the problem. The problem needs to first be clearly defined but who would do that? What group is in the best position to describe the situation that hopefully would lead to a clear definition of the problem? That would seem to be the WCG-Techs, but where are they? For the meantime, with the silence, we are left with jabbing the symptoms not the problem.; |
||
|
|
Movieman
Veteran Cruncher Joined: Sep 9, 2006 Post Count: 1042 Status: Offline |
But you only found a workaround; you did not solve the problem. The problem needs to first be clearly defined but who would do that? What group is in the best position to describe the situation that hopefully would lead to a clear definition of the problem? That would seem to be the WCG-Techs, but where are they? For the meantime, with the silence, we are left with jabbing the symptoms not the problem.; BUT is there a problem? App is doing what it was designed to do, use the GPU to it's maximum. Ok, it seems that it is a issue for some people but not for all. Perhaps, if possible, a window to set percentage of GPU use so that the user can decide what to use whether 10% or 100%.. I have it running on this machine right now with a 5870 card and for net browsing no issue but this is a 16 core high end workstation. |
||
|
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: 
|
BUT is there a problem? App is doing what it was designed to do, use the GPU to it's maximum. Ok, it seems that it is a issue for some people but not for all. Perhaps, if possible, a window to set percentage of GPU use so that the user can decide what to use whether 10% or 100%.. I have it running on this machine right now with a 5870 card and for net browsing no issue but this is a 16 core high end workstation. The Folding@home people have been working for years trying to control the GPU usage, and were supposed to have a slider on their control unit to do just that a couple of revisions ago. But it is not an easy matter to control GPUs, unlike CPUs. I too was surprised when I first started using GPUs for distributed computing that they could be so ornery, and wondered how such projects survived. But I now see more of the technical problems inherent in their operation, and have learned to work around it. I am more annoyed now by the people who complain about it. I guess that is progress. |
||
|
|
|