Optimizations to stats web pages
Posted: Sat Jan 02, 2010 12:48 am
I just noticed this information on Vijay's blog ...
To be honest, I could care less how many "active" clients I've run within the last 50 days. I really only care about how many clients I've run within the last 7 days to make sure my machines are functioning properly. The fact that the active client counts increase whenever you install the software from scratch makes the information being stored even less meaningful. This problem will get worse in the future as new clients (V7, Protomol, GPU3 and SMP2) are released and more donors participate.
I realize it's the easy way out but I've never really understood the concept of thowing hardware at a problem.
Is it really necessary to keep track of all CPUs that have participated in FAH since inception? Is this information really that useful? It seems like a database purge could be put in place to reduce the amount of data being processed and/or the number of days until a client is deemed "inactive" could be reduced.This change is temporary since the cause is clear: our db keeping track of items like spec ... ed in FAH. This won't be a problem with the new servers, so we will just turn on these features after we migrate. For now, turning off this parts of the stats pages will help a lot until we switch over.
To be honest, I could care less how many "active" clients I've run within the last 50 days. I really only care about how many clients I've run within the last 7 days to make sure my machines are functioning properly. The fact that the active client counts increase whenever you install the software from scratch makes the information being stored even less meaningful. This problem will get worse in the future as new clients (V7, Protomol, GPU3 and SMP2) are released and more donors participate.
I realize it's the easy way out but I've never really understood the concept of thowing hardware at a problem.