| log in |
Message boards : Number crunching : I want to process only GPU data and no CPU data files.
| Author | Message |
|---|---|
|
I am looking for a way to avoid getting CPU data files. I do not want to interfere with the procesing of the SETI files on the CPUs. Can you help me? | |
| ID: 9674 · Rating: 0 · rate:
| |
|
Deselect 'Use CPU' in your Collatz Preferences. | |
| ID: 9675 · Rating: 0 · rate:
| |
|
I have deselected use CPU "since the project started" and now suddenly I am getting SSE CPU tasks on one of my hosts. Due to this I can't use Collatz, anyone else having the same "bug" ? | |
| ID: 9709 · Rating: 0 · rate:
| |
|
Have you got your computers set to different venues, with different preferences for each?, or do you have Just the Default preferences? | |
| ID: 9710 · Rating: 0 · rate:
| |
I have deselected use CPU "since the project started" and now suddenly I am getting SSE CPU tasks on one of my hosts. Due to this I can't use Collatz, anyone else having the same "bug" ? This setting was changed during a Server upgrade a while back I think but only for some people, most of us went in and reset the settings to the way we wanted them to be, have you checked yours and is it still set the way you want it to be? This did NOT affect everyone just some of us. | |
| ID: 9721 · Rating: 0 · rate:
| |
|
This is still happening. Can you look into it please? I have separate prefs set via BAM and no cpu WUs set for my work box but I still get them there. | |
| ID: 10005 · Rating: 0 · rate:
| |
|
When not using BAM it seems to work fine, so maybe the problem is BAM... | |
| ID: 10006 · Rating: 0 · rate:
| |
|
Yes, I know and have done that. BAM is where I set up the separate profiles for my machines. Here is where I configured those profiles. Back to my original request. :-) | |
| ID: 10009 · Rating: 0 · rate:
| |
|
Host running ati13ati | |
| ID: 10011 · Rating: 0 · rate:
| |
|
Enable sched_op_debug in the cc_config and then look at the log when it requests work. Does it request more than 0 seconds of CPU work even though you have disabled it in your preferences? If so, the issue is with the BOINC client and/or BAM. Please note that the client will alternate between GPU and CPU requests so you have to look through several requests to see what it is doing for sure. | |
| ID: 10016 · Rating: 0 · rate:
| |
Enable sched_op_debug in the cc_config and then look at the log when it requests work. Does it request more than 0 seconds of CPU work even though you have disabled it in your preferences? If so, the issue is with the BOINC client and/or BAM. Please note that the client will alternate between GPU and CPU requests so you have to look through several requests to see what it is doing for sure. This is why , I wanted to run COLLATZ Conjecture on GPU not CPU! 120 times faster, a EAH5870 v.s. Core i5 2.7GHz Additional software to 'control' BOINC, only takes extra CPU cycles :) ____________ | |
| ID: 10018 · Rating: 0 · rate:
| |
|
And in your Account Settings settings for Collatz C., you've set | |
| ID: 10022 · Rating: 0 · rate:
| |
|
Use CPU | |
| ID: 10023 · Rating: 0 · rate:
| |
Enable sched_op_debug in the cc_config and then look at the log when it requests work. Does it request more than 0 seconds of CPU work even though you have disabled it in your preferences? If so, the issue is with the BOINC client and/or BAM. Please note that the client will alternate between GPU and CPU requests so you have to look through several requests to see what it is doing for sure. I take that to mean you have already enabled sched_op_debug and have seen that the BOINC client is requesting CPU work even though the preferences are set to not use the CPU. If that's the case, there isn't anything I can do on this end. The bug is in the BOINC client. The preferences control the client asking for work and not the server sending work. In other words, if the client asks for CPU work, the server will send it. | |
| ID: 10030 · Rating: 0 · rate:
| |
Enable sched_op_debug in the cc_config and then look at the log when it requests work. Does it request more than 0 seconds of CPU work even though you have disabled it in your preferences? If so, the issue is with the BOINC client and/or BAM. Please note that the client will alternate between GPU and CPU requests so you have to look through several requests to see what it is doing for sure. I know that this option does work, have had CPU use deselelected on each venue, and the computers on those venues don't get CPU work, If you look at the Properties Page for Collatz in Boinc Manager, it should say 'Don't fetch CPU tasks', and if you enable <work_fetch_debug> logging you should see work fetch for CPU's is blocked: 21/10/2010 19:13:16 | Collatz Conjecture | [work_fetch] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (blocked by prefs) Boinc 6.10.18 and earlier did have a Bug with Multi Venue Preferences, where preferences from the default venue interfered with Work/School/Home venues, I reported this issue prior to 6.10.17 becoming recommended, It was finally fixed in Boinc 6.10.19, and every version i've tested since then has worked correctly, Claggy | |
| ID: 10032 · Rating: 0 · rate:
| |
|
| |
| ID: 10033 · Rating: 0 · rate:
| |
Message boards :
Number crunching :
I want to process only GPU data and no CPU data files.