What does the "t" signify in yafu-4t and yafu-32t ???
How does one choose the number of CPUs for each type of yafu WU ???

What does the "t" signify in yafu-4t and yafu-32t ???
How does one choose the number of CPUs for each type of yafu WU ???

Yo YoYo are you there???
Doesn't anybody know the answer???

If you want to attempt to tame this beast put this in your app_config:

<app_config>
    <app>
        <name>yafu-32t</name>
        <max_concurrent>1</max_concurrent>
    </app>
    <app_version>
        <app_name>yafu-32t</app_name>
        <plan_class>32t</plan_class>
        <avg_ncpus>32</avg_ncpus>
        <cmdline>--nthreads 32</cmdline>
    </app_version>
</app_config>

Then restart it:

/etc/init.d/boinc-client restart

4t is thought to run on 4 threads
8t on 8 threads
and so on.

The big ones use every core they can find if not constrained.

---

The big ones use every core they can find if not constrained.

So are you saying I need a 16 or 32 core machine to run the 16 and 32 core workunits? I know how to constrain them thru the settings but am asking as I do not own a 32 core machine.

I think the answer is "yes" Mikey.
A 1950X will use all 32 threads to crunch a 32t task.

---

I think the answer is "yes" Mikey.
A 1950X will use all 32 threads to crunch a 32t task.

I figured that but am wondering if I NEED a 32 thread machine to crunch them? Can I for example fudge the numbers and use a 24 thread to make it THINK I have a 32 thread pc or do I even need too.
The short answer is I can't seem to get any of the 32 thread tasks and me not having a 32 thread machine seems to mean I will never run them.

The 16t and 32t Tasks are not just for fun 16t or 32t Tasks. They can be very cpu consuming, means they can run 2 days on 32 cores. So if you run them on just 8 cores they will run very long.

But on every system you can fake the number of cores BOINC sees. On a 8 core system you can state there are e.g. 60 cores and BOINC will handle it as there are 60 cores.

See ncpus here https://boinc.berkeley.edu/wiki/Client_configuration

---

.

I just gave up on a 32T task after it had been running for nearly 7 days, 3 of which it sat at 100%.
I could see the task in my task manager and it was using about 4% of my CPU. After I restarted BOINC, the task restarted at about 76% complete and the 7 days disappeared to be replaced with about 8hrs. After I left it over night, then aborted it.
7 days locking up 32 threads is just a bridge too far.

---