Message boards :
Number crunching :
Limiting GPU usage
Message board moderation
Author | Message |
---|---|
Send message Joined: 25 Apr 09 Posts: 5 Credit: 2,275,994 RAC: 0 |
I would like to ask is there any option on which I could limit the usage of the milkyway GPU application. I know that the "optimized" GPU program had the ability to set different wait factors and kernel frequency through app_info.xml but there isn't one on default milkyway. |
Send message Joined: 14 Feb 09 Posts: 999 Credit: 74,932,619 RAC: 0 |
They are actually the same app. |
Send message Joined: 25 Apr 09 Posts: 5 Credit: 2,275,994 RAC: 0 |
So can I somehow get it to work so that BOINC would run both CPU and GPU work and I would have the ability to pause GPU work? From few people posts I got the impression that app_info would make the applications as anonymous platforms and BOINC would deal them as CPU applications hence I would have to pause both CPU and GPU work if I would only want to pause GPU work. The main question is, can I get both of them to run through app_info.xml? |
Send message Joined: 28 Apr 08 Posts: 1415 Credit: 2,716,428 RAC: 0 |
I'm using boinc 6.10.29 this release has a "snooze GPU" feature. It might be worth trying. Right click on tray icon, its in the menu there. |
Send message Joined: 25 Apr 09 Posts: 5 Credit: 2,275,994 RAC: 0 |
I'm using boinc 6.10.29 this release has a "snooze GPU" feature. It might be worth trying. Right click on tray icon, its in the menu there. I have 6.10.29 and I know I can pause GPU work, but can I limit the GPU workload through app_info.xml and still have the ability to use both CPU and GPU and pause GPU work while CPU continues to calculate? |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
You might want to try emailing the boinc_dev or boinc_projects mailing list if you think this is a useful feature for the boinc client. |
Send message Joined: 12 Apr 08 Posts: 621 Credit: 161,934,067 RAC: 0 |
You might want to try emailing the boinc_dev or boinc_projects mailing list if you think this is a useful feature for the boinc client. BOINC Dev or Alpha, projects is for project issues ... not BOINC features ... :) But, essentially, that is the only way to get an idea in the works ... 4-5 years later you might even see it implemented ... |
Send message Joined: 25 Apr 09 Posts: 5 Credit: 2,275,994 RAC: 0 |
What if you Travis add there an feature where the application would read a file where a user could put the options as on app_info.xml <cmdline></cmdline>? |
Send message Joined: 7 Oct 07 Posts: 25 Credit: 35,430,690 RAC: 1,388 |
What if you Travis add there an feature where the application would read a file where a user could put the options as on app_info.xml <cmdline></cmdline>? Good idea! I would like to be able to set those options for the standard application. When life gives you lemons, make lemonade! |
Send message Joined: 25 Apr 09 Posts: 5 Credit: 2,275,994 RAC: 0 |
So it is possible to run both GPU and CPU through app_info.xml and that way limit gpu usage. For some reason when I tried it last time it gave just errors or didn't run on both. Here is my App_info.xml file. <app_info> <app> <name>milkyway</name> </app> <file_info> <name>astronomy_0.20_x64_SSE3.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>19</version_num> <file_ref> <file_name>astronomy_0.20_x64_SSE3.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_0.21_windows_x86_64__ati13ati.exe</name> <executable/> </file_info> <file_info> <name>brook64_ati.dll</name> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>21</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <coproc> <type>ATI</type> <count>1</count> </coproc> <cmdline></cmdline> <file_ref> <file_name>milkyway_0.21_windows_x86_64__ati13ati.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>brook64_ati.dll</file_name> </file_ref> </app_version> </app_info> The first file_info and app_version is for optimized cpu application to change the cpu application, just rename both "astronomy_0.20_x64_SSE3.exe" parts to corresponding exes. The second and third file_info and second app_version is for the ati GPU application. And here you can find the <cmdline></cmdline> where you could put the normal options. |
Send message Joined: 10 Feb 08 Posts: 32 Credit: 13,227,191 RAC: 0 |
*bump* I would like to know too, if and how it might be possible to lower the load on the GPU? Im working on my PC and the input lag is very annoying. Thx in advance for any help! |
Send message Joined: 6 Apr 08 Posts: 2018 Credit: 100,142,856 RAC: 0 |
*bump* The only way I know is to suspend any projects using GPU. In this case it will also suspend any MW CPU WUs, so I just kick off my usual CPDN 'backup' WUs. (When I come to restart MW I don't have to worry about finishing off any 'backup' WUs and running out of time on them since CPDN WUs have no time limits.) |
Send message Joined: 10 Feb 08 Posts: 32 Credit: 13,227,191 RAC: 0 |
That isnt really an option since usualy when the PC is on... im working on it. So what im looking for is a way to limit the GPU usage to say 75% - or whatever is needed to have a lagfree Windows. |
Send message Joined: 6 Apr 08 Posts: 2018 Credit: 100,142,856 RAC: 0 |
|
Send message Joined: 12 Apr 08 Posts: 621 Credit: 161,934,067 RAC: 0 |
The 6.10.32 (and later) version has a CPU limiter feature that you could try. If the system detects usage over the preset limit it will suspend BOINC. It is supposed to suspend both CPU and GPU usage and this may help your issues. In my case it was randomly slowing the work by suspending when I was asleep so I don't find the feature useful. |
©2024 Astroinformatics Group