Desdoblar botón "No pedir nuevas tareas" para CPU y GPU [Unfold "Do not ask for new tasks" button for CPU and GPU]

Message boards : BOINC Manager : Desdoblar botón "No pedir nuevas tareas" para CPU y GPU [Unfold "Do not ask for new tasks" button for CPU and GPU]
Message board moderation

To post messages, you must log in.

AuthorMessage
[Bro.Inc] AdM

Send message
Joined: 10 Nov 17
Posts: 1
Message 82878 - Posted: 10 Nov 2017, 12:23:17 UTC

Desdoblar el botón "No pedir nuevas tareas" diferenciando CPU y GPU simplificaría muchísimo el poder controlar qué proyecto y en qué ordenador quieres que se ejecuten tareas GPU. Desmarcar el uso de GPU en la web de cada proyecto es engorroso y afecta a todos los ordenadores. Suspender el uso de GPU en el menú del Boinc Manager afecta a todos los proyectos (y no deja de pedir tareas GPU, sólo las deja suspendidas).

Sé que se puede (aunque desconozco cómo) crear archivos de configuración para cada proyecto, pero me parece una opción complicada y farragosa para ir cambiando el proyecto con el que quieres procesar con la GPU.

Creo que desdoblar dicho botón sería la opción óptima.

Graicas y un saludo,

[Bro.Inc] AdM

p.d. Siento no poder escribir en inglés, y pido disculpas si este tema ya se ha tratado en otro hilo


[Google translator]
Unfolding the "Do not ask for new tasks" button, differentiating CPUs and GPUs, would make it very easy to control which project and which computer you want to run GPU tasks on. Unchecking the use of GPUs on the web of each project is cumbersome and affects all computers. Suspending the use of GPU in the Boinc Manager menu affects all projects (and does not stop asking for GPU tasks, it only leaves them suspended).

I know that it is possible (although I do not know how) to create configuration files for each project, but I find it a complicated and cumbersome option to change the project with which you want to process with the GPU.

I think that unfolding this button would be the optimal option.

Thanks and best regards,

[Bro.Inc] AdM

P.S. I am sorry I can not write in English, and I apologize if this topic has already been dealt with in another thread
ID: 82878 · Report as offensive     Reply Quote
SekeRob
Volunteer tester
Help desk expert

Send message
Joined: 25 Aug 06
Posts: 1596
Message 82881 - Posted: 10 Nov 2017, 13:58:12 UTC - in response to Message 82878.  

For this to be implemented at the client side, it probably surely also requires implementation at the project side (many). Right now the switch is "send work of any type that's allowed to be sent under the location profile that's linked to the device". The limitation is, if a location profile is told by the client to not sent GPU or CPU work, all your other devices connected to that location profile will also start not receiving the type of work from that project.

IIRC, there used to be app_info.xml that directly inserted itself into the server scheduler process, but think projects (I know WCG for sure), have/had a seriously dislike of this incursion, which is when app_config.xml as a processing control was born.
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 82881 · Report as offensive     Reply Quote

Message boards : BOINC Manager : Desdoblar botón "No pedir nuevas tareas" para CPU y GPU [Unfold "Do not ask for new tasks" button for CPU and GPU]

Copyright © 2018 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.