The OS is Linux, and the following output is from htop:

 13:15 -  206,76, 172,96, 168,02, yafu CPU time: 9,06361h 91,6717h
 13:16 -  147,00, 164,79, 165,69, yafu CPU time: 9,08h 91,6717h
 13:17 -  55,42, 135,30, 155,50, yafu CPU time: 9,09694h 91,6717h
 13:18 -  22,10, 111,16, 145,93, yafu CPU time: 9,11361h 91,6717h
 13:19 -  9,04, 91,20, 136,89, yafu CPU time: 9,13h 91,6717h
 13:20 -  4,35, 74,90, 128,42, yafu CPU time: 9,14694h 91,6717h

...

 21:03 -  1,93, 1,89, 1,95, yafu CPU time: 16,8483h 129,496h
 21:04 -  1,74, 1,86, 1,94, yafu CPU time: 16,8653h 129,513h
 21:05 -  1,53, 1,76, 1,90, yafu CPU time: 16,8819h 129,532h
 21:06 -  1,46, 1,72, 1,88, yafu CPU time: 16,8986h 129,549h
 21:07 -  6,97, 2,81, 2,22, yafu CPU time: 0,00138889h 0h

Mostly all of the 150 64t- and 250 128t-tasks till yet, run the first 2/3 of the time with full throttle,
and the last 1/3 in idle. In this case, the cpu crunch the first 9 hours, and the next 8 hours she idles.

This 64t is about to break 5000 CPU hours.
I'm thinking it's time to abort.

Had to restart the machine and it went back to ECM mode.

It's aborted.

Welp, at least another blue app for WUProps....

Can the number of 64t tasks available for download please be increased? Quite often, there are none available, so the machine sits idle.

You can run also 32t and 128t instead.
Sequences, which are hadled in 64t are leading to 128t workunits if they grow. This might lead to too many workunits in 128t, where not many computer are taking them.

Therefore I restrict the amount of workunits in 64t when other queues have too much unsent results.

---

.