Need some help understanding stats

[linflas]

Welcome back linflas
Registered Member Since: 06/23/2007

Activity Summary
My Accumulated Points: 3,228
My Current Ranking: 238,671
My Team: XtremeSystems


Detailed Statistics
Statistics Last Updated: 06/25/2007 12:06:03 (UTC) [0 hour(s) ago]

Totals:
Total Run Time (y:d:h:m:s) (Rank) 0:000:19:45:56 (#283,210)
Points Generated (Rank) 3,228 (#238,671)
Results Returned (Rank) 8 (#248,432)

Averages:
Avg. Run Time Per Calendar Day (y:d:h:m:s) 0:000:06:35:19
Avg. Run Time Per Result (y:d:h:m:s) 0:000:02:28:15
Avg. Points Per Hour of Run Time 163.31
Avg. Points Per Calendar Day 1,076.00
Avg. Points Per Result 403.50
Avg. Results Per Calendar Day 2.67

Miscellaneous:
Last Result Returned (UTC) 06/25/2007 09:34:51 [3+ hour(s) ago]
Device Installations 1




Why is my run time average per day only 6 hours? My comp has been idle, other than maybe 2 hours each day, not sure why run time has been limited.

[Martijn]

Because of the quorum system, some work-units will be validated later than the time you return them. If you have a fast system, you have to wait for the others to turn their results in. Because you've only been running for a few days now, I guess that is the problem. It'll go up in a few days :)

Just give it a few days.

[meshmesh]

...
Registered Member Since: 06/23/2007
...
Avg. Run Time Per Calendar Day (y:d:h:m:s) 0:000:06:35:19
...
Avg. Points Per Hour of Run Time 163.31
...
Why is my run time average per day only 6 hours? My comp has been idle, other than maybe 2 hours each day, not sure why run time has been limited.

During the past two days since you registered, you have been running ~22 hours per day.
But since it has only been two days since you started, most of these Working Units returned are still in the pipe line pending validation.

Log onto wcg website
From left menu, go to Results page
Filter by "Pending validation"
You will see many results waiting there until the other participants return their crunched units. These do not count in the stats until proven valid, at which point they will be awarded the points.

Your machine is capable of making 163 points/runtime hour. That is per core. This is imressive. My guess is that this is probably a C2D or a quad running at ~3.6 Ghz, so multiply this value by number of cores.

Just leave the machine running for a month, and look back at the daily stats. The numbers will stabilize. Don't worry, it is just like money deposited in the bank. It takes up to 5 working days to be added to your account.:)

For more detailed info on the credit system, have a look at this post (http://www.xtremesystems.org/forums/showthread.php?t=138424)

Edit: as Martijn said.

@martijn: "Xtreme PSU Killer" :D

[Martijn]

Edit: as Martijn said.

@martijn: "Xtreme PSU Killer" :D

Isn't it true? :shrug:

[linflas]

Thanks guys, yes many are pending, thanks, was just wondering if Vista was F*cking up something else in sleep or hibernation or whatever bullsh*t M$ calls it this week.

Meshmesh nice guess, lol, I scaled my clock back for folding to make sure I got it right, will run 3.6 for a week or two then put it up to 3.85 again and see what it does. E6600.

Thanks again guys, I did read the post about how the points worked, but did not put that together with time running, makes sense I guess as it is only counted the completed and validated parts.

[sierra_bound]

It usually takes about a week before you can get a better idea of what your computer is capable of producing point-wise on a daily basis. The validation process is sometimes slow, especially on weekends.

[mcflurry4321]

lol @ meshmesh with a perfect guess.

[sierra_bound]

Just wanted to add a few things about points. If a work unit is classified as an error, you get no credit. Errors are almost always caused by system instability. If a result is ruled to be invalid, you get half-credit.

[linflas]

Just wanted to add a few things about points. If a work unit is classified as an error, you get no credit. Errors are almost always caused by system instability. If a result is ruled to be invalid, you get half-credit.


That is why I dropped my clock to make sure it was rock solid, so far so good, everything validated! Except for some of the small projects I have received more points than listed as claimed, so everything seems to going well, will do as suggested and just sit back for a few weeks and let it do it's thing.

I am 99% sure of my 3.85 clock as I am 24 hours prime95 stable, but wanted to check temperatures and such for a few weeks, so far so good, have not hit abouve 45C during the last 2 days, so looks good.

[meshmesh]

Thanks guys, yes many are pending, thanks, was just wondering if Vista was F*cking up something else in sleep or hibernation or whatever bullsh*t M$ calls it this week.
if you want to keep it crunching continously, do not allow the machine to go into sleep or hybernation. Disable the "feature". Power otion = Always On. Blank screen saver to minimize GPU power draw and use monitor off button when not infront of machine.

Meshmesh nice guess, lol, I scaled my clock back for folding to make sure I got it right, will run 3.6 for a week or two then put it up to 3.85 again and see what it does. E6600.
As long as it gets all it's WUs valid you can inch it slowely. At the current 3.6 Ghz, estimate ~ 7600 ppd. Once the machine has run uninterrupted for two weeks at a specific setting, I average over a 7 day cycle afterwards.

[linflas]

if you want to keep it crunching continously, do not allow the machine to go into sleep or hybernation. Disable the "feature". Power otion = Always On. Blank screen saver to minimize GPU power draw and use monitor off button when not infront of machine.


As long as it gets all it's WUs valid you can inch it slowely. At the current 3.6 Ghz, estimate ~ 7600 ppd. Once the machine has run uninterrupted for two weeks at a specific setting, I average over a 7 day cycle afterwards.

Yea turned off sleep hybernation the first few minutes after installing Vista, although with Vista you never can tell what you get when you do that. My first install, no matter what options I used it would hybernate and kill the sata controller, and would not fire back up. This install has been up for 5 months now and seems to be doing fine.

My monitor shuts off after five minutes of Idle anyway, so from looking at my numbers everything is going well, will have a better idea, I am sure like you said in 2 weeks.

Will be going quad at the end of July, so will have a week or so of tweaking getting a new overclock stable. Then will have a quad, and this E6600 to crunch with. The E6600 will go into the media center which is an older P4, will try and get that one up for crunching to, put it in a hole in the basement somewhere cool.

[SIOUX]

Yea turned off sleep hybernation the first few minutes after installing Vista, although with Vista you never can tell what you get when you do that. My first install, no matter what options I used it would hybernate and kill the sata controller, and would not fire back up. This install has been up for 5 months now and seems to be doing fine.

My monitor shuts off after five minutes of Idle anyway, so from looking at my numbers everything is going well, will have a better idea, I am sure like you said in 2 weeks.

Will be going quad at the end of July, so will have a week or so of tweaking getting a new overclock stable. Then will have a quad, and this E6600 to crunch with. The E6600 will go into the media center which is an older P4, will try and get that one up for crunching to, put it in a hole in the basement somewhere cool.

Same thing here....you need to go under advanced power settings, and tell your harddrive never to power down :)