Average CPU efficiency 0.937621
Result duration correction factor 0.52257

What are they, or what do those number represent?

/Thanks

---

/Mav

We have lingered long enough on the shores of the cosmic ocean.
We are ready at last to set sail for the stars.
(Carl Sagan)

Not too sure on the Average CPU efficiency but the Result Duration Correction Factor (RDCF or DCF) indicates how much faster you are completing units than the benchmark calculates. It is used these days with the benchmark to calculate completion time and therefore the amount of work you can download. It takes 20 to 25 units to be crunched to become stable, after that your work cache if you have one should be ~correct. But if you have a problem and computer slows down DCF is immediately increased.

Andy

edit/ If DCF is over one you are crunching slower than expected. Yours says you are nearly twice as fast as benchmark indicates.

I've always taken "Average CPU Efficiency" to be the ratio of actual time time work is scheduled by BOINC to the CPU time used - more accurately the other way round.
So if BOINC is allowed to schedule SETI work 24 hrs a day (and has WUs to do), the total SETI CPU time won't ever reach 24Hrs, as some CPU gets used by whatever else you run on the host, and some is always used by the operating system overhead.
Thus, I believe that and Average CPU efficiency of .737621 means that approximately 6.3% of the time the CPU could have been running SETI it was doing something else instead.

---

Average CPU efficiency 0.99947
Result duration correction factor 0.475804

Can't get much more efficient than 99.947%
:)

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.

Average CPU efficiency 0.99947
Result duration correction factor 0.475804

Can't get much more efficient than 99.947%
:)

I can beat that:

http://setiathome.berkeley.edu/show_host_detail.php?hostid=882512

And no, I haven't "doctored" any of the state files manually, BOINC did that all on its own. :-)

Alinator

I'm afraid we can't see your CPU efficiency. It is only visible to the owner if they are logged in.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

LOL, sorry forgot about that! :-O

% of time BOINC client is running 99.664 %
While BOINC running, % of time work is allowed 99.9847 %
Average CPU efficiency 1.000033
Result duration correction factor 3.300521

Although, I don't see how this is "classified" info from a privacy POV. :-)

But since BOINC considers it so, I guess I have to kill you all now! :-D

Alinator

% of time BOINC client is running 99.4613 %
While BOINC running, % of time work is allowed 99.4921 %
Average CPU efficiency 0.959019
Result duration correction factor 1
******************************************************************
are these numbers good??

% of time BOINC client is running 99.4613 %
While BOINC running, % of time work is allowed 99.4921 %
Average CPU efficiency 0.959019
Result duration correction factor 1
******************************************************************
are these numbers good??

excellent compared to my slug
% of time BOINC client is running 97.3688 %
While BOINC running, % of time work is allowed 99.8164 %
Average CPU efficiency 0.8634
Result duration correction factor 1.621406

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Not too sure on the Average CPU efficiency but the Result Duration Correction Factor (RDCF or DCF) indicates how much faster you are completing units than the benchmark calculates. It is used these days with the benchmark to calculate completion time and therefore the amount of work you can download. It takes 20 to 25 units to be crunched to become stable, after that your work cache if you have one should be ~correct. But if you have a problem and computer slows down DCF is immediately increased.

Andy

edit/ If DCF is over one you are crunching slower than expected. Yours says you are nearly twice as fast as benchmark indicates.

Great, thanks!
I thought it had something to do with the fact that estimated times to completion seemed to change in boinc manager. I knew this version used some formula to adapt it, but didn't realize that number was part of it.

Regards.

---

/Mav

We have lingered long enough on the shores of the cosmic ocean.
We are ready at last to set sail for the stars.
(Carl Sagan)

My Family host:
% of time BOINC client is running 97.6136 %
While BOINC running, % of time work is allowed 99.9836 %
Average CPU efficiency 0.87816
Result duration correction factor 1.200372


My moms computer:
% of time BOINC client is running 63.0599 %
While BOINC running, % of time work is allowed 99.7486 %
Average CPU efficiency 0.826643
Result duration correction factor 0.925075

I guess they are ok.

My computer runs 24/7, but I run a bunch of projects. My moms computer, runs when she's playing online games, maybe 12 hours a day, give or take some. :-)

Jeremy

---

This one is a single CPU system !? CPU efficiency is supposed to be in the range of 0 - 1 / CPU. So a two CPU system could have a value up to 2.0 for CPU efficiency.

% of time BOINC client is running 99.8143 %
While BOINC running, % of time work is allowed 99.9847 %
Average CPU efficiency 1.418211
Result duration correction factor 1.203126


This one obviously has run into a snag - probably one of the alpha test projects.

% of time BOINC client is running 99.7839 %
While BOINC running, % of time work is allowed 99.9248 %
Average CPU efficiency 0.286162
Result duration correction factor 0.765348

---

BOINC WIKI

This one is a single CPU system !? CPU efficiency is supposed to be in the range of 0 - 1 / CPU. So a two CPU system could have a value up to 2.0 for CPU efficiency.

% of time BOINC client is running 99.8143 %
While BOINC running, % of time work is allowed 99.9847 %
Average CPU efficiency 1.418211
Result duration correction factor 1.203126


This one obviously has run into a snag - probably one of the alpha test projects.

% of time BOINC client is running 99.7839 %
While BOINC running, % of time work is allowed 99.9248 %
Average CPU efficiency 0.286162
Result duration correction factor 0.765348

Mine is as follows:

% of time BOINC client is running	78.6456 %
While BOINC running, % of time work is allowed	99.9906 %
Average CPU efficiency	0.998497
Result duration correction factor	1.037531

Of course It's been really warm lately so since I overclock I had to adjust the cpu speed a couple of times, Outside the house It was 115F on Sunday, Inside It was 92F. Of course today was a bit cooler and more humid, We're expecting Thunderstorms as It's the Desert Monsoon season.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This one is a single CPU system !? CPU efficiency is supposed to be in the range of 0 - 1 / CPU. So a two CPU system could have a value up to 2.0 for CPU efficiency.

% of time BOINC client is running 99.8143 %
While BOINC running, % of time work is allowed 99.9847 %
Average CPU efficiency 1.418211
Result duration correction factor 1.203126


This one obviously has run into a snag - probably one of the alpha test projects.

% of time BOINC client is running 99.7839 %
While BOINC running, % of time work is allowed 99.9248 %
Average CPU efficiency 0.286162
Result duration correction factor 0.765348

I'm not sure who you were responding to here John, but the one I have showing an efficiency >1 is a K6-2, which is why I found it humourous it's reporting that value. It hasn't run an SAH result in a while, but 1.000033 is what came up after it reported the last time.

All the others K6's are in the .98 to .99 range. I guess I should let it run another result and see what happens.

Alinator