FAD Stats Update... ANOTHER new feature! **UPDATED 02-23**

Toggle sidebar Toggle sidebar
G

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
** 02-23 **
Historical node information has been completely reloaded (I think there may be a couple of older files that failed... I'm looking into them) and the show_node and show_similar_work pages are pretty snappy if I say so myself! :)

More new functionality I've added a page that shows node activity for 5 complete days + today, broken out by upload date/time. This should help to identify dead nodes. Long strings of empy boxes could indicate a dead (or really slow) node. The page can't be lhit yet from any other pages, but you can see it here (fill in your own properly escaped userid):

http://fad.tastats.com/show_nodes_2.php?UserId=TA_GeoffS

:)

** 02-22 **
I've rebuilt the history db file and am now repopulating it from scratch... I made some bad decisions about the file design that were incurring a heavy performance penalty... the new & improved really fast file should be available in an hour or two... it's processing history files at a rate of about 1 every 4 seconds and there are ~1800 of them...

** 02-21 **
Added some color to the work comparision page to indicate whether times are above or below the averages. See it here:

http://fad.tastats.com/show_similar_work.php?p=1t76-q1&j=m38030

** 02-18 **
The nodes page is now updating every 6 hours starting at 0250 EST! :thumbsup:

Now you can click on a protein and see how other people did on that same protein/job! Last upgrade before the weekend... I promise! :p

Next up, I think, is to revamp the first page and update the entire stats every 6 hours :)

Check out... you can link to this page from the Daily Team Stats by clicking on the number in the Nodes column...

http://fad.tastats.com/nodes0001.jpg and http://fad.tastats.com/nodes0002.jpg

* LIVE *
http://fad.tastats.com/show_nodes_1.php?userid=TA_GeoffS&dayoffset=0

Change the dayoffset to whatever you want and you'll see that day's production. The userid has to be in the same case as your registration and has to be properly escaped if necessary.

Clicking on a node number will take you to a page where you can name your node... easier to find those stuck machines!

I'll be adding a 'days offset' parameter so that you can look back into history are far as you please. The default when coming to the page will be 0 = today.

I've had a couple of requests for Estimated CPU Rating... if someone knows how to calculate this, or wants to spend time working on an algorithm so I can keep working on the updates, that would be most excellent!
** ESTIMATED CPU RATING IS IN **

Protein/Job will be clickable to bring up a list of other occurances of that combination in the database so you can compare your results against others.

Got feedback? Bring it on! :D

Geoff
 
U

Unforgiven

Golden Member
May 11, 2001
1,827
0
0
id like to say a special thanks to Geoff in that he pm'd me asking my opinion on improvements to the FaD stats and he's implemented almost everything ive suggested. people like Geoff are the reason that the DC community on Anandtech is the best around! awesome work dude, keep up the great work! :beer:
 
U

Unforgiven

Golden Member
May 11, 2001
1,827
0
0
i found out how to calculate the cpu rating for stats purposes:

points earned for a job divided by number of hours it took to run the job = estimated cpu rating

this is not an exact number but is relatively close to what the cpu rating should be on individual machines.

you need to be fairly precise with the calculation in that if it took you 4 hours and 20 minutes to run a job of 500 points it would look like this:

example:
500 / 4.333333 (since 20 minutes is 1/3 of an hour) = 115.38 est cpu rating
 
G

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
Originally posted by: Unforgiven
i found out how to calculate the cpu rating for stats purposes:

points earned for a job divided by number of hours it took to run the job = estimated cpu rating

this is not an exact number but is relatively close to what the cpu rating should be on individual machines.

you need to be fairly precise with the calculation in that if it took you 4 hours and 20 minutes to run a job of 500 points it would look like this:

example:
500 / 4.333333 (since 20 minutes is 1/3 of an hour) = 115.38 est cpu rating
Click to expand...

Excellent! Piece of cake! :)
 
Freewolf

Freewolf

Diamond Member
Feb 15, 2001
9,673
1
81
Originally posted by: Wolfsraider
Very nice layout and I too am very impressed.
Great job Geoffs :beer:
Click to expand...

Damn my friends do good work :)

Good thing too all I can do is crunch.
 
G

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
Estimated CPU rating is in. This page is accessible from the Daily Team Stats page by clicking on the number of nodes in the user's row. :)
 
Freewolf

Freewolf

Diamond Member
Feb 15, 2001
9,673
1
81
bty that reminds me

Top producer: Rebel_Alliance (105,041 points)

( From your stats page today my friend )

:p


The Doc and I are cooking.

:)
 
Wolfsraider

Wolfsraider

Diamond Member
Jan 27, 2002
8,305
0
76
Hmmm... Let me see what happens today...Might do a burn in on Find-a-Drug lol

If the parts do come in

Guess I'll visit the managers office a tad early :)
 
G

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
Server is down for the moment... upgrading ZoneAlarm... building new indices on the history table... moving new code into place... yeah... all on a Friday afternoon and I'm heading north to Canada for the weekend!! :p

Geoff
 
G

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
Back up with a new upgrade... you can now click on a protein to see how other people did on the same protein/job :)
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom