Hi, Help,

First, sorry for my english, I'm french and not fluent ;)

The last task from milkyway@home was 28 hours instead of 4 hours usually, but the same time to go to the deadline !

Few days after, the time spent is now 44 hours and only 17% running (the lasting time is still increasing 3 hours this morning, 6 hours now !!!) !!!!
Deadline is 22 of august. It's too short !!!

The computer is an old one, only used for "milkyway" & "seti" but I never had such problem of too short deadline with "milkyway" !

What to do ?

Thanks.

Some of the tasks lately have had outrageous processing time. I'm not sure what happens to overdue tasks on this project, but I would think that you could just abort it if it looks like it's not going to finish in time. Once the deadline has passed, the task is resent to somebody else anyway.

Hi, Help,

First, sorry for my english, I'm french and not fluent ;)

The last task from milkyway@home was 28 hours instead of 4 hours usually, but the same time to go to the deadline !

Few days after, the time spent is now 44 hours and only 17% running (the lasting time is still increasing 3 hours this morning, 6 hours now !!!) !!!!
Deadline is 22 of august. It's too short !!!

The computer is an old one, only used for "milkyway" & "seti" but I never had such problem of too short deadline with "milkyway" !

What to do ?

Thanks.

One idea would be to lower your cache settings so you don't have so much work on your pc waiting to be crunched, it just means you will be contacting the project more often and will still give you plenty of work as long as your internet connection is reliable. For instance my cache settings are 0.75 days in the first box and then 0.25 days in the 2nd box. That results in just about 1 days worth of work, counting the units in progress, and keeps me away from any deadline problems.

The problem with older pc's is that we have already crunched all the 'easy' and short units, now we are getting to the harder ones and the older pc's are struggling. They ARE still valuable AND needed, but maybe another idea for you would be to crunch for one project this month and then switch to a different project next month. Concentrating your resources instead of trying to do it all at once. At Milky Way we are mapping the Milky Way, that is not going to be finished today or even tomorrow, likewise Seti is searching for 'the' signal. If and when they find one they will KEEP looking for more, as then they have proof that their way does work.

Some of the tasks lately have had outrageous processing time. I'm not sure what happens to overdue tasks on this project, but I would think that you could just abort it if it looks like it's not going to finish in time. Once the deadline has passed, the task is resent to somebody else anyway.

Overdue tasks are treated just like aborted tasks, resent to someone else to crunch. That is sometimes why the credits can seem to be slower then at other times. If for instance you and I get the same units and we both return it within 12 hours we will get the credits fairly quickly, but if my pc crashes and I don't crunch the unit at all, then you will be waiting for the deadline to expire on my pc, but will also then be waiting on the next person to crunch the unit. If they TOO let it expire and it gets resent to still another person...well you can see why sometimes it can take a while.

Thanks, it's clearer now :)
I prefer abort the task and, to review, as suggested by Mikey, the preferences of my manager.
Thanks you from Paris ;)