Error al limitar el número de procesadores con tareas multiprocesador (Failed to limit the number of processors with multiprocessor tasks)

Message boards : Questions and problems : Error al limitar el número de procesadores con tareas multiprocesador (Failed to limit the number of processors with multiprocessor tasks)
Message board moderation

To post messages, you must log in.

AuthorMessage
Juan M. PdC

Send message
Joined: 6 Mar 14
Posts: 4
Spain
Message 54025 - Posted: 8 May 2014, 17:15:20 UTC

En primer lugar, vuelvo a pedir disculpas por escribir en español, pero mi nivel de inglés sigue siendo mínimo.

Proceso con Windows_7 x64 y 8 núcleos, utilizando la versión 7.2.42 x64 de BOINC.

Tengo puestas las preferencias para que Boinc use sólo el 50% de los procesadores, es decir, sólo 4 de los 8 que tengo. Esto ha funcionando correctamente hasta que me ha llegado una tarea multiprocesador de Collatz (Supongo que ocurrirá tambien con otros proyectos)

En la columna "Estado" indica "Ejecutando (4 CPUs)", pero el Administrador de tareas de Windows muestra el proceso utilizando el 99-100% de CPU. Pulsando el botón "Propiedades" de la tarea de Boinc Manager, el "Tiempo de CPU" viene a ser el "Tiempo transcurrido" multiplicado por 8. Es más; cuando la tarea se pone en estado "Esperando para ejecutar" o si se suspende la tarea, sus columnas de porcentaje de "Progreso" y el tiempo "Restante (estimado)" siguen variando, y en el Administrador de tareas de Windows sigue apareciendo un proceso Collazt usando más o menos el 50% de CPU mientras el resto de proyectos completan el 100% de CPU usando cada uno entre el 12% y el 13%, que es lo normal.

Espero haberme explicado suficientemente claro, y que os sirva para algo las indicaciones.

Un saludo y gracias por todo,

Juan M. PdC



Translation into English by Google

First, I again apologize for writing in Spanish , but my English is still minimal .

Process Windows_7 x64 and 8 cores , using BOINC 7.2.42 x64 version .

I have set the preferences to use Boinc only 50% of the processors , ie , only 4 of the 8 I have. This has been working properly until I have received a multiprocessor task Collatz ( I guess also occur with other projects )

In the "Status" column indicates "Executing ( 4 CPUs ) ," but the Windows Task Manager shows the process using 99-100 % of CPU. . Pressing the "Properties " button on the task of Boinc Manager , the " CPU Time " is to be multiplied by 8 " Elapsed Time" is more ; when the task is put in " Waiting to run " or if the task is suspended , its columns of percentage of " Progress" and the time " remaining (estimated) " still vary , and in the Windows Task Manager still see an Collazt process using roughly 50% of CPU while the other projects completed 100% of CPU each using between 12% and 13% , which is normal .

I hope I explained clearly enough , and that I may do some indications .

A greeting and thanks for everything,

Juan M. PdC
ID: 54025 · Report as offensive
Juan M. PdC

Send message
Joined: 6 Mar 14
Posts: 4
Spain
Message 54044 - Posted: 10 May 2014, 11:08:06 UTC - in response to Message 54025.  

Esto ha funcionando correctamente hasta que me ha llegado una tarea multiprocesador de Collatz (Supongo que ocurrirá tambien con otros proyectos)

Rectifico: Me acaba de llegar una tarea multiprocesador de Yafu y no ocurre lo mismo. Estando en estado "Ejecutando (4 CPUs)", en el Administrador de Windows aparecen 4 tareas (ecm.exe) cada una de ellas con el 12-13% de CPU: "Suspendida" o "Esperando para ejecutar" la CPU aparece al 50% y 4 tareas no-Yafu usando el 12-13%.

Saludos,


This has been working properly until I have received a multiprocessor task Collatz ( I guess it also occur with other projects )

Rectified: I just got Yafu multiprocessor task and it is not so. Being in "Running (4 CPUs)," Manager in Windows shows 4 tasks (ecm.exe) each with 12-13% CPU "suspended" or "Waiting to run" appears when the CPU 50% and 4 tasks no-Yafu using 12-13%.

regards,
ID: 54044 · Report as offensive
mo.v
Avatar

Send message
Joined: 13 Aug 06
Posts: 778
United Kingdom
Message 54066 - Posted: 12 May 2014, 0:42:56 UTC
Last modified: 12 May 2014, 0:43:52 UTC

Hola Juan

Perdóneme el retraso en contester pero he estado fuera durante un mes.

Si no me equivoco, resulta que estas tareas multiprocesador de Collatz no respetan lo que Ud ha mandado en las Preferencias en la pestaña de Utilización de los Procesadores.

He buscado su cuenta en el proyecto Collatz para descubrir cuales son las tareas que le dan este problema y quizás intentar reproducirlo en mi ordinador, pero veo que sus ordinador(es) están amagados:

http://boinc.thesonntags.com/collatz/show_user.php?userid=50875

¿Cómo se llaman las tareas problemáticas?

¿Ha explicado el problema en el foro Collatz?

¿Podría por favor cambiar sus preferencias i en lugar de limitar el número de procesadores al 50%, poner esta cifra al 100% y limitar el tiempo de CPU al 50%, a ver lo que pasa entonces?

------------------------------------------------------------------------

Juan has found that his Collatz multiprocessor tasks do not respect his Preferences setting of 50% of CPUs, according to which his tasks should use only 4 CPUs of the 8 available. He has found by checking Windows Task Manager that these tasks use 100% of all 8 CPUs. This situation is further demonstrated by the fact that when he opens the Properties button of one of these tasks the CPU time shown there is the Elapsed time X 8.

In addition, when one of these tasks is waiting to run or suspended, the elapsed and remaining times continue to change, and Task Manager shows 50% usage.

He has found that Yafu multiprocessor tasks do respect his preferences regarding % of CPUs.

I have looked at Juan's Collatz account in the hope of identifying which application type he's been running, which might allow me to attempt to reproduce the problem on my own computer. But his computer(s) are hidden.

I've asked:

* the name of the problem task types

* whether he's asked about this on the Collatz forum

* whether in his preferences he could reduce CPU time to 50% instead of limiting the number of processors to 50%, to see whether the effect is the same.
ID: 54066 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 54069 - Posted: 12 May 2014, 8:07:50 UTC
Last modified: 12 May 2014, 8:10:17 UTC

Juan talks of receiving "a multiprocessor task", and that corresponds with "Executing ( 4 CPUs )". BOINC refers to these as either 'multicore' or 'multithread' applications.

But looking at the Collatz Applications page, they have no apps defined with an 'MT' plan class. It's possible that Jon hasn't quite got the hang of sending/handling the --nthreads N parameter from http://boinc.berkeley.edu/trac/wiki/AppPlan.

There are very few MT projects around, so not much experience for project admins to draw on - but it sounds as if Yafu have got it right, and could maybe help (except their website is unreachable, because they haven't renewed their domain name).

Edit - it would be best to stick with limiting the number of processors, and work with Jon to debug the plan_class problem.
ID: 54069 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 54071 - Posted: 12 May 2014, 9:30:51 UTC - in response to Message 54070.  

collatz opencl cpu apps keep running if the "leave in memory" box is checked in the computer pref. and the way the app is it will take or try to take 100% of the cpus (cores) no matter what the setting, in otherwords it is an mt app.

Well, it functions by using multiple cores, certainly, but not in the way that BOINC defines an MT app (from that description). What does Process Explorer say while the app is running - does it show additional threads spawned (one per core), the way AQUA and MilkyWay MT apps do? Or does it operate by launching microkernels, like a GPU?

so collatz has a little bit of work to do.

And possibly BOINC as well, to add a predefined opencl_cpu plan class which supports processor %age in the way that MT's nthreads does.
ID: 54071 · Report as offensive
mo.v
Avatar

Send message
Joined: 13 Aug 06
Posts: 778
United Kingdom
Message 54073 - Posted: 12 May 2014, 9:57:59 UTC

The problem isn't only Collatz. I have a laptop with an i7 and 8 cores but I can only allow one core to crunch in order to keep the CPU temp down. I use it for CPDN, and also Einstein NVidia tasks because it has a good GPU.

If I set the CPU % to 12.5% that should limit the number of cores to one (though in fact Windows spreads the usage over 4 cores for temperature management). While only a climate model is running Task Manager shows CPU usage fluctuating round 12.5%.

When an Einstein GPU task using 0.2 of CPU kicks in, the total usage goes up to around 14.5 or 15%. This is not what I specified. It sends CPU temperature above what I want and should not happen. The only way I can keep the temperature down while using both CPU and GPU is by also limiting CPU time to 85%.

I don't think it's fair to expect participants to fiddle around with the effect of these settings while also studying what happens to the CPU and GPU temperatures.
ID: 54073 · Report as offensive
Juan M. PdC

Send message
Joined: 6 Mar 14
Posts: 4
Spain
Message 54204 - Posted: 20 May 2014, 18:41:57 UTC - in response to Message 54074.  

Por lo que veo, efectivamente es un problema de Collatz (No puedo indicaros que tipo de tarea es porque ya está borrada del historial en Collatz) Ahora mismo tengo una tarea de BURP también multicore y también funciona correctamente.

No abrí un hilo en Collatz porque pensé que era un problema de Boinc; perdón por las molestias.

Gracias por las respuestas.



From what I see, it is indeed a problem Collatz (I can not point out to you what kind of task is deleted because it is already history in Collatz) Right now I have a task of multicore and BURP also works correctly.

I did not open a thread in Collatz because I thought it was a problem of Boinc; sorry for the inconvenience.

Thanks for the replies.
ID: 54204 · Report as offensive

Message boards : Questions and problems : Error al limitar el número de procesadores con tareas multiprocesador (Failed to limit the number of processors with multiprocessor tasks)

Copyright © 2024 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.