I have one QC task and one Long run task running on my main Linux box. So far I have made 42 QC tasks and 27 Long run tasks.
Tullio

I'm crunching several CPU only projects. Not all projects have work available at all times, but rather release batches that are done within a week (e.g. Sixtrack). Other projects take regular maintenance breaks (but not this past week). Consequently my system will hop projects and try to level out quotas.

I'm usually buffering fewer than 10 tasks. I never exceeded that number, although I must admit I was playing around with the project (emptying and filling the queue), because it's tasks are peaky and hot on my CPU. If there is anything you could do to fix that without impacting performance, I would appreciate it.

EDIT: Keep in mind GPU tasks had issues lately. Perhaps more volunteers tried to setup QC but abandoned their tasks?

LAST EDIT: I know several other projects have disappointed CPU volunteers, so maybe these volunteers increased their work share with GPUGRID?

DANG IT BOBBY I SAID LAST EDIT: I did switched from the default 4 CPU tasks to 1 CPU tasks a week ago with an app_config.xml modification. Of course the number of tasks I buffer increased accordingly - but I would guess this was last week.

My guess is some users have their BOINC set to a queue of 10 days and an extra 10 days of WUs which can equate to hundreds if not thousands of WUS. If you have multiple people doing that, it will add up.

I keep my queue at 0.5 days so I'm not bombarded/hog all the WUs.

I think the only way to tell if there is an increase of computing power is on your end. You can tell how many WUs are coming back per day vs previously.

What's going on? Are people buffering/hogging more WUs or is it an actual increase in computing power by the users releasing CPUs from the GPU queue to the CPU queue?