@SekeRob* Thanks for your answer. I understand. My question was in relation to why you had only specified FAHB work not being sent if it could not be returned with in the 96 hour time frame as the other Is units have the same deadline.

I test ran a few WU from this project even on a high end system I get like 15 hours runtime pretty much like CEP2 with long runs. I don't cache anyway since systems are full time.. my other system will get it done like 17-20 hours. once done my 5 year mission on OET is done.. then will be on this project.. if it trickles work units even that is fine.. systems do other stuff not needing much CPU at all.. :)

I speculate that you are running some Linux variant. OET WU's are using Vina which runs extremely well on Linux. FAAH2 runs on BEDAM which runs completely differently. On my Linux systems any project running Vina yielded about twice the points of any other project, no matter the underlying software.
Cheers

Seen now, 76 days into the project generation #30, so that's how long the fastest target has been observed as completing. With a preprogrammed 4 days allowance, there's 120 days maximum on the shortest series, 160 days for the -ls- tasks, as they are 40 interdependent tasks long. If 120 respectively 160 days is the 'but we can't or want to wait any longer', there's the suggestion a little but of stretch in the deadline is present, but that's only an outside perspective where the techs are in that soundproof, windowless room where hardly ever anything escapes from.

Edit: To add, not wanting to plant a guilt-complex, but it may or may not have escaped you, we regularly see '[Run dry already' where fellow hosts are not getting work because the 'waiting on your result' is one of the factors it seems.

Edit2: And techs, because of this, members are buffering up, so once more, like the senator who does his weekly climate presentation in Congress, maybe time to set a ceiling, for that steadier flow. My Q6600 takes 33 to 35 hours to complete, so I'd be more than happy to have just a few to keep the cores busy when the previous completes.

Other projects aren't reporting their usage until they finish the WU, but I've been seeing FAAH2 reporting that it has used some number of hours, but many more hours are still needed. The FAAH2 WU then keeps running, all 17 hours or whatever, but the credit given is only from that first report. I suspect this is why your average per computing hour is low, there's a chunk of wastage at the end. Like you, I've decided to stop running FAAH2 until somebody gets it straightened out. "status: No reply" with "CPU Time / Elapsed Time (hours): 1.63" just doesn't make enough sense to inspire confidence that FAAH2 isn't a waste of time.