But on the other hand, if Robert wants to use that GPU on another project, it should be fine advice. If he just wants to disable the GPU on Einstein, then the separate venue is the way to go, bar an app_info.xml that doesn't include a GPU app on that system.
A little more experimentation has shown that that I can temporarily shut off BOINC's use of the GPU by telling it to wait a large amount of time, such as 3600 minutes, between my last use of the keyboard and the time it starts using the GPU. That is enough to allow me to use both CPU cores at the usual 60% of full speed for laptops. Or, if I prefer, I can enable GPU use but leave the CPU running so slowly that it seldom completes any CPU workunits at all by their deadlines.
At this moment, it looks better to try the cc_config method for turning off BOINC GPU use more permanently, and seeing if that's enough to stop asking for GPU workunits from ANY BOINC project, and then waiting until it gets one before it even tries to get any CPU workunits.
Although Einstein@Home is the best choice for GPU workunits that GPU can handle, it currently looks like shutting off any BOINC GPU use at all is the best choice. This may change if I learn enough about Rivatuner to slow down the GPU without too many problems.
TThrottle does not appear to offer any other workable way to limit the GPU temperature more than the CPU temperature.
At this moment, it looks better to try the cc_config method for turning off BOINC GPU use more permanently, and seeing if that's enough to stop asking for GPU workunits from ANY BOINC project, and then waiting until it gets one before it even tries to get any CPU workunits.
Make sure to exit & restart BOINC after you added the option. A mere re-reading of the config file isn't going to help as GPU detection decisions are made at BOINC start-up, not some place in the middle.
When using the option or any of the options, there will only be CPU work requests. Just so you know.
The newest versions of BOINC also have an option in the Control (? Steuerung in German) menu of BOINC manager where you can selectively (and only for that host) disable CPU computing, GPU computing and Networking (it used to be only Computing in general and networking). You can select either "always", "never" or "according to preferences".
I guess if you want to disable GPU on (say) a notebook, that's simpler than going thru the venue configuration.
Looks like I need to find more about the typical deadlines for the Einstein@Home workunits, and then decide if it's worth switching back and forth between a mode where it will fetch GPU workunits but not run them, and a mode where it will try to run both GPU workunits and CPU workunits, but the CPU workunits are unlikely to run fast enough.
Looks like I need to find more about the typical deadlines for the Einstein@Home workunits, and then decide if it's worth switching back and forth between a mode where it will fetch GPU workunits but not run them, and a mode where it will try to run both GPU workunits and CPU workunits, but the CPU workunits are unlikely to run fast enough.
that's on of those very bright things deep inside the boinc client - if you run a project which has both cpu and gpu work, it will just get crazy and keep crazy about work fetch.
you will never sort it out with a current client-version unless you decide to limit a project to either cpu or gpu crunching.. :(
Looks like I need to find more about the typical deadlines for the Einstein@Home workunits, and then decide if it's worth switching back and forth between a mode where it will fetch GPU workunits but not run them, and a mode where it will try to run both GPU workunits and CPU workunits, but the CPU workunits are unlikely to run fast enough.
that's on of those very bright things deep inside the boinc client - if you run a project which has both cpu and gpu work, it will just get crazy and keep crazy about work fetch.
you will never sort it out with a current client-version unless you decide to limit a project to either cpu or gpu crunching.. :(
What I'm currently planning to do on my laptop is alternate between those states for a while, with Einstein@Home the only BOINC project enabled. If that causes too many problems, I'll have to try something else.
But on the other hand, if
)
But on the other hand, if Robert wants to use that GPU on another project, it should be fine advice. If he just wants to disable the GPU on Einstein, then the separate venue is the way to go, bar an app_info.xml that doesn't include a GPU app on that system.
A little more experimentation
)
A little more experimentation has shown that that I can temporarily shut off BOINC's use of the GPU by telling it to wait a large amount of time, such as 3600 minutes, between my last use of the keyboard and the time it starts using the GPU. That is enough to allow me to use both CPU cores at the usual 60% of full speed for laptops. Or, if I prefer, I can enable GPU use but leave the CPU running so slowly that it seldom completes any CPU workunits at all by their deadlines.
At this moment, it looks better to try the cc_config method for turning off BOINC GPU use more permanently, and seeing if that's enough to stop asking for GPU workunits from ANY BOINC project, and then waiting until it gets one before it even tries to get any CPU workunits.
Although Einstein@Home is the best choice for GPU workunits that GPU can handle, it currently looks like shutting off any BOINC GPU use at all is the best choice. This may change if I learn enough about Rivatuner to slow down the GPU without too many problems.
TThrottle does not appear to offer any other workable way to limit the GPU temperature more than the CPU temperature.
RE: At this moment, it
)
Make sure to exit & restart BOINC after you added the option. A mere re-reading of the config file isn't going to help as GPU detection decisions are made at BOINC start-up, not some place in the middle.
When using the option or any of the options, there will only be CPU work requests. Just so you know.
Hi! The newest versions of
)
Hi!
The newest versions of BOINC also have an option in the Control (? Steuerung in German) menu of BOINC manager where you can selectively (and only for that host) disable CPU computing, GPU computing and Networking (it used to be only Computing in general and networking). You can select either "always", "never" or "according to preferences".
I guess if you want to disable GPU on (say) a notebook, that's simpler than going thru the venue configuration.
CU
HBE
This is in the Activity menu,
)
This is in the Activity menu, the option for the GPU is Suspend GPU, but this won't stop the work requests for the GPU.
Here's what mine writes when I suspend the GPU:
03/08/2011 12:10:02 | | [cpu_sched_debug] Request CPU reschedule: GPU mode changed
03/08/2011 12:10:50 | Docking | [work_fetch] request: CPU (640.92 sec, 2.00 inst) ATI (25920.00 sec, 1.00 inst)
03/08/2011 12:10:50 | Docking | Sending scheduler request: Requested by user.
03/08/2011 12:10:50 | Docking | Requesting new tasks for CPU and ATI
03/08/2011 12:10:50 | Docking | [sched_op] CPU work request: 640.92 seconds; 2.00 CPUs
03/08/2011 12:10:50 | Docking | [sched_op] ATI work request: 25920.00 seconds; 1.00 CPUs
03/08/2011 12:10:57 | Docking | Scheduler request completed: got 0 new tasks
03/08/2011 12:10:57 | Docking | [sched_op] Server version 603
03/08/2011 12:10:57 | Docking | Project requested delay of 3 seconds
As you can see, work requests for the GPU continue without ado.
Looks like I need to find
)
Looks like I need to find more about the typical deadlines for the Einstein@Home workunits, and then decide if it's worth switching back and forth between a mode where it will fetch GPU workunits but not run them, and a mode where it will try to run both GPU workunits and CPU workunits, but the CPU workunits are unlikely to run fast enough.
RE: Looks like I need to
)
that's on of those very bright things deep inside the boinc client - if you run a project which has both cpu and gpu work, it will just get crazy and keep crazy about work fetch.
you will never sort it out with a current client-version unless you decide to limit a project to either cpu or gpu crunching.. :(
RE: RE: Looks like I need
)
What I'm currently planning to do on my laptop is alternate between those states for a while, with Einstein@Home the only BOINC project enabled. If that causes too many problems, I'll have to try something else.