Depends where you're reading "estimated". There was a server bug (#4151) which did exactly that, which is now fixed - we fixed it for the forthcoming CPDN MT tasks - but most servers won't yet have the fix.

Bit the client - I think - has always recorded elapsed time accurately, and once the initial ropey estimates have worked their way out of the system, they should be accurate, too. Even the "[sched_op] estimated total CPU task duration: 12221 seconds" in the Event Log should be OK.

I will see what happens after a few more tasks have run.

I will see what happens after a few more tasks have run.

After seeing an initial increase in estimated time the latest one download is estimating 4hourst 25 minutes which seems realistic. First several were all estimating between 15 and 19 hours something. The change in estimated time seems to have settled on a realistic figure, much more slowly than I have experienced in the past.