Message boards : Graphics cards (GPUs) : Why does CUDA always occupy a CPU's core ?
Author | Message |
---|---|
I find cuda program will occupy a CPU's core when it is running. But Task Manager shows the core occupied by cuda has done nothing until the cuda program terminates. | |
ID: 6627 | Rating: 0 | rate: / Reply Quote | |
Or it's a bug in gpugrid.net ? No, it's a bug in BOINC 6.4.5. Use 6.5.0 and you should be fine. MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 6628 | Rating: 0 | rate: / Reply Quote | |
Since anything later than 6.4.5 is a dev version, how can I know which ones are stable enough to use? | |
ID: 6845 | Rating: 0 | rate: / Reply Quote | |
As far as I understood 6.4.5 is also a development version. If that one does not behave well try 6.5.0. | |
ID: 6846 | Rating: 0 | rate: / Reply Quote | |
Is that a platform specific bug..? I don't have that on 6.4.5 and XP64...(on an X2 core). If you use 6.4.5 you have to make a cc_config file with some goobledy-gook in it to make it see the CPUs and GPUs as needed. My 6.4.5 must be twisted...It's stock, and runs fine... ____________ Consciousness: That annoying time between naps...... Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it. | |
ID: 6847 | Rating: 0 | rate: / Reply Quote | |
As far as I understood 6.4.5 is also a development version. If that one does not behave well try 6.5.0. You have it backwards ... 6.4.5 is "recommended" by UCB ... 6.5.0 is development, but is better and more stable ... which is why we recommend it ... in this case "better" because it runs GPU tasks without needed a configuration file like 6.4.5 and earlier do ... As to Daniel's question ... you ask people you trust ... :) If you use 6.4.5 you have to make a cc_config file with some goobledy-gook in it to make it see the CPUs and GPUs as needed. 6.5.0 sees the GPUs correctly (Nvidia only) ... Of course, the next question, do you trust me ... :) | |
ID: 6848 | Rating: 0 | rate: / Reply Quote | |
You have it backwards ... 6.4.5 is "recommended" by UCB Recommended by UCB? Oh, I missed that one. The 6.4.x seemed such a step backwards compared to 6.3.21, so the idea that these might be official never crossed my mind. And I wondered why GPU-Grid recommended 6.4.5 .. :D MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 6849 | Rating: 0 | rate: / Reply Quote | |
You have it backwards ... 6.4.5 is "recommended" by UCB Yeah ... The problem is that the developers, as best as I can tell are not, ahem, real users of BOINC. By that I mean that they don't seem to have that much interest in the operational use of BOINC to do projects. My opinion is derived from there longstanding opposition to many features that would make BOINC easier to use when running BOINC. I mean, multiple select rows did not get into the thing until 5 years after launch. Even now, how many people know about that feature? For those that use BOINC as start and forget, and there are a lot of people out there that are like that, BOINC has always been adequate, even bad versions like 6.4.5 which does work if you just leave it alone. *BUT*, if you are passionate about your projects, and involved with them, BOINC is very inadequate. Saddest of all BOINC does not meet several of its design goals nor its original vision. | |
ID: 6856 | Rating: 0 | rate: / Reply Quote | |
I think I know what you mean. Especially the first BOINC versions, when basically everything was still alpha / beta, it could *almost* drive one mad not to have manual overrides. So hard to tell BOINC what it should do in cases where it didn't automatically do it right. However, since a couple of years it basically ran flawlessly for me. | |
ID: 6866 | Rating: 0 | rate: / Reply Quote | |
I think I know what you mean. Especially the first BOINC versions, when basically everything was still alpha / beta, it could *almost* drive one mad not to have manual overrides. So hard to tell BOINC what it should do in cases where it didn't automatically do it right. However, since a couple of years it basically ran flawlessly for me. Overall I also have little to complain about with regard to operation, the only problem is that if you do want to customize the operation some, it is very difficult to do so. If you just want to load and forget it, it will run reasonably well with no intervention. My problem with it is that with the way I run projects and by careful (obsessive?) observation I can see that it is not really running tasks the way that the developers say it should be running tasks ... more importantly, it does not run them the way I would like them to be run. That said, mostly I do just let it run ... The problem is that there are 10 kinds of BOINC users ... :) The kind that knows binary and those that don't ... some of us want a little more direct control over the flow of work through our systems ... yet the developers insist that if they give us those controls the people that will NOT intervene in their systems will use the controls to mess things up ... as if they are not sometimes messed up already ... But, we are way off topic here .... | |
ID: 6895 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : Why does CUDA always occupy a CPU's core ?