Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: OpenPandemics GPU Beta Test - March 12 2021 [ Issues Thread ] |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 160
|
Author |
|
ca05065
Senior Cruncher Joined: Dec 4, 2007 Post Count: 325 Status: Offline Project Badges: |
I was using the priority shown in Process Explorer. I could not find a display of priority in Task Manager.
|
||
|
goben_2003
Advanced Cruncher Joined: Jun 16, 2006 Post Count: 145 Status: Offline Project Badges: |
You can change the priority level of the cpu and gpu tasks independently in cc_config.xml. Tasks started after you make the changes and have boinc read config files will have the new priority level.
----------------------------------------From BOINC client configuration: <process_priority>N</process_priority>, <process_priority_special>N</process_priority_special> The OS process priority at which tasks are run. Values are 0 (lowest priority, the default), 1 (below normal), 2 (normal), 3 (high) and 4 (highest). 'Special' process priority is used for coprocessor (GPU) applications, wrapper applications, and non-compute-intensive applications, 'process priority' for all others. The two options can be used independently. |
||
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2068 Status: Offline Project Badges: |
A CPU only work unit runs with a priority of 4 and normal windows task with a priority of 8. That's interesting. Checking this morning, my CPU tasks are running with a priority of 1. That's with a generic BOINC client (v7.16.11) setting the priorities as the apps launch, under Windows 7.My CPU task priority in Process Explorer for MCM tasks is Idle: 4, on windows 7, Boinc 7.16.7. I haven't got any OPN1 tasks to check if those are different. I can't see any priority 1 option at all in Process Explorer. Process Explorer only lists Idle 4, Background 4, Below Normal 6, Normal 8, Above Normal 10, High 13, and Realtime 24. [Edit 4 times, last edit by Grumpy Swede at Mar 15, 2021 11:32:33 AM] |
||
|
Richard Haselgrove
Senior Cruncher United Kingdom Joined: Feb 19, 2021 Post Count: 360 Status: Offline Project Badges: |
I was using the priority shown in Process Explorer. I could not find a display of priority in Task Manager. So was I. |
||
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2068 Status: Offline Project Badges: |
I was using the priority shown in Process Explorer. I could not find a display of priority in Task Manager. So was I.Edit: @Richard:Well, that was not the tab I used, I was using the Performance tab, where it states Priority 4. |
||
|
Richard Haselgrove
Senior Cruncher United Kingdom Joined: Feb 19, 2021 Post Count: 360 Status: Offline Project Badges: |
|
||
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2068 Status: Offline Project Badges: |
|
||
|
sam6861
Advanced Cruncher Joined: Mar 31, 2020 Post Count: 107 Status: Offline Project Badges: |
The CPU part used 100% of a thread while the GPU percentage jumped between low values and 100%. I have noticed the same things on my NVidia GPU. Ryzen 2700x, Win 10, NVidia GT 1030, 0.61 / 0.62 hours. (98%) Ryzen 2700x, Win 10, AMD 5500 XT, 0.08 / 0.16 hours. (50%) Ryzen 3900x, Win 10, AMD RX 550, 0.05 / 0.49 hours. (10%) Intel i7 2600, Win 10, AMD RX 580, 0.07 / 0.21 hours. (33%) Look at how high NVidia CPU is for slow NVidia GT 1030. This appears to be a problem with NVidia OpenCL using a spin lock wasting CPU. AMD GPU appears to free up CPU and wait for IRQ (interrupt request) from GPU. There are some possible workarounds, search the internet, NVidia OpenCL 100% CPU workaround. I use Process Hacker tool, it can check and change thread priority with right click of a thread. The previous beta had GPU thread run at idle priority, and that slowed down my AMD GPU when CPU is maxed out by CPU tasks. This March 12 beta use normal thread priority and it ran faster for my AMD GPU. |
||
|
Richard Haselgrove
Senior Cruncher United Kingdom Joined: Feb 19, 2021 Post Count: 360 Status: Offline Project Badges: |
Look at how high NVidia CPU is for slow NVidia GT 1030. This is very common for programmers working in OpenCL for NVidia/Windows. The NVidia driver stack apparently doesn't support callback synch for OpenCL - for that, you need to use native CUDA, which means extra programming if your development is cross-platform. Perhaps @Uplinger could have a discussion with Scripps once the release is out of the way?This appears to be a problem with NVidia OpenCL using a spin lock wasting CPU. AMD GPU appears to free up CPU and wait for IRQ (interrupt request) from GPU. There are some possible workarounds, search the internet, NVidia OpenCL 100% CPU workaround. I use Process Hacker tool, it can check and change thread priority with right click of a thread. The previous beta had GPU thread run at idle priority, and that slowed down my AMD GPU when CPU is maxed out by CPU tasks. This March 12 beta use normal thread priority and it ran faster for my AMD GPU. I use Process Lasso, which can make the change permanent for each new instance of a chosen app. It helps, in particular, with the Einstein OpenCL app for iGPU. |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
The CPU part used 100% of a thread while the GPU percentage jumped between low values and 100%. I have noticed the same things on my NVidia GPU. Ryzen 2700x, Win 10, NVidia GT 1030, 0.61 / 0.62 hours. (98%) Ryzen 2700x, Win 10, AMD 5500 XT, 0.08 / 0.16 hours. (50%) Ryzen 3900x, Win 10, AMD RX 550, 0.05 / 0.49 hours. (10%) Intel i7 2600, Win 10, AMD RX 580, 0.07 / 0.21 hours. (33%) Look at how high NVidia CPU is for slow NVidia GT 1030. This appears to be a problem with NVidia OpenCL using a spin lock wasting CPU. AMD GPU appears to free up CPU and wait for IRQ (interrupt request) from GPU. There are some possible workarounds, search the internet, NVidia OpenCL 100% CPU workaround. I use Process Hacker tool, it can check and change thread priority with right click of a thread. The previous beta had GPU thread run at idle priority, and that slowed down my AMD GPU when CPU is maxed out by CPU tasks. This March 12 beta use normal thread priority and it ran faster for my AMD GPU. Nvidia OpenCL support has always been poor at best so what you’re seeing is no surprise. Doubt that will ever change because they are more interested in developing their CUDA app.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|