I did not get enough wu, only 20 for the queue on a threaripper 3990x. I run out of wu overnight serverial times. There is no resting timer running. I find my computer idling in the morning and i haven't yet configured a 0 prio backup project. The backup project wouldn't help to keep the Computer running with Sidock wu.
Please increase the limits of task in progress for this processor.

it's not just big and fast cpus. my little 3770k and 3570k run out often. it looks like the core count x2 is max at a time.

it would be nice if they could raise max in progress.

I am not seeing a 2 core limit on my Intel 4790K rig. Right now it is processing 6 tasks, 3 RxDock and 3 CurieMarieDock. My Ryzen 1700x rig has not received more than 1 task at a time though.

I expect that they limit the number sent out to each machine in order to get them back quickly.
I can live with that, if it helps the science. Otherwise, I could use more too.

The limit of 2 WU per core is not the problem.
But with the limit of 128 WU per host it is not possible to run hosts with 128 or more cores efficient at SiDock.
This value should increased.

I think it would be better to rise it up to 512wu...
Some Threadripper 64c/128t are already present on this project
On others projects there are dual Epyc (128c/256t) monsters....

For us donors who need to plan and maintain our donations, there are generally three methods to approach this:

1) Ask the project admins for a general increase of these host limits. Of course this is what this thread is for.

Lately, this project became better in keeping small/slow computers fed with work overnight. Large/fast computers are still prone to run out of work, and as mentioned, more than 128 logical CPUs are not being fed even with 1-deep workqueue. 88- and 96-threaded computers have been a common sight in Distributed Computing for years now, 128-threaded computers are quite common now too, and 256-threaded computers are making more appearances too. Particularly, what the SiDock@home server is perceiving currently is listed here: cpu_list.php

So the question is, to which degree are the admins ready to cater to the convenience of donors with larger/faster-than-average hosts?

2) As an individual donor of large/fast hosts, get in personal contact with an admin and ask for the server to have extra limits configured for selected host IDs.

I don't know if this is acceptable here at SiDock. I never tried this approach at any project myself; I merely saw that some project admins do this.

3) Partition your single large/fast computer into several small/slow computers.

This gives very good control into your own hands, and it works with almost all projects. Therefore, this is what I routinely do at projects with low limits of work in progress per host, if I am having trouble to maintain a reasonable work buffer at such projects. This method needs to be implemented responsibly though. I am not going into detail how to implement it.

looks like the problem is not software, but the disk space on the server, I think that one needs to be upgraded to higher capacity, so that all computers can be properly fed with workunits.