I just got my first batch of results for this project.

They have a absolute impossible return time of 8 hours.
I am offline longer than that during the night . I don't run 24/7.

Please make the deadline longer. Minimum 2 days.

The batch I just got only ran for a couple of minutes. Guess this project isn't for you.

The batch I just got only ran for a couple of minutes. Guess this project isn't for you.

I think you are confusing run time and deadline here. An eight-hour deadline is ridiculously short, especially when you run more than one project -I run forty.

---

The batch I just got only ran for a couple of minutes. Guess this project isn't for you.

I think you are confusing run time and deadline here. An eight-hour deadline is ridiculously short, especially when you run more than one project -I run forty.

I am not.

If someone can't complete a task that will run for like 5 minutes and that starts immediate in high priority then again, the project is not for them. The deadline is short but if they don't run their PC all the time then they can't expect to have every project cater to them.

No matter if you run 1 thousand projects, the tasks are high priority and will run right away.

mmonnin, not a very nice attitude.

I just made the remark that I found the deadline very short in the hope that the admin will change it.
If the admin has a reason not to do that, then I will decide what to do with this project.

I just recieved over a hunderd new results and I noticed the runtime is not the 5 minutes you mention but it is variable. Some are much longer.
It would help if the admin created in the preferences the option to limit the number that is send to a user.

The return deadline of 8 hours became just even more ridiculous.

A result killed itself after running for about 3,5 hrs because it hit a max runtime limit.

If a result runs that long it is either a error or it has found something that needs a lot of time to figure out.
A error should die much sooner, it is waisting time.
A good result should get all the time it needs and not run into a runtime limit or a retum deadline.

a deadline under 24h is ridiculous. even more when some taks take up to 4 hours to complete...

---

I just downloaded 31 wu's on this host and could not complete any within deadline.
Most were Not started by deadline - canceled
https://boinc.nanohub.org/nanoHUB_at_home/workunit.php?wuid=234066
https://boinc.nanohub.org/nanoHUB_at_home/workunit.php?wuid=234075
I also produced a few Error while computing results
https://boinc.nanohub.org/nanoHUB_at_home/result.php?resultid=416303

The host is still trying to complete one task that is beyond deadline. I smile because I sometimes do the exact same thing.

---

Today I had a set of results that were all resends. All had a number _3 extension.

I did a few of them but most hit the deadline and have been send out again to the next user.
If this user also fails to do them on time they will hit the max results allowed number and will be killed permanently.

This shows how dumb this short a deadline is. You get a lot of resends, each for a extra 8 hours wait time or the work won't get done at all.
A longer deadline will get a higher success rate and will reduce network and database load.

+1 for a deadline increase to at least 24 hours.

I just downloaded some work with a 1 day deadline

I think that is still to short for users who don't run 24/7 and that the minimum workable is 2 days.
But I will give it a try.

We did extend the deadline to 24 hours for all new WUs. We will watch over the next few days to see if it should be extended to 48 hours.

We did extend the deadline to 24 hours for all new WUs. We will watch over the next few days to see if it should be extended to 48 hours.

Please do make it 48 hours.

However that will not fix another problem, the variable runtime of the results.

They go from a few minutes to 4 hours but they all show up on my host with a estimated run time of about 20 minutes.
So if my host asks for enough work for half a day I may get in reality work for 6 full days and then I will hit the dealine problem again.

You have to find a way for the estimated runtime to be closer to the real runtime for each seperate result.

I have already in a earlier post made the request to give users the option to limit the number of results they download.

There are plenty of options via BOINC Manager and app_config.xml files to limit the # of tasks.

There are plenty of options via BOINC Manager and app_config.xml files to limit the # of tasks.

It is impossible to set a limit on results in the BOINC Manager.
I don't know any way to do that in app_config.xml. Please post a example.