As user capability continues to increase I've noticed that requesting 10 days worth of work only represents a few days for medium-capability users like me. Consequently even short outages (a day or two) leave me with nothing to do. Could this be either increased (e.g. 20 days) or redefined such that whatever was 10 days of work in 2007 is still 10 days of work in 2017 for most users?

On a tangential note, should systems like mine even be processing small CUDA jobs (e.g. <5 min) at all? I'm guessing that the relative transmission overhead is higher for small jobs.

Finally, just out of curiosity, what is the limiting factor for allowing users to request a very high number of work units? I suspect there is a "downside" to this in the extreme, but I'm not sure what it is. Maybe the risk of not meeting the return deadline? The risk of returning work units issued significantly prior to a change in the processing algorithm?

Finally, it has been an honor and my pleasure to support this project. Whatever the occasional problems of the past or present I have great respect the both the leaders and the even larger group of dedicated inner-circle volunteers. You folks represent a model of achieving "greatness on a budget" of which the commercial world can only dream to emulate.

Congratulations, and thanks for all the fish!

There are work unit limits of 100 tasks per CPU Not cores) and 100 per GPU.

This is primarily to prevent problems with massive numbers of tasks being uploaded and down loaded after the outage, which causes problems with writing to the database (as far as I remember)

So, however many days of work you set you will never get more than 100 tasks each for a CPU and GPU.

Great answer -- thanks for taking the time to explain it so clearly.