I keep getting 3.3.27 WUs that upon arrival have an estimated time to completion between the 60 and 80 hours, while in effect they are ready after some 4 hours of crunching. My fellow team members came up with suggestions as:

boinc tends to give some very off estimates in many projects... but it has its learning curve and after a good number of workunits it gets it right

and

This is to prevent a newly attached client from getting flooded with work.

but that does not hold because those same machines run WuProp since November 2010 -and in doing so must have a pretty steep learning curve-, and you cannot flood your PC with WuProp WUs.

---

Hi Dirk.

You are correct that the WUProp project sends only one work unit per client at a time.

It is possible that the estimate baseline was reset when the latest client app was released on 29 Sept.
http://wuprop.boinc-af.org/apps.php
The original WUProp work units ran for much longer than the current length.

On the AMD Users forum you also observe that the estimate is getting longer.
I can confirm that I see the same thing on my clients also.
That behaviour is a puzzle.

There could be some other reason that the Admin may share with us?

Looks like my estimates are coming down again.
They exceeded 90 hours this morning, but now are back down to around 34 hours.

This has started again, around 80 hours estimated run time.
Causing work fetch problems for other projects, the ones that WUProp is trying to measure.

Version 3.27

Conan

---

This has now increased to 115 hours estimated run time.

Conan

---