so i downloaded the client and got my first work unit yesterday. it has 75 hours to go and a deadline in 4 days. now you see, the only way i could meet that deadline on the default settings - that is, boinc only running when i'm not using my computer - is if i left my computer running 24/7 and never used it.

i'm sorry but my computer is not a dedicated compute node for you. i have to pay power builds and i did not purchase my graphics card just for gpugrid.net. there is no way in hell mu machine will ever make that deadline, and if the deadlines continue to be like that, there is no way in hell my computer will ever make ANY of them. so what, does all the work get thrown away then? that sounds downright retarded.

deadlines should be more on the order of months. their only purpose is to be able to reassign a work task on the very rare chance that one gets orphaned, by say someoen reformatting their hard drive or something like that.

deadlines DO NOT effect the rate of processing results, with the exception of they are too short, in which case they an enormous effect on it - it can bring it to a practical standstill in short order.

so make the deadline months out as they should be and which your effective computing power instantly jump an order of magnitude at no cost to anyone.

so i downloaded the client and got my first work unit yesterday. it has 75 hours to go and a deadline in 4 days. now you see, the only way i could meet that deadline on the default settings - that is, boinc only running when i'm not using my computer - is if i left my computer running 24/7 and never used it.

i'm sorry but my computer is not a dedicated compute node for you. i have to pay power builds and i did not purchase my graphics card just for gpugrid.net. there is no way in hell mu machine will ever make that deadline, and if the deadlines continue to be like that, there is no way in hell my computer will ever make ANY of them. so what, does all the work get thrown away then? that sounds downright retarded.

deadlines should be more on the order of months. their only purpose is to be able to reassign a work task on the very rare chance that one gets orphaned, by say someoen reformatting their hard drive or something like that.

deadlines DO NOT effect the rate of processing results, with the exception of they are too short, in which case they an enormous effect on it - it can bring it to a practical standstill in short order.

so make the deadline months out as they should be and which your effective computing power instantly jump an order of magnitude at no cost to anyone.

kevin,

If you think the 5 day deadline is bad news then wait... it gets even worse. If you don't return your result in 3 days they replicate the task to another host. That's right, they have 2 "deadlines" here: the 5 day one you are already aware of and the 3 day one. So if you're concerned about efficiency and not duplicating work then you want to get your results back within 3 days, not 5.

Also, there is a 50% credit bonus for returning a result with 12 hours. That should tell you how much they value quick returns here. It's because they generate work units pretty much "on the fly", as Retvari explained already.

Also, there is a 50% credit bonus for returning a result with 12 hours.

Reading this post made me aware about:

You should unselect the "ACEMD for long runs (8-12 hours on fastest GPU)" in your profile