That wouldn't work to well, many people run it on a "variable" number of
machines. I've run it on as few as one and as many as eleven. Right now
it's chugging away on eight. So what would my "system count" be?
Besides, to track that would mean gathering more data on users machines, and
that could get them into a privacy problem.
Uray
I don't have a problem with listing the number of computers that are working
for each person (in fact, I think that would be an interesting stat to have,
along with rankings showing how I compare to other people using the same
number of systems); however, this is more than we can reasonably expect from
the people running this project as they have far more important things with
which to concern themselves.
Perhaps we would all be better off if S@H got rid of all the statistical
reports and rankings. Afterall, how many of us joined up and started
running the software for the stats? Isn't the science what we should
concern ourselves with?
-MRiley *
george a. <tec...@yahoo.com> wrote in message
news:381F68CD...@yahoo.com...
Same for me. I was running up to 5 clients (UnixWare 7, linux, Win95/98
GUI), but at the moment I can't get more than 2 running (UnixWare 7, Win
95).
> So what would my "system count" be?
Just a suggestion: S@H has the date, when a user got his account. So
they could add a "statistical field" with CPU time divided by the time
since signing up. This would at least give a feeling of how many CPUs a
user would use in average.
> Besides, to track that would mean gathering more data on users machines, and
> that could get them into a privacy problem.
>
--
Stefan Bauer
It might be an interesting statistic, but CPU count isn't the only factor
that would influence it. The time SETI is running on each machine would
matter as well. I could have one machine running for 24 hours, or I could
have 24 machines than only ran it for an hour each. Both situations would
give me 24 CPU hours of SETI per day.
Uray
An even better method is when client, CPU-type and OS are also considered
(CPU clock and FSB frequenty, cache(s), RAM).
Gr. Jan