Yeah, the whole boinc thing is much more complicated than Foldingathome.
No need there for running multiple tasks at once, as each task/WU, ballasts each GPU nearly 100%.
In my case, I have several PCs. It wouldn't matter if you saw my PCs, as I am going through test phases, and probably will have a good 10 listed, though only 1 or 2 are active at a time.
 
I know I can choose one setting for home, one for work, etc... but even my own PCs change their GPUs regularly; which is why I haven't given the 0.x tasks per GPU a thought yet.
The ~80W reference was to this post you posted in this thread:

 
At some point I might be ready for it, but I also have a family to feed and spend time with. So multi task GPU study will come soon for me.
What gets me, is that x-amount of tasks per GPU is different from GPU to GPU. And even from project to project.
It takes a lot of work, and a dedicated system to run all the tasks constantly on one GPU.
Once the system is stable, the project goes down, and you'll have to start again with another project.
And it works easier if you have a set of identical GPUs per PC. If the GPUs are different, the app_config.xml file needs more coding..

I stopped using Xeon CPUs, as they're not as efficient as a GPU.
Perhaps one day when all GPU projects are done, I'll fire up the old Xeon again...

When it comes to Milkyway the AMD Radeon VII Graphics Card or any Double Precision Graphics Card will out Perform an Non-Double Precision Graphics Card so learning and testing BOINC Projects that have a GPU Apps Milkyway is not the best one to start with and compare settings and results.
The AMD Radeon VII Graphics Card uses only 1%-2% of the CPU (12 Cores) while a Non-Double Precision Graphics Card uses up to 25% per Card or 48%-51% of the CPU (14 Cores) with two Graphics Cards.
You should NOT be running different BOINC GPU Projects on the same Host at the same time, nor should you be Folding on the same Host.
To Fold on your Host Run Only BOINC Projects and use the CPU App of the Project.

bill1024
Aren't all tasks in Milkyway validation inconclusive until validated?
I think so, not validation pending, not sure why they do it that way.
I'll have to run some to double check that.

Not that I have seen, but "Results are inconclusive until someone else validates the same work unit."
I get a higher rate of Validation inconclusive when I try to run to many Tasks on the GPU.
Validation inconclusive (217)  · Valid (1802) Running for Days now
Validation inconclusive (134)  · Valid (109) Running Today
Validation inconclusive (408)  · Valid (661) Running Today
It should really say Pending Validation, like most other Projects.
Current: Workunits waiting for validation 55 Server Status
 
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4542&postid=69280#69280
""Validation inconclusive" is misleading on this project.  Those jobs should be labeled as "Validation Pending", like they are on other projects.  So, as previously stated, it's nothing to worry about.  "Invalid" or "Error" are the only ones to be concerned with.

The message you see might indicate some other problem though.  Typically that appears when BOINC is trying to use a GPU that's not working well.  You'll need to do some troubleshooting to see what's causing that.  Your host shows as having two GPUs, but your run times are consistent with BOINC trying to start a work unit on a GPU that it can't use for some reason.  That WU then has to wait until a GPU becomes available.  There might be a hardware issue.  Load up a GPU monitoring tool like GPU-Z, HWInfo or System Information Viewer to see what your GPU loads look like."