I ask the above due to extremely varying times shown for elapsed and remaining times for PrimeGrid work units. A couple of examples: 1> elapsed time ~ 112 hrs. for 40% progress; estimated remaining time ~ 1,603 hr. or 66 days. A simple calculation shows that given the same resources as previously, this job should be done in approx. 168 hr (7 days).
2> elapsed time 10 days for 25% progress; est. remaining time 18 days. Simple calc says should take approx. 3x10 days or 30 days.
The above provided examples for a tasks both under and overestimated timewise. Why is this? Benchmarks are done on one's CPU so why aren't the estimates closer? The real question is: what happens in the second example above. The deadline is 1/16/20, only two days from now, which ain't gonna happen, to put it succinctly. Is the work flushed when the deadline is reached? If so, why should I be participating? If the deadline isn't real, why is it so close? And, why was the work allocated to me when the benchmarks should have shown the deadline wouldn't have been met?
Sorry for so many questions on the same issue, but I find this extremely irritating. Either the deadlines should mean something, or they shouldn't exist.