« FLOPS | Main | Power surge on campus -- servers down »

March 20, 2009

Comments

Daniel

Seems like a good idea there. I've only ever briefly looked at mine in the 2 years I've been folding.

Kyle

Yeah, while occasionally I find it interesting to look at how many WUs I've done for a particular project, it's much more common that I get slightly annoyed because the stats are still in update mode. It's not a feature I'll miss all that much.

brityank

Dr. Pande,

Something I've noticed is that there are a large number of members who are no longer contributing to the projects. How about setting a six-month delete point for failure to update to cut back on the full overhead?

Trotador

I would much prefer to keep them. I check them daily.

I agree with previous comment that it could be removed (I'm not sure if just from stats web site or permanently deleted) for those member that have not contributed for a long time. Six months seems a reasonable period

Kamaradski

Hi all,

I hardly ever look at the WU's per project, so if it drasticly improves stat-updating.

On the above mentioning of deleting inactive users or cpu's, i disagree. It will impact the team-scores of teams that hold inactive members. Unless there is a way to make the results of those inactive users and CPU's static and therefore removing the need to process them again and again. You should never manipulate stats by deleting information.

Cheers kamaradski

Stephen Dewey

What about just running the project-specific stats update less frequently, e.g. once every month? While people check those lists less frequently, they are still interesting.

I disagree re: deleting old members. Not only would it mess up team statistics, but it is also unfair to those members, since they did at some point make a contribution. It might be possible to achieve some optimization by updating "dormant" members' statistics less frequently, however, depending on the organization of the database.

Luke Elliott

I definitely am against this big time. Because I for one want to know what projects I'm working on, and how much work I've put against each project. The reason being is, if I'm really interested in helping out with Alzheimers, finding out that I am doing a lot of work relating to that, feels good.

Why don't we move it to just once a week update.

Johan

It's a pity that you don't update it at all anymore. I think it would be better if, like many others said here, you update these numbers once a month or something lika that.

Jim Smitts

Yeah, just like many others here, maybe once a day, once a week, once every other week, but no longer then once a month. I think you should do a poll before you decide on what people want. I for one would like it to occur once a week at the longest.

slls

There was a poll, and majority voted for omitting the project/wu count in order to speed up the stats update.

Kyle

"If so, what's the point in telling people anything about what WU they are doing."

Knowing what WU you are working on can be very helpful for the devs/mods for debugging purposes (both their issues and your issues). It also allows you to make rough comparisons with other people as to how well you computer is folding.

I will somewhat redact my earlier comment and say that I wouldn't have a problem with the project count being updated on a less regular basis. Is it possible to keep that info stored without updating the main database, or would doing that lead to slowdowns elsewhere?

nelson

how about every 15 menits update score

The comments to this entry are closed.