[quote]TN is only using 29.51%.

Do you mean a TNGrid task only uses 29.51% of a CPU core? - Correct. now its at 46.82%

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.

what do you call this file?

Anything ending in .bat, for example hamster.bat

So WCG is screwed up, Cosmology as well. What's going on?

Lack of funds?

I went back to MOO. I used to do them long ago, but looks like my account was deleted at some point in time.

I lost my Climate prediction account too, a few years back. The admins had no idea why it went away.

[quote]TN is only using 29.51%.

Do you mean a TNGrid task only uses 29.51% of a CPU core? - Correct. now its at 46.82%

Odd, I just tried one on a Ryzen 9 3900X and it's 100%. Yours has the required AVX instruction set. What's the total CPU usage reported in task manager?

I had thought about the bug in the new version of Windows 11 which causes incorrect CPU % reporting, but you're on Windows 10. I'm not aware of a bug in that, but there might be the same one. Are any other projects doing the same?

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"

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

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"

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).

yeah I keep forgetting gpu uses cpu, but then again figured BOINC or the system would take care of managing that.

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.

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).

yeah I keep forgetting gpu uses cpu, but then again figured BOINC or the system would take care of managing that.

It's not very good at it. GPU tasks should get higher priority on the CPU than CPU tasks get on the CPU. But we all know Boinc is a piece of shit. However in your case it was actually doing it correctly!

The only thing wrong in your case is the GPU task is noted as 0.2C + 2NV. So Moo project has determined that task will take a fifth of a CPU core, when it's really taking 2. That's Moo's fault. You can change it in an app_config.xml for Moo.

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.

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.

HWINFO says GPU's are 98% capacity. 15/16 cores are used in BOINC. 1 core is left free for general non BOINC stuff. Though if there was a way that when I am not on the computer to use all 16 and then release one when the computer is in use, then it would be a more efficient use of my system. So I could configure MOO to do like you said for now. I will have to look up the command to do that.

HWINFO says GPU's are 98% capacity.

Then all is well. I use MSI afterburner which gives lovely graphs. I can see temperature and usage of CPU and GPU all at once and adjust Boinc until everything is running most efficiently.

15/16 cores are used in BOINC. 1 core is left free for general non BOINC stuff. Though if there was a way that when I am not on the computer to use all 16 and then release one when the computer is in use, then it would be a more efficient use of my system.

The current version 7.20 of Boinc doesn't have that setting, but it's planned for 7.22. https://github.com/BOINC/boinc/pull/4871

So I could configure MOO to do like you said for now. I will have to look up the command to do that.

Have you used app configs before? You need this app_config.xml in the Moo folder:

<app_config>
    <app>
        <name>dnetc</name>
        <gpu_versions>
            <gpu_usage>2</gpu_usage>
            <cpu_usage>2</cpu_usage>
        </gpu_versions>
    </app>
</app_config>

Then all is well. I use MSI afterburner which gives lovely graphs. I can see temperature and usage of CPU and GPU all at once and adjust Boinc until everything is running most efficiently.


I use that as well...more for boosting the GPU temp range to run it a bit harder.
But I see the usage graph now as well. I'm pretty much maxed out. 98% on both cards.

I forgot it looks at CPU as well.
Based on that info, the system is working just under maximum. 98% seems to be a common number.
CPU temp with a radiator is also just under max.

That's what I built this system to do.
Gaming board, hardcore but not pricey CPU.
GPU's are second hand. I got a good deal on the 1080 a long time ago, that group sold off all their cards really fast. I'm ok with a 1060 and a 1080.
I've spent all the money I am going to on this system and I will just keep it this way until it dies.

App_config I have used in the past to limit LHC ATLAS. But then they changed their coding and the app_config was no longer needed.

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

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


Thats good to see they are looking at that idea for more specific control for idle and non idle systems.

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.

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.

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.

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?

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?

1080 and a 1060TI