Message boards : BOINC Manager : exclusive_gpu_app *.exe not working in 6.10.24
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Dec 09 Posts: 7 |
Hi all, I have a problem. I can´t get boinc to stop computing while a specific app is running. However, the <exclusive_gpu_app> command in the same file works fine. Boinc also recognizes the file correctly and tells, computing won´t be done while *.exe is running. When the app is running boinc stops GPU-Computing, but the CPU work still continues. I´m running the beta version 6.10.24, could this be the reason? |
Send message Joined: 29 Aug 05 Posts: 15560 |
The <exclusive_gpu_app> condition only works on work for GPUs. If you want the CPU to stop while that same app is in memory, you'll need to use the <exclusive_app> option as well. Used in the same way as the exclusive GPU app option. |
Send message Joined: 15 Dec 09 Posts: 7 |
The one project that runs on the GPU stops computing properly. But the others, that run on the CPU, don´t. Here´s my cc_config.xml: [CODE]<cc_config> <log_flags> </log_flags> <options> <exclusive_app>1.exe</exclusive_app> <exclusive_app>2.exe</exclusive_app> <exclusive_app>3.exe</exclusive_app> <exclusive_app>4.exe</exclusive_app> <exclusive_gpu_app>a.exe</exclusive_gpu_app> <exclusive_gpu_app>b.EXE</exclusive_gpu_app> <exclusive_gpu_app>c.exe</exclusive_gpu_app> <exclusive_gpu_app>1.exe</exclusive_gpu_app> <exclusive_gpu_app>2.exe</exclusive_gpu_app> <exclusive_gpu_app>3.exe</exclusive_gpu_app> <exclusive_gpu_app>4.exe</exclusive_gpu_app> </options> </cc_config>[/CODE] I´ve renamed the actual names of the EXEs to 1,2,3,4,a,b,c. The <exclusive_app> doesn´t stop GPU computing either. PS: The tread name should be: <exclusive_app>*.exe</exclusive_app> not working in 6.10.24 (somehow the <></> were deleted with the content inside.) Could you please rename it? |
Send message Joined: 29 Aug 05 Posts: 15560 |
The <exclusive_app> doesn´t stop GPU computing either. No, that's known. Which is why we got the <exclusive_gpu_app> option to play with as well. According to this thread it takes a good 10 seconds for the <exclusive_gpu_app> to kick in, which can be attributed to the GPU running to the end of cycle, writing back the info to disk, before being available. A neater way than just to dump whatever it was doing. So, recap: <exclusive_app> is for CPU only. It can take anywhere from immediate to 10 seconds to respond. <exclusive_gpu_app> is for GPU only. It can take anywhere from 10 seconds to a minute to respond (depending on the throughput speed of the videocard and the slot it's in). If you want the same application to suspend BOINC on both CPU and GPU, you will need to use both the <exclusive_app> and <exclusive_gpu_app> options and remember their individual execution times. PS: The tread name should be: I'm not even going to try. Those <></> tags can be considered HTML, which the titles still use. They're made into links we can click, remember? ;-) |
Send message Joined: 15 Dec 09 Posts: 7 |
Ah, thanks for renaming. The GPU stops almost instantly (2 sec), Now I have let run one app that should stop CPU computing for about 10 min: GPU computation has stopped, but the CPU still computes and boinc even requests new tasks and starts them. Some info: I have set the preferences in all the project home pages to stop CPU computing, when user is active but GPU should still compute while user is active. But I have set up Boinc-Manager to always compute. Maybe this could be the reason. But why then GPU-computing stops? Maybe I have to set always compute on the project pages and change BOINC to look for the preferences online. Hm, I´ll try it out. Yes, that was the problem. But why BOINC doesn´t just stop computing, when an exclusive app is running, no matter what options I have set somewhere. I usualy wanted to let boinc always compute, but when I do something demanding, I could switch to read the online preferences, resulting in computing only when inactive. Now when I do something demanding (like HD Flash Video in the webbrowser..., and I can´t use the <exclusive_app> command, because my webbrowser is always on) I´ll always have to stop computing completely and when I forget to set it back, it will not compute at all, until I realize it some day. Is it somehow possible to stop computing when flashplayer is running? The Taskmanager doesn´t show flashplayer in the list. |
Send message Joined: 20 Dec 07 Posts: 1069 |
..., and I can´t use the <exclusive_app> command, because my webbrowser is always on) I´ll always have to stop computing completely and when I forget to set it back, it will not compute at all, until I realize it some day... As a workaround for that (the forgetting to resume:-), you could use the "Snooze" command from the right-click menu on the task-bar symbol. That one resumes computing after one hour snoozing. Gruß, Gundolf |
Send message Joined: 23 Apr 07 Posts: 1112 |
..., and I can´t use the <exclusive_app> command, because my webbrowser is always on) I´ll always have to stop computing completely and when I forget to set it back, it will not compute at all, until I realize it some day... Or if he feels brave, ;), he can try 6.10.25, which has the snooze GPU function, i've tried it, it does work, not timed it through. Claggy |
Send message Joined: 15 Dec 09 Posts: 7 |
Umm, I can´t find a beta 6.10.25 anywhere. Or is this beta (alpha?) only for linux? I don´t have the snooze-feature. |
Send message Joined: 23 Apr 07 Posts: 1112 |
Umm, I can´t find a beta 6.10.25 anywhere. Or is this beta (alpha?) only for linux? boinc_6.10.25_windows_intelx86.exe boinc_6.10.25_windows_x86_64.exe Claggy |
Send message Joined: 20 Dec 07 Posts: 1069 |
I don´t have the snooze-feature. Try a right click on the BOINC manager icon in the task bar. Gruß, Gundolf |
Send message Joined: 15 Dec 09 Posts: 7 |
I use the german version of BOINC Manager, I see the following options when clicking on the boinc-symbol in the taskbar: Öffne BOINC Manager... BOINC anhalten über BOINC Manager... Beenden Boinc anhalten means suspend Boinc, for me. Maybe this is the snooze function you are talking about. Anyway, I´m extremely brave, I will now install version 6.2.28 :D Hm, why is the wcg-boinc-manager available in version 6.2.28, but the normal Client is only version 6.2.25, anyway, I´m installing version 6.2.25 now. Oh, big mistake here, I mean version 6.10.25, there´s no wcg-6.10.28 client! Good, now I see the GPU-Snooze function. But it won´t stop CPU-computing, better than nothing. Is there any version history somewhere? What was done in version 6.10.25? |
Send message Joined: 20 Dec 07 Posts: 1069 |
Boinc anhalten means suspend Boinc, for me. Maybe this is the snooze function you are talking about. Genau, das ist sie. Die unpassende Übersetzung ist auch der Grund warum ich die englische Version benutze :-) ...Is there any version history somewhere? What was done in version 6.10.25? See this thread for the version history. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) |
Send message Joined: 29 Aug 05 Posts: 15560 |
But it won´t stop CPU-computing, better than nothing. Snooze will stop CPU and GPU. Snooze GPU will only stop GPU. (Snooze CPU only doesn't make sense because all GPU apps use CPU too, often a significant amount). |
Send message Joined: 15 Dec 09 Posts: 7 |
Hm, everything seemed to be fine so far, but now I realized that exclusive_app also stops GPU computation, but I would like to only stop CPU-computation for one app. Why doesn´t it work? |
Send message Joined: 20 Dec 07 Posts: 1069 |
Why doesn´t it work? It works as designed ;-) (see Ageless's last post) Gruß, Gundolf |
Send message Joined: 15 Dec 09 Posts: 7 |
Oh, I somehow overlooked it. Is it somehow possible, never the less? I use a program, which needs much CPU, but doesn´t need GPU at all. |
Send message Joined: 8 Jan 06 Posts: 448 |
Oh, I somehow overlooked it. No. It would be pointless the GPU needs the CPU to do the work even if it's only a fraction of 1% of the CPU. |
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.