Mike, I am happy to work on pulsar searches. I believe every bit of science data gathered is beneficial. I will continue to crunch data for whatever GPU application E@H projects can provide. I find your comment about GW crunching mandatory amusing when the project preferences page itself has the option to not use the CPU which has been set to No for as long as I have attached to the project. Curious as to why that option hasn't been removed if mandatory CPU use is required if attached to the project.
Until the time that the BOINC Manager is completely rewritten to accommodate GPU usage for processing multiple simultaneous tasks, I am forced to use an app_info even though that was not its original intended purpose.
Saw in another thread someone's solution to the automatic 4 hour backoff. Run a CRON job in Linux or Schedule a Task in Windows. I have setup such a task to run and update every hour in the hope that I can continue to grab BRP4 work when it becomes available.
Cheers, Keith
Keith you will clearly act as you see fit, as is your choice. But it remains true that 'Gravitational Wave S6 GC search' option is greyed out, and you have chosen to use an app_info.xml workaround plus clever optioning and time fiddling on the client host to subvert project intentions. I am bound to point out that this is not project policy ... and we both know that you are precisely aware of this aspect. Do you recommend that we should close that loophole then ? Now that you have demonstrated that so clearly for us, I will refer this matter upwards .... :-) :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
My laptop has a different problem with the current setup. Although it has 2 CPU cores and a GPU, it cannot run all three at once without overheating. I've tried TThrottle for slowing it down; that prefers to slow down the CPU instead of the GPU, and so much that few of the CPU workunits meet their deadlines. I'm now draining all the workunits on it to prepare for a few changes, which MIGHT include telling it to only run Einstein@Home CPU workunits for a while - and might not.
My laptop has a different problem with the current setup. Although it has 2 CPU cores and a GPU, it cannot run all three at once without overheating. I've tried TThrottle for slowing it down; that prefers to slow down the CPU instead of the GPU, and so much that few of the CPU workunits meet their deadlines. I'm now draining all the workunits on it to prepare for a few changes, which MIGHT include telling it to only run Einstein@Home CPU workunits for a while - and might not.
Yup, same here: whenever room temps get slighty over normal (say 20 deg Celsius), my notebook will throttle down under full load as well.
You might want to use the "local" settings in the BOINC Manager on that notebook to (say) tell it to use only some of the CPU cores. That will not slow down the GPU and might be sufficient to keep the notebook at a reasonable temp.
My laptop has a different problem with the current setup. Although it has 2 CPU cores and a GPU, it cannot run all three at once without overheating. I've tried TThrottle for slowing it down; that prefers to slow down the CPU instead of the GPU, and so much that few of the CPU workunits meet their deadlines. I'm now draining all the workunits on it to prepare for a few changes, which MIGHT include telling it to only run Einstein@Home CPU workunits for a while - and might not.
That is another possibility, but if you limit the performance of the GPU e.g. by forcing a lower clock rate, that will of course affect your whole user experience with that notebook, also for other applications. Probably not what you want. If you instead just tell BOINC to run less than the max number of possible CPU tasks, it will reduce the heat generated by BOINC but will not affect other applications.
My laptop has a different problem with the current setup. Although it has 2 CPU cores and a GPU, it cannot run all three at once without overheating. I've tried TThrottle for slowing it down; that prefers to slow down the CPU instead of the GPU, and so much that few of the CPU workunits meet their deadlines. I'm now draining all the workunits on it to prepare for a few changes, which MIGHT include telling it to only run Einstein@Home CPU workunits for a while - and might not.
Yup, same here: whenever room temps get slighty over normal (say 20 deg Celsius), my notebook will throttle down under full load as well.
You might want to use the "local" settings in the BOINC Manager on that notebook to (say) tell it to use only some of the CPU cores. That will not slow down the GPU and might be sufficient to keep the notebook at a reasonable temp.
HBE
I've already tried telling it to use only one of its two CPU cores. That did not reduce the temperature enough. I then added TThrottle, and set the temperature limits I wanted (about 94C for both the CPU and the GPU). That slowed down the CPU so much that it seldom completed CPU workunits by their deadlines. Raising the CPU temperature limit to 95 C essentially shut off both temperature limits. Looks like I need still more things to try, and I've decided to try a BOINC update next.
Room temperature now around 75 F here most of the time.
Is there any way I can tell BOINC on my laptop not to use the GPU even if it finds a suitable one? It looks like you currently need CPU workunits done, but can't generate GPU workunits fast enough to keep up with the demand. That GPU happens to be one close to the low end of what you can use anyway.
When I told it to switch Einstein@Home on that laptop to CPU workunits only, it refused to download CPU workunits at all until I got a GPU workunit from another BOINC project. I doubt if you want Einstein@Home CPU workunits to be the ones slowed down so much they will not meet the deadlines.
Is there any way I can tell BOINC on my laptop not to use the GPU even if it finds a suitable one? It looks like you currently need CPU workunits done, but can't generate GPU workunits fast enough to keep up with the demand. That GPU happens to be one close to the low end of what you can use anyway.
I had a GPU issue with my laptop and the suggestion that worked for me was to put it in the "school" group and deselect the GPU tasks for that group.
This is on the "preferences for this project" in the home account page.
RE: Mike, I am happy to
)
Keith you will clearly act as you see fit, as is your choice. But it remains true that 'Gravitational Wave S6 GC search' option is greyed out, and you have chosen to use an app_info.xml workaround plus clever optioning and time fiddling on the client host to subvert project intentions. I am bound to point out that this is not project policy ... and we both know that you are precisely aware of this aspect. Do you recommend that we should close that loophole then ? Now that you have demonstrated that so clearly for us, I will refer this matter upwards .... :-) :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
My laptop has a different
)
My laptop has a different problem with the current setup. Although it has 2 CPU cores and a GPU, it cannot run all three at once without overheating. I've tried TThrottle for slowing it down; that prefers to slow down the CPU instead of the GPU, and so much that few of the CPU workunits meet their deadlines. I'm now draining all the workunits on it to prepare for a few changes, which MIGHT include telling it to only run Einstein@Home CPU workunits for a while - and might not.
RE: My laptop has a
)
Yup, same here: whenever room temps get slighty over normal (say 20 deg Celsius), my notebook will throttle down under full load as well.
You might want to use the "local" settings in the BOINC Manager on that notebook to (say) tell it to use only some of the CPU cores. That will not slow down the GPU and might be sufficient to keep the notebook at a reasonable temp.
HBE
RE: My laptop has a
)
you could try riva-tuner - http://www.guru3d.com/index.php?page=rivatuner.
it will allow you to control the clocks on your GPU.
the user inteface is quite tricky, but it works..
That is another possibility,
)
That is another possibility, but if you limit the performance of the GPU e.g. by forcing a lower clock rate, that will of course affect your whole user experience with that notebook, also for other applications. Probably not what you want. If you instead just tell BOINC to run less than the max number of possible CPU tasks, it will reduce the heat generated by BOINC but will not affect other applications.
HBE
RE: RE: My laptop has a
)
I've already tried telling it to use only one of its two CPU cores. That did not reduce the temperature enough. I then added TThrottle, and set the temperature limits I wanted (about 94C for both the CPU and the GPU). That slowed down the CPU so much that it seldom completed CPU workunits by their deadlines. Raising the CPU temperature limit to 95 C essentially shut off both temperature limits. Looks like I need still more things to try, and I've decided to try a BOINC update next.
Room temperature now around 75 F here most of the time.
Is there any way I can tell
)
Is there any way I can tell BOINC on my laptop not to use the GPU even if it finds a suitable one? It looks like you currently need CPU workunits done, but can't generate GPU workunits fast enough to keep up with the demand. That GPU happens to be one close to the low end of what you can use anyway.
When I told it to switch Einstein@Home on that laptop to CPU workunits only, it refused to download CPU workunits at all until I got a GPU workunit from another BOINC project. I doubt if you want Einstein@Home CPU workunits to be the ones slowed down so much they will not meet the deadlines.
RE: Is there any way I can
)
If you want BOINC to not use the GPU on any project, you can create (or modify) a cc_config.xml file with the option set to one.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: Is there any way I can
)
I had a GPU issue with my laptop and the suggestion that worked for me was to put it in the "school" group and deselect the GPU tasks for that group.
This is on the "preferences for this project" in the home account page.
Joe
Yes, but you'll have to do
)
Yes, but you'll have to do that for every project that offers GPU applications.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
