Stats down again. Get it together, Standford!

I notice that there are apparent problems with the F@H stats server again today. I am seeing a trend here - on most holidays, Stanford has problems with the F@H stats. My experience leads me to the following conjecture:

• The stats services require a lot of manual intervention to keep running; thus when people are off on holiday, there are interruptions in service
• The stats services are poorly architected
• The stats services are poorly designed and/or implemented
• The stats infrastructure is not adequately robust (lacking capacity, dependability, scale, etc.)
• Managers of the project view availability of stats services as a low priority
• Poor management of the stats services contributes to lower confidence in the project as a whole

It's a shame that a project of this size and importance suffers this kind of visible, poor performance. Stats are not beta. They are an important part of the production environment. Stanford needs to get their act together and improve the availablity of the stats services. Perhaps if more top-producing teams complain about it, they would be more inclined to improve the availablity of their reporting.

why do you thing the stats are down again, I see nothing alluding to that

Stats weren't totally out, just individual ones. Team stats were fine. However it is fixed now, I just got 4209 points all at once after 4 updates of 0. They are still updating so the sigs haven't updated yet.

Standford huh?

yeah, it was on fahs's end, not eoc's... http://foldingforum.org/viewtopic.php?f=18&t=5298
but it's fixed.. I just got hot with a 9k update..

Quote:

---

Originally Posted by coo-coo-clocker

I notice that there are apparent problems with the F@H stats server again today. I am seeing a trend here - on most holidays, Stanford has problems with the F@H stats. My experience leads me to the following conjecture:

• The stats services require a lot of manual intervention to keep running; thus when people are off on holiday, there are interruptions in service
• The stats services are poorly architected
• The stats services are poorly designed and/or implemented
• The stats infrastructure is not adequately robust (lacking capacity, dependability, scale, etc.)
• Managers of the project view availability of stats services as a low priority
• Poor management of the stats services contributes to lower confidence in the project as a whole

It's a shame that a project of this size and importance suffers this kind of visible, poor performance. Stats are not beta. They are an important part of the production environment. Stanford needs to get their act together and improve the availablity of the stats services. Perhaps if more top-producing teams complain about it, they would be more inclined to improve the availablity of their reporting.

---

:rofl: Spoken like the typical F@H vet with years of experience. :) Roll with the punches coo-coo. We all do. It's nothing I haven't seen multiple times in 3 years of folding and we'll all see it again. ;)

Standford? Must be a UCLA grad. :rofl: J.K. Coo-coo. It's a CAL joke. :cool: I couldn't resist. :)

Fold On!