It's ok now since it started a new task. So now it 2+2 on MOO, 4 LHC (like normal) and 9 single tasks (15) and then 16 is for windows and other stuff.

I've never seen a task (including Moo) use two GPUs. I don't have any machines with two identical cards to test it right now, but I'm sure I have in the past and I just got 2 Moo tasks, one on each card. Maybe only Nvidias do it? (I only have AMDs) Are your GPUs identical?

I use that as well...more for boosting the GPU temp range to run it a bit harder.

I find the manufacturer's range lets it go up to 90C and crash. I reduce it to 50C no fan, 70C half fan, 80C full fan. I also reduce clocks on old cards that are tired and crash a lot, but I never increase clocks as that just causes unreliability and busted cards. I also boosted the max power consumption on my Fury from normal to +50% (!) to stop it reducing the clock when thinking hard and it seems happy with it, apart from I melted the power connector, so I soldered the wires directly on, it's working now. I was going to boost it even higher, but if I select the option to exceed manufacturers overclocking specs, it crashes the other card in that machine, even though I'm not overpowering that one.

But something isn't adding up: 10/20/2022 2:32:52 PM | Moo! Wrapper | Found app_config.xml
10/20/2022 2:32:52 PM | | Config: use all coprocessors

I see nothing wrong there.

The percentages look the same and the core usage configuration looks the same still.

It should have noticed your Moo task needs 2 CPU cores, and should have reduced the number of CPU tasks running. The CPU will presumably still be maxed out, but doing the correct number of things, so the CPU tasks should drift up to nearly 100% each.

Note: it will still display the same 0.2C+2NV until you download new Moo tasks, then it will show 2C+2NV. It's doing what you asked, just not updating the display on the tasks you already have. Yet another Boinc bug.

Also noticed that BOINC tasks says MOO is using between 180-190% CPU and maybe TN with Rosetta and FAH is chewing up to much capacity?

A couple of TN's are 40 minutes behind in CPU time vs run time.
Makes me wonder if TN needs more power.
Rosetta is fine, running about 15 minutes behind.
Maybe drop TN then. For now, setting it to no new tasks to see what happens after it has completed all the stuff in queue.

Your computer's running fine. Your GPU task is getting the 2 CPU cores it needs. The GPUs are most important since they're much more powerful and should always be kept busy. Your remaining CPU cores are shared between the CPU tasks.

Either leave it as it is, since presumably (you haven't told me) your GPU is flat out and so is your CPU.

Or use app config in Moo to tell it that task requires 2 CPU cores, so Boinc will run less CPU tasks at the same time.

Or decrease the number of CPU cores Boinc is allowed to use in preferences, but this won't be very automatic, since if you change your GPU to do something other than Moo, it won't be set correctly.

FAH both GPU's
BOINC 1 GPU at the moment, 15 cores in total allocated to BOINC
TN got more work, so more cores as its a new project.
MOO is also "new"

Must have been a learning thing. CPU's in the 90s now on TN

Either that or you're running more things than cores. You have 16 cores, but you're using 17 cores (Moo is using two cores, as indicated by task manager saying 12%). The CPU doesn't care, but you should watch your GPU usage, because if the CPU is overloaded, it might not feed the GPU fast enough (depends on the project).

FAH both GPU's
BOINC 1 GPU at the moment, 15 cores in total allocated to BOINC
TN got more work, so more cores as its a new project.
MOO is also "new"

[quote]TN is only using 29.51%.

cd /d e:\Program Files\BOINC

:loop

boinccmd --network_available

TIMEOUT /T 300 /nobreak
goto loop

Which I placed in a batch file and told Windows to run at startup and minimised.

QuChemPedia - interesting chemistry research - Can't run this, does not work on my system. Might try again.

I don't remember having problems, but they're out of work just now so I can't test, and I haven't run it for so long my tasks aren't in Boinctasks history or server history.

TN-Grid - genetics _ interesting, will have a look ***Is this CPU or GPU or both?***

CPU only. - bah..there is enough CPU stuff out there and I have plenty of work for CPU. I'm looking for GPU now. If Denis comes back something has to go.

WCG - loads of work now, and I've never had a single error you speak of

Only getting OPN because I am trying to fill my GPU queue. CPU has enough
10/18/2022 8:50:47 AM | World Community Grid | Temporarily failed download of ab73b5548cff860eccd4f3bd6afcc1b4.pdbqt: transient HTTP error
10/18/2022 8:50:47 AM | World Community Grid | Backing off 00:10:09 on download of ab73b5548cff860eccd4f3bd6afcc1b4.pdbqt
(and repeat 15 times) - aborted. They didn't do a blinking thing over night which is normal when they are stalled out with transient. I think I abort more stalled downloads than I do work. Seems to be a GPU task thing. CPU works just fine. Almost thing its time to stuff WCG for a month and come back. Another group that is in over their heads and can't fix stuff.

So your only problem is you have to retry downloads? You need to run "boinccmd --network_available" from a batch file and/or task scheduler. This will retry all downloads. You can set it to run as often as you like.

For those of you interested in other BOINC projects:

collatz has shut down, and expects a few months before it is ready to restart.

SETI@home has shut down, and plans to restart only when they get a new source of data.

cosmology@home appears to have a server problem - they've been unreachable for about a day.

RNA World stopped creating workunits over a year ago, but is still trying to get their last 20 or so workunits finished. The remaining workunits are expected to run for months each.

Some BOINC projects are now using a very high initial estimate for the run time, possibly in order to get an especially high priority for their tasks. GPUGRID is one of them. You need to watch how the estimated time to completion drops in order to see if that happened,

If that was true, it would only work once. Boinc then adjusts using the duration correction factor. So, no point in a project doing so.

What I'm seeing with GPUGRID work does not agree with you. The tasks start out with an expected runtime of hundreds of days (well past the deadline) and actually finish in less than two days, over and over.

One possibility I've thought of - the duration correction factor works for CPU tasks, but does not work for GPU tasks. I've only seen this odd behavior on GPU tasks, GPUGRID seldom offers any CPU tasks.