I'm using 6.12.33, but I seem to remember this problem in years gone by as well.

I am running SETI and Einstein on my GPU only. Rosetta, Malaria, and LHC run on the CPUs. All are equal priority 100, except Einstein which is 5.

I have only seen this on SETI/Einstein. When SETI downloads get stuck (the network traffic thing), the computer runs out of GPU work pretty quickly and never tries to get Einstein work. If SETI just runs out of work (nothing stuck in the download queue), it downloads Einstein as expected and keeps on working. CPU projects seem to work as expected.

Any ideas?

---

Downloads that are stuck will eventually come in. You've had work appointed by the Seti project, it's just not in on your system yet. This isn't categorized as "No work from project", which is when Einstein as a sort of backup project would try to fetch work.

---

And therein lies the rub. Those WUs may sit stuck in the queue for days (depending on how jammed up Seti is) while the "backup" project is never asked for work.

This seems to be the usual failure mode for the past several months. If this is how the scheduler is supposed to behave, it does away with the value of a "backup" project.

---

You are probably right. It just seems to me like it ought to be able to figure out that if it is out of work ready to start it should get some from anybody that has it. Figuring out how much might be a bit dicey, but some minimum amount should work. If the work that was stuck comes flowing in, so be it, it would be delayed by the amount of time the work unit in progress takes to reach its task switch interval or finish. I don't know if that would cause deadline issues later or not, probably would depend on how many units were stuck in the queue.

It really doesn't make all that much difference, when it goes idle, I save a bit of electricity. I haven't figured out what to do with all of those "credits" I have accumulated anyway.

---