Sys Admin: I don't like having WUs queued up on my computers when someone else could be running them. I keep shortening my queue preferences and I'm down to 0.2/0.2 and still you send me too many WUs at a time.

For example, setting the queue to 0.25/0.25 means to me send enough work to fill a half a day and NOT 3 days. This morning on a computer with a single GPU it sent me a WU estimated to take 17 hours to complete. A couple of minutes later it sent me another estimated to take 17 hours.

This also messes up the 24-hour QRB. In this example the second WU would not qualify for the 24-hour QRB. What's the point of even having a QRB if you sabotage it???

---

Projects don't send work (it wouldn't get through your firewall): your client requests work.

I usually get by on 0.25 + 0.05: because I have 'fast' GPUs and 'slow' GPUs, and I only want to run GPUGrid on the fast ones, I have the slow ones excluded, and BOINC only requests one job when the previous one is within three hours of finishing. The occasional task that runs for over 21 hours still catches me out, but it's rare.

The client will request work to fill the queue no matter the length of the task. Tasks will be downloaded until its full and that could be queue time + 1 min or queue time + 10 days. Its all the same.

Yes I've tried queues ranging from 0.04/0.04 to 0.1/0.1 to 0.25/0.25. The queue I set is irrelevant unless it's large.
With a single GPU it's not such an issue. With multi-GPU computers it's a constant problem if I want to run two different GPU projects.

Picky picky, yes my computers ask for work but the server sends ways too much.

---

The client will request work to fill the queue no matter the length of the task. Tasks will be downloaded until its full and that could be queue time + 1 min or queue time + 10 days. Its all the same.

These first two sentences are not the same. I define a small queue and the server overfills my queue with too many WUs.

What the server thinks is full is far more than I need.

"...queue time + 1 min or queue time + 10 days." Where does the + 1 min and + 10 days come from??? The queue time comes from my Computing Preferences "Store at least 0.2 days of work" and "Store up to an additional 0.2 days of work." I ask for less than half a day of work and if I have 2 GPUs it sends me 3 to 4 days of work, way too much. It's taking that "at least" phrase way too far.

I suspect this is a BOINC design flaw and GPUGrid may not be able to do anything about it. BOINC is predicated on the lowest denominator and does nothing to address those that do the lion's share of the work.

---

It's not just a matter of getting the QRB for a WU. If I have too many of anything it changes BOINC priorities in ways I cannot control. If a bunch of lengthy WUs pile up like Bald Eagles under a windmill (tRUMP lie #11,731) then other shorter WUs may not even be sent. The shorter WUs may have a deadline at a later date. The only tool I have available to me is abortion. Abortions cost me nothing but may drive up server costs due to extra data traffic.

---

The client will request work to fill the queue no matter the length of the task. Tasks will be downloaded until its full and that could be queue time + 1 min or queue time + 10 days. Its all the same.

These first two sentences are not the same. I define a small queue and the server overfills my queue with too many WUs.

What the server thinks is full is far more than I need.

"...queue time + 1 min or queue time + 10 days." Where does the + 1 min and + 10 days come from??? The queue time comes from my Computing Preferences "Store at least 0.2 days of work" and "Store up to an additional 0.2 days of work." I ask for less than half a day of work and if I have 2 GPUs it sends me 3 to 4 days of work, way too much. It's taking that "at least" phrase way too far.

I suspect this is a BOINC design flaw and GPUGrid may not be able to do anything about it. BOINC is predicated on the lowest denominator and does nothing to address those that do the lion's share of the work.

It's an example that no matter what the task length is the client on your own PC will fill it with whatever size task is gets. Then it will stop requesting more work. The extra time of that last task could be 1 min over your buffer or 10 days. An example.

Setup multiple clients if you want to run one project on one card and something else on a 2nd card. Then you can set 0.1 + 0 days for a card and you'll never get extra work until your current task is nearly complete.

Using multiple clients to compensate for this deficiency is unacceptable.

---

That's your opinion but you've spent more time typing out your complaints about queues you don't understand than the time it would take to setup another client.

We need a block user feature for people that make ad hominem attacks.

---