When exactly does Boinc check for a running app and then suspend gpu work when using......

<exclusive_gpu_app>important.exe</exclusive_gpu_app>

I attempted to use this option but the gpu's went right along crunching. Messages indicated that Boinc read and understood the option when read as the executable was named and message stated not to use gpu's.

Perhaps this is checked when a wu first starts and not checked again if wu is part way done?

Boinc version 6.12.8 32 bit.

---

Boinc....Boinc....Boinc....Boinc

No, it's checked immediately upon reading the cc_config.xml file and for evermore thereafter; as soon as program "however.exe" comes into Windows memory, the suspend mode will be activated. However, this isn't that easy on a GPU ran app, especially not if this task hasn't checkpointed yet. It'll run to the next checkpoint, before BOINC tries to break in.

Make sure that "however.exe" is the program that stays in Windows memory. Some programs use a launcher program that's called "however.exe", but their actual program runs with "stayhere.exe".

---

Thanks Ageless,

I also read some of your other posts on this subject. Will try again later and see what happens now that I know what to look for.

---

Boinc....Boinc....Boinc....Boinc

Working as advertised!!

Nice option to have.

Now I can encode video (which uses the NVIDIA GPU), Boinc suspends the CUDA apps and my DCF does not get messed up when finished with the video. Excellent!

---

Boinc....Boinc....Boinc....Boinc

Sorry to report some problems.

It appears that the cpu apps stop working in conjunction with the gpu apps. The GPU apps are stopped and completely removed from memory. (not listed in Task Manager) The cpu apps are still listed in task manager but are using 00 cpu cycles. Bringing up Boinc manager shows the gpu tasks are "waiting to run" and the cpu tasks are "running" and accumilating time but progress is not being made on the tasks.

I would not recommend using this option at this time with this version 6.12.8

---

Boinc....Boinc....Boinc....Boinc

It appears that the cpu apps stop working in conjunction with the gpu apps. The GPU apps are stopped and completely removed from memory. (not listed in Task Manager) The cpu apps are still listed in task manager but are using 00 cpu cycles. Bringing up Boinc manager shows the gpu tasks are "waiting to run" and the cpu tasks are "running" and accumilating time but progress is not being made on the tasks.

I don't quite follow.
Just to make sure we're on one line here, you know that there are no GPU apps to be seen in Task Manager? That all apps run on the CPU, be it CPU apps or GPU apps cos no OS out there knows how to run applications straight on anything else but the CPU? Just checking.

Now then, are you only using <exclusive_gpu_apps> or also <exclusive_apps> ?

I'll do some testing today, between last minute chores before new year's. Will let you know how I fare later on. If I can find a reliable project I can use my ATI on... all seem to be down. ;)

I would not recommend using this option at this time with this version 6.12.8

Since it's a test version, best report what you see to the developers.

---

Opened BOINC Manager + Windows Task Manager Processes tab.
Got work from Collatz.
Made a screenshot of it running.
Set <exclusive_gpu_app>steam.exe</exclusive_gpu_app> in cc_config.xml.

Exited and restarted BOINC.
Opened BOINC Manager + Windows Task Manager Processes tab.
Started Steam.
Made a screenshot of it paused.

(Screenshots at 1920x1080 pixels)

As you can see, CPU applications continue running.
Collatz isn't running at all.

Works as advertised for me.

---

I had made the changes to cc_config only for the GPU to suspend.

Then started working with my video files. Starting and stopping the video editing app that would have suspended the GPU work and restarted it several times during the day. I worked with the video files for most of 4 hours.

Later I checked with Boinc Manager. Found that at one point the Boinc service had restarted because the log showed the startup within the last hour. I did not expect that. Examination of the work units showed cpu time advancing but no progress being made. Checked task manager. It showed the science apps for cpu running but using 0 to 5% on all 4 instances. GPU apps not running or in task manager.

I was going to copy the message page but it was useless as it did not show the gpu work pausing, only the RESTART of the cpu work.

My best guess is that multiple stopping and restarting of the software that is supposed to shut down GPU work only, Boinc gets messed up. And I still believe it was useless to copy what little messaging was in the displayed log.

If it's usefull I guess I could turn on some flags (which ones?) and work with some more video over the holiday weekend. Or perhaps I still have log files on board that would be useful?

Please advise.

---

Boinc....Boinc....Boinc....Boinc

If BOINC had stopped the CPU apps (actually issued a 'suspend' instruction), you would see restart/resume messages in the log, same as you're seeing for the GPU apps.

I can only assume that - as far as BOINC is concerned - the CPU apps are running normally, and clocking up time. Remember that current BOINC managers display elapsed (wallclock) time, not CPU time.

And I guess the apps themselves were fighting for whatever resources (CPU, memory) were left over from from the video editing. Have you checked how heavy the CPU use of that app is?

Today it's working just fine...........

Perhaps my 60+ year old, pain medicated brain simply didn't do it right yesterday. Or some such thing. I get tired and don't remember things as they occured later in the day.

It's good that Ageless demands absolute proof for problems to be solved.
I'm sorry if I caused undue concern with this section of Boinc operation.

---

Boinc....Boinc....Boinc....Boinc

It's good that Ageless demands absolute proof for problems to be solved.
I'm sorry if I caused undue concern with this section of Boinc operation.

{Smiles}

It's just that we're a forefront against a developer email box overflow of things not needing to be sent to them. But don't let that scare you. Next time you will find a bug. :)

---