Out of 90 completed FAH2 that I can still see, there are only 2 where my wingman (first attempt) was "Too Late". All the rest either had a wingman error or had replication = 1. I'm using Windows 10 so I don't see the number of resends that you see.

My tasks on an i5 processor run either 1, 3 or 5 hours. And, as soon as one finishes, the system immediately sends another one to start. I am only running FAH2 and Beta on my computer. I usually pick up several Betas each day.

Only 10 more days till I get my Sapphire for FAH2. :)

I think the answer to the 24 hour deadline is that the work units have such a large number of parts. For instance this one:
FAH2_ 001464_ avx17629-0_ 000008_ 000077_ 028 _ 0--
The "028" means it is the 28th part of this work unit. I seem to recall somewhere that these work units may have more than 100 parts. If that were the case, rather than taking 100 days to complete the entire work unit it could take up to 1000 days ( about 2.75 years) to complete the sequence for that work unit if the deadline were 10 days. I would think the scientists would like their results of the completed work units in a timelier fashion. I believe there is some backend work about putting all the parts of the work unit together to get the final result. This implies that there could be some kind of storage constraint on holding the parts of the work unit until its completion.
If I am off base on this explanation, someone with more information should feel free to correct me.
Cheers

Thanks for the answer. That makes sense, although I can understand why the short deadline can't be handled by everybody... like they say, it's the nature of the beast.

Thanks,
CJSL

Saving the world, one crunch at a time...

The following is from memory and not searching the forums.
When FAHB was first introduced a work unit consisted of 100,000 steps with a trickle up process every 10,000 steps. The next work unit was generated using the output from the returned work unit. A complete ‘unit of work’ consisted of a chain of 10 work units. Each work unit had a 10 day deadline so the complete chain could take about 100 days. Each work unit needed 10 to 15 hours CPU time to complete on a reasonably fast machine (I7-6700).

The project had strange rules which caused the server abort of running work units if the server considered the work unit would not complete before the deadline which was not always popular.
The trickle up process also caused problems for PCs which did not have a permanent internet connection as the upload of the completed work unit had problems if all the trickle up results had not been processed. There were also problems when the upload servers were not available due to maintenance at WCG.

The current work units avoid the above problems but have the disadvantage of the 1 day deadline and the allowance of one work unit per thread. There are two types of work units which contain either 10,000 or 50,000 steps. Looking at my results I can see a 26th generation work unit of 50,000 i.e. 1,300,000 steps. The highest 10,000 series work unit I can see is only 32 generations (but I seem to remember much higher generations in the past) which is 320,000 steps.

The beta for this project is still on-going. There I can see 196 generations of 10,000 steps (1,960,000 in total), 117 generations of 30,000 steps (3,510,000 in total) and 83 generations of 50,000 (4,150,000 in total).

I hope I have remembered correctly.