I have some new PCs but there are really noisy when crunching data even with only one CPU task running.
Is there a way to run only GPU tasks with no CPU running ?

---

Bonjour, bien sûr il suffit de désactiver le CPU dans les préférences de Seti@home https://setiathome.berkeley.edu/prefs.php?subset=project

décocher " utiliser le CPU "

puis dans Boinc Manager cliquer dans l'onglet Projets sur Seti@home et faire une mise a jour ;)

---

Thanks but it doesn't work
I put this snew computer in another group 'Work' (different from others computers).
Then I have edited 'Separate preferences for work' to untick 'CPU'
Last, I have updated project in boincmgr....but still using CPU tasks

I suppose it should be related to global_prefs.xml and global_prefs_override.xml file.

---

en effet Boinc ne téléchargera plus d'unité CPU mais finira celles en cours ;)

dans ce cas vous pouvez les annuler si besoin .

---

You should be able to configure the preferences to not use the cpu for tasks. If that is impossible you can always brute force it and run anonymous platform and simply remove the cpu apps.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

My Asteroids@home tasks use a 0.01 CPU plus a NVIDIA GTX 1050 Ti with cuda 55. I don't know what would happen if I blocked the CPU usage.
Tullio

---

Thanks but it doesn't work
I put this snew computer in another group 'Work' (different from others computers).
Then I have edited 'Separate preferences for work' to untick 'CPU'
Last, I have updated project in boincmgr....but still using CPU tasks

It may finish any current tasks but should not get any new ones. I've done this on a few machines and it works...

---

Thanks.
To be more precise, I would like to process CPU tasks only the night and no CPU tasks during the day.
So if the server doesn't send any more CPU tasks, it will not work as I would like.

---

Thanks.
To be more precise, I would like to process CPU tasks only the night and no CPU tasks during the day.
So if the server doesn't send any more CPU tasks, it will not work as I would like.

Maybe you could use BoincTask to do this.
This manager have Rules that could be used to suspend boincapps by the applevel on walltime.
Backdraw for you - its a Windows program - but it should work under Wine

https://forum.efmer.com/index.php?board=29.0

or you could use a sheduled dymmy program and use
<exclusive_app>filename.exe</exclusive_app>
BOINC will suspend computing whenever the executable is running (e.g., a game). Case is ignored in filenames. Multiple applications can be specified: place each <exclusive_app>filename.exe</exclusive_app> on a separate line.
<exclusive_gpu_app>important.exe</exclusive_gpu_app>
BOINC will suspend use of GPUs whenever the executable is running.
I am not an *nix person (yet)

Moving the CPU apps is a good idea ! It may generate a lots of error in boinc but it can solve my problem to suspend
CPU tasks during the day (you can suspend GPU tasks, but not CPU).
Thanks for your help !

---

Hi Lazydude2

Maybe you could use BoincTask to do this.
This manager have Rules that could be used to suspend boincapps by the applevel on walltime.
Backdraw for you - its a Windows program - but it should work under Wine

BOINCTasks does indeed run in Wine on Linux. I'm running it on Linux Mint 19.2.

Here's a forum post explaining how to install BOINCTasks in Wine on Linux. This is what I followed. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Moving the CPU apps is a good idea ! It may generate a lots of error in boinc but it can solve my problem to suspend
CPU tasks during the day (you can suspend GPU tasks, but not CPU).
Thanks for your help !

Hmmm...in fact, not a good idea. If I rename the CPU app, boinc discard all CPU tasks .
When I put back the CPU app, all CPU tasks have disappeared.

I can't use BOINCTasks as the CPU use should be triggered by a script (off the day/on the night).

Answers found :
1) disable CPU task from the web interface....but it means no CPU tasks at all
2) leave only one CPU running with setting the right value in max_ncpus_pct (global_prefs_override.xml)

It seems there is no way to enable/disable all CPU tasks as you can do with GPU.

---

Moving the CPU apps is a good idea ! It may generate a lots of error in boinc but it can solve my problem to suspend
CPU tasks during the day (you can suspend GPU tasks, but not CPU).
Thanks for your help !

Hmmm...in fact, not a good idea. If I rename the CPU app, boinc discard all CPU tasks .
When I put back the CPU app, all CPU tasks have disappeared.

I can't use BOINCTasks as the CPU use should be triggered by a script (off the day/on the night).

Answers found :
1) disable CPU task from the web interface....but it means no CPU tasks at all
2) leave only one CPU running with setting the right value in max_ncpus_pct (global_prefs_override.xml)

It seems there is no way to enable/disable all CPU tasks as you can do with GPU.

Add that to a Issue at Github for BOINC with the "Feature Request" tag and hope for one of the developers to pick up the issue and run with it. This is one I put in a long time ago.
https://github.com/BOINC/boinc/issues/2085

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Add that to a Issue at Github for BOINC with the "Feature Request" tag and hope for one of the developers to pick up the issue and run with it. This is one I put in a long time ago.
https://github.com/BOINC/boinc/issues/2085

Better yet, add it to https://github.com/BOINC/boinc/issues/41 - the second-oldest unimplemented open feature request in the whole repository (12 years and counting). Many other people have re-invented that particular wheel over the decades, but we're trying to consolidate on the mother lode.

Add that to a Issue at Github for BOINC with the "Feature Request" tag and hope for one of the developers to pick up the issue and run with it. This is one I put in a long time ago.
https://github.com/BOINC/boinc/issues/2085

New feature added but I don't think it will be available before boinc 7.20 ;)

---

Add that to a Issue at Github for BOINC with the "Feature Request" tag and hope for one of the developers to pick up the issue and run with it. This is one I put in a long time ago.
https://github.com/BOINC/boinc/issues/2085

Better yet, add it to https://github.com/BOINC/boinc/issues/41 - the second-oldest unimplemented open feature request in the whole repository (12 years and counting). Many other people have re-invented that particular wheel over the decades, but we're trying to consolidate on the mother lode.

sorry, I've added the feature request before you write your post !

---

sorry, I've added the feature request before you write your post !

That's OK, I've added cross-references to #41 and #2993. I've also (I think) demolished David's knee-jerk reaction.

sorry, I've added the feature request before you write your post !

That's OK, I've added cross-references to #41 and #2993. I've also (I think) demolished David's knee-jerk reaction.

:)
Different CPU profiles is a good idea !

---

An idea:
Use two app_config.xml
with <project_max_concurrent>X</project_max_concurrent>

X=number GPU-tasks

ie
Appconfig DAY X=1
Appconfig Night X=24

and with script change what appconf you want to use.
AND do a restart of boinc or --read_cc_config with https://boinc.berkeley.edu/wiki/Boinccmd_tool
My appconfig loos like this:
<!-- SETI -->

<app_config>
<app>
<name>setiathome_v8</name>

<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.05</cpu_usage>

</gpu_versions>

</app>

<app>
<name>astropulse_v7</name>

<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>1.0</cpu_usage>



</gpu_versions>
</app>

<!-- <project_max_concurrent>12</project_max_concurrent> -->

</app_config>
<!-- <report_results_immediately/> <project_max_concurrent>8</project_max_concurrent> <fraction_done_exact/> -->

Then you dont trash any WU
Also take a look att https://boinc.berkeley.edu/wiki/Client_configuration
Just an idea

Lazy

An idea:
Use two app_config.xml
with <project_max_concurrent>X</project_max_concurrent>
Lazy

Works great with <project_max_concurrent> !!! :)

Set to 1 to get the GPU running without CPU
Set to 4 to get the GPU running and 3 CPU tasks

All I need is to reload the app_config.xml file using :
./boinccmd --read_cc_config

One question : when I set value to 1, how boinc know it should be the GPU tasks which should remains running ?

PS: I've tried adding <max_concurrent> and restart boinc but it doesn't seems to work.

<app>
<name>setiathome_v8</name>
</app>
<file_info>
<name>MBv8_8.05r3345_avx_linux64</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>805</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<cmdline></cmdline>
<max_concurrent>1<max_concurrent>
<file_ref>
<file_name>MBv8_8.05r3345_avx_linux64</file_name>
<main_program/>
</file_ref>
</app_version>

---