What is the above?
I notice most of my PC\'s are set to 1.0, wheras my Atlon 64 3000+ has a figure 1.424242.
What is this telling me?

---

p.s.

I have just realised that this machine looks a though it has been struggling with a misallocated result and I have reset the project.
Has this something to do with it?
I also notice that my Linux machine is not showing a \"Result duration correction factor.\"

---

I can\'t see this on mine.
Where abouts is it displayed?

I can\'t see this on mine.
Where abouts is it displayed?

My machine number is 170146

It is down the bottom of the page below \"Average CPU efficiency\" and above \"Location\".

Is it to do with using Boinc 5.2.2
Windows XP Home.

---

It must be 5.2.2
I don\'t have \"Average CPU efficiency\" either.
I\'m still on 4.25

At least the other person won\'t be getting your credits now. :)

There may be something about 5.2.2 on the SETI site, as they have far more people than us.

I found it mentioned in the BOINC Wiki <a href=\"http://boinc-doc.net/boinc-wiki/index.php?title=Version_History_of_The_BOINC_Client_Software\"> here,</a> under Major Features of Version 5.x.x. But no explanation.

The duration correction factor (DCF) is used in determining how long a result will take to complete.

BOINC makes an initial estimate based on the system\'s benchmark figures and the estimated number of floating point operations specified for the result (actually in the workunit, but that\'s just nit-picking). This is then weighted by the DCF for that project.

As a result is processed the project\'s DCF is modified to improve the time estimate.

Unfortunately the initial estimate is way out for CPDN (I\'m seeing a 50% over-estimate in spinup testing!) and the adjustment downwards is in very small increments. My guess is that it\'ll take at least one complete result on your host to get the DCF down to the point where BOINC gives a reasonable estimate for CPDN.

I can see this causing problems for people who are running multiple projects, with BOINC being forced into EDF scheduling mode unnecessarily because it thinks a CPDN result isn\'t going to meet a deadline that\'s easily achievable.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

I found it mentioned in the BOINC Wiki <a href=\"http://boinc-doc.net/boinc-wiki/index.php?title=Version_History_of_The_BOINC_Client_Software\"> here,</a> under Major Features of Version 5.x.x. But no explanation.

Sorry the link is in now. The page is here: http://boinc-doc.net/boinc-wiki/index.php?title=Result_Duration_Correction_Factor

---

BOINC WIKI

BOINCing since 2002/12/8

Thanks for the link. Looks like lots of new things to learn.