You probably need to set the <sched_op_debug> logging flag in cc_config.xml, so you can see in a little more detail how much work (how many seconds) your computer is requesting, and how long the work you receive in response to those requests is estimated (again, by your computer) to take.

800 isnt "a lot". I assume your GPU is getting these WU's because seti thinks it can crunch them before the deadline. A newer GPU can run through 300+ a day.
I assume your's isnt the latest greatest.
If you think you are getting to many WU's, then reduce your cache to 1-2 days. If that is too much then change the "contact server every" to 1 day or less.

Just a demonstration. I have 1 PC that currently has 4800 WU's in progress. My PC's with GPUs all have large caches. In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

If I have tasks which continue running after reaching 100% (No, I don't mean just 10 Minutes) I have to reboot my machine.
If I only close BOINC and restart it it will resume from last checkpoint but still not complete the task.
I will write to the Alpha mailing list about it tomorow or so to find out which log flags to set.

And then wait for it to happen again in a couple of weeks..........

Addition: did the estimated time to completion go down significantly? Then you need to wait and complete at least 10 tasks (which need to validate) for that the server will re-calculate the time correction factor.Christoph

Min work buffer is 5.00 days, Max additional work buffer is 0.01
(sniporest)

Ok, there was a huge shorty storm a while back, which may have caused your experience. If you card was capable of crunching 7 work units an hour set to crunch 3 at a time, 24 hours a day with a 5 day cache, 800+ work units in your cache is a reasonable number.

My wild ass guess is the servers saw you going like gangbusters through work units (shortys remember) and at the same time something was done at the servers to increase the number of downloads per request. There were posts of people getting 100+ work units per download so what you saw was your cache FINALLY being filled up to its maximum for 5+ days worth of work.

I can see where that might be unsettling to someone who never has experienced that sort of thing before.

What you can do is set from .33 to 1 for how many work units to run at one time (which I see you have done). This should drop the number of downloads by 2/3rds BUT NOT IMMEDIATELY. There is some time lag in the system that would make this take a few days. Quicker would be to set your cache down to 1 day max and .01 additional. This will probably cause Seti to go into high priority mode to clear out the excess. DON'T WORRY about it, just be patient and give Boinc a week to settle down.

What the problem really was was not that you got a metric buttload of work units all at once but that you weren't getting all the work units you were previously requesting in the first place.

To figure out the cache you want take the number of work units your gpu and cpu can do per hour (on average), multiply that by how many hours a day you are going to crunch work units.
Say 5 wu per hour for gpu and 2 per cpu. (5 + 2)X 24hrs= 168 per day
If you want 5 days cache expect to see about 5 X 168= 840 work units in your cache if everything works as it should.

In the mean time patience, there is quite a bit of lag built into Boinc.
Don't worry about High Priority.
Don't worry about missed deadlines.
Don't worry about wingmen.
What ever you don't get done will be done by somebody else eventually.
This is not a race. Just give your system a few days to weeks to settle down. As long as you are not producing errors everything will adjust itself eventually.

Now here is where others tell you where I'm wrong, The good thing is that between me and them is that you'll get the answer you want. :)

I'll run with a GPU count of 1 for a week, and then see if I can move to .33 again.

I was more worried about WUs that reached 100% staying there and not moving from BOINC Manager preventing others from starting.

Anyway, I'm currently running with app_inf set to count 1 and everthing is running and reporting ok.

Again thanks Bill

You're welcome.

I would wait at most an hour on the ones that seem to be hung at 100% then abort them. maybe it's the work unit or maybe it's machine but no sense letting it run for ever. Like I said it will be crunched by somebody eventually if it's crunchable. If all of the work units hang then I'd look into a computer solution. If it's a bad work unit a history of more than one person aborting it will show it. Aborting a work unit is not a crime.