I run a WU (4CPU)
Tasl manager reports CPU charge 30% and used memory 25%
My global and project preference are set to max 90%
But WU start and stop at 6.128% and freeze Boinc Manager so also computer !?
Task manager report hen CPU usage 15%, used memeory : 15%
All my eight core do nothing more. The only way is a logpff using task manager.
Than all start nirmal again, but at 6.128%; again freeze. So I abort the WU
Look on my host 33373
Who have idea ?

---

No any answer !
I forgot to say, my prference are set "not use more or 90% CPU time"
Also in my BAM it set at not use more 80% (to prevent overheating of CPU)
The latest will say 3 second working one second wait.
As good as i know, the BAM setteings have priority on project setting (unless other specified)
So BAM says 80% CPU time max. YAFU 90% max (from the 80%)
So normally YAFU can use max 72% of CPU.. It is mathematical !
But, and here is the problem. Sometimes YAFU take 100% of CPU (so reported my task manager)
I means "yafu.exe" , and when it freeze it is "yafuwrapper_26014.......exe" who takes 100% CPU,
I alwys need to force logoff to unfreeze my host, by using task manager. All other software are also frozen !.
I also tryed to give (in task manager) priority "below normal". Nothing change.
Who can explain ?

---

It has to be something with your computer.
yafuwrapper does nothing. It only starts yafu. yafuwrapper doesn't use 100% cpu at any time.

Hello
Thank you for answer.
Next time, I will make a screenshot and send by privaye message.
Best regards

Hello,
it do perfect the same on my second host. https://yafu.myfirewall.org/yafu/results.php?hostid=33275
Once again Yafu take 100% non stop.
In my BAM also in my computing preference here on my account page ,
there are restriction : " use max 90% cpu time (.to reduce and prevent over heat).
Yafu ignore it. With results of host not more can do something (exept task manager.
I will not put my CPU in danger for Yafu who ignore the settings.

:

---

If yafuwrapper_26014.......exe is taking up 100% CPU then it's probably fighting with the firewall/security application.

Make sure the firewall or other security software isn't blocking the wrapper executable.

Open up the Boinc\Data directory in your firewall/security software.

The wrapper code just manages the yafu.exe, ecm.exe and gnfsxxx.exe tasks and shouldn't use more than 0.2% CPU.

Hello Marmot.
On Z77 and Maximus host, there is only Win7 Ultimate and drivers. nothing else.
There are used pnly to crunch WU.
The only internt connections are to project and BAM.
On host 33275, they are security. But BOINC folder also associated folders are excluded from scan
On my router, I have manbually allow the IP adress from te project's server.
Perfect the same. With/without security, always the same.
It seem Yafu not like I7-2600K /Win7 Ultimate (official, not cracked) !!!
Look to all my stats.....
I will not more accept WU from this project. I will stay visible because I use BAM and synchro
To be sure on host 33275, all is manual. Not say " it is the reason".
All works perfect with all project except this.
If we look to stats, very few persons are working.
No any real answer from Admin.
Thank you for your answer. I know you are also on many other projects and member of Gridcoin.!!!
Best regards from Belgium

---

I say it again. The only task of the yafuwrapper is to start yafu. Yafuwrapper doesn't do any computation. It doesn't need and doesn't use 100% cpu. But if this is the case it has something todo with your computer, which I can't analyze. Yafuwrapper runs well on my Win7 and Win10 systems.

I leave.
I will suggest to the first belgian team to leave this project.
Everyone have the same problem in our team.
I mean everyone running Win7 X64.and running other projects.
This one need all cores. Impossible tu run together wuth Einstein GPU
It will be stupid to crash our CPU.
Sorry.
Good bye.

---

Hello,
it do perfect the same on my second host. https://yafu.myfirewall.org/yafu/results.php?hostid=33275
Once again Yafu take 100% non stop.
In my BAM also in my computing preference here on my account page ,
there are restriction : " use max 90% cpu time (.to reduce and prevent over heat).
Yafu ignore it. With results of host not more can do something (exept task manager.
I will not put my CPU in danger for Yafu who ignore the settings.

:

Tech PowerUp ThrottleStop is one solution to globally protect CPU's from overheating if TThrottle and BOINC MGR fail on Windows.


@yoyo_rkn, I understand what they are talking about now.
I have seen the same problem. I even installed TThrottle to idle WU's in order to protect my laptop from over heating and it will throttle down yafu_wrapper but the sub processes do not receive a throttle control message and continue at 100% and overheat the CPU.
It could be that TThrottle doesn't recognize the sub processes started by wrapper as being BOINC processes. But BOINC.exe also refuses to throttle them YAFU sub processes and this is what marsinph is complaining about.

Maybe it's just a global variable that's not being exported to the OS environment that TThrottle and BOINC.exe need to see in order to throttle down the ecm/gnfs-lasieve sub procs?

Protecting machines from overheating by limiting BOINC to 80% max CPU is legitimate need for users.

To recreate this, use your test machine and install TThrottle, tell it to keep the CPU temp under 70C, then watch it's behavior on YAFU and other projects. For LHC Theory or ATLAS, it will lower the VM's CPU usage till the CPU temp drops to 70C. For sixtrack.exe, it throttles the executable using OS commands. It throttles yafu_wrapper but not ECM/GNFS.
Also, see what BOINC.exe does with YAFU when telling it to use at most 80% CPU.

The thread and whole discussion was about yafu_wrapper taking 100% CPU, which isn't the case at all. Then in his last posting he blamed that yafu.exe takes 100% CPU and because of this he ranted and left the thread.

Now to your case of throttling.
As fas as I know there is no message in Windows or Linux which tells a process to throttle down. AFAIK BOINC and such throttling tools suspends the respecting process some seconds or fractions of a second. So in this case yafu_wrapper can't do anything, it is suspended! So I think such throttling tools does it wrong, they must throttle also al childs and childs of the childs and so on. Or they must throttle those childs which consumes much CPU.
Isn't there a way to specify the process names which should be throttled?

yoyo

Hello,
Once again, i repeat that my setting on BOINC are set to 75% of CPU and 80% of CPU time.
With other words with 8 cores CPU, using 75% it will say at most using 6 from the 8 CPU's
Then 80% of CPU time totally, for the 8 cores, BOINC may use at most about 70% of total power.
It works perfect for all project, except Yafu who ignore the restriction of Boinc.
This on all my hosts
I would be able to make a screenshot, but when it happens, all is frozen.

Isn't there a way to specify the process names which should be throttled?

yoyo

In TThrottle there is a way to add processes to the recognized list.
I tried using it for YAFU sub processes, but failed after an hour of attempts, so resorted to a global throttle of ThrottleStop (which was already installed and ready to go).

I just tried setting BOINC Manager to 75% maximum CPU usage and it is properly throttling gnfs-lasievexxx today as the processes are going gray for split seconds avery few seconds in process manager. (I remember that prior version of BOINC wasn't doing this but my memory is getting older now and might not be reliable).

So BOINC Mgr can throttle YAFU and protect the CPU from overheating and the OP's problem should be solved.

@marsinph, if you set BOINC to use at most 6 cores then you can only run yafu, yafu small composite and yafu-4t. If you made changes to app_config.xml to allow for 16t by setting virtual core count to 16, then 75% of 16 is 12 cores. At 12 virtual cores you are still using all 8 real cores on Yafu, Yafu composite, Yafu 4t and Yafu 8t if you haven't set specific core and thread counts for each work unit.

So if your virtual core count is 16, you need to set BOINC to 37% or change the app_config.xml (or delete it).

EDIT: Forgot this thread was about 4t only. BOINC setting to 80% CPU is working fine for a 4t WU on this laptop as I type this. Using Process Hacker to watch the WU throttling down.

Hello Marmot,
We cross often on forum !!!

I have read 2, 3 4 times tio be sure to understand (I am native french speaking but I do my best)
My Yafu settings (Internet are "small composite" and 4 Cores
Boinc for project, the same..CPU use set on 80%

The problem is that Yafu NOT respect it !

If I try to run ONE, I repeat ONE 4T WU (also on 4Cores from the 8 availale (i7-2700K) Yafu take all

Very often reported to Admin, always the same answer ; users get erdits !!!
It is not the problem. The proble is only on the WU on Yafu, Yoyo and RNA,
Three differents PRJ, but same kind of WU and same admin.....

Isn't there a way to specify the process names which should be throttled?

yoyo

In TThrottle there is a way to add processes to the recognized list.
I tried using it for YAFU sub processes, but failed after an hour of attempts, so resorted to a global throttle of ThrottleStop (which was already installed and ready to go).

I just tried setting BOINC Manager to 75% maximum CPU usage and it is properly throttling gnfs-lasievexxx today as the processes are going gray for split seconds avery few seconds in process manager. (I remember that prior version of BOINC wasn't doing this but my memory is getting older now and might not be reliable).

So BOINC Mgr can throttle YAFU and protect the CPU from overheating and the OP's problem should be solved.

@marsinph, if you set BOINC to use at most 6 cores then you can only run yafu, yafu small composite and yafu-4t. If you made changes to app_config.xml to allow for 16t by setting virtual core count to 16, then 75% of 16 is 12 cores. At 12 virtual cores you are still using all 8 real cores on Yafu, Yafu composite, Yafu 4t and Yafu 8t if you haven't set specific core and thread counts for each work unit.

So if your virtual core count is 16, you need to set BOINC to 37% or change the app_config.xml (or delete it).

EDIT: Forgot this thread was about 4t only. BOINC setting to 80% CPU is working fine for a 4t WU on this laptop as I type this. Using Process Hacker to watch the WU throttling down.

Please screenshots or something similar to see that 4t uses 8 cores!!!!!
Where and how do you see it? You just claim it, but didn't provide any symptoms.

The server configuration for 4t is:

    <plan_class>
        <name>                  4t          </name>
        <min_ncpus>             4           </min_ncpus>
        <max_threads>           4          </max_threads>
        <nthreads_cmdline/>
    </plan_class>

It works perfect on every host where no app_config was done and the standards from the project are used. It uses exactly 4 cores.