However, one thing to note is that SETI @Home doesn't seem to be as "idle
priority" as Prime95 is. I ran it for a while, and I felt I could notice a
slowdown, and when it wasn't minimized, there was a VERY noticeable
slowdown. I think SETI @Home actually steals more than just idle cycles,
and gets a few more.
--Peter
At 22:45 06/04/1999 -0400, you wrote:
>The message of the day on the Sun machines here at the University of
>Michigan included the following today:
>
> * * * * *
>Please do not run the Seti At Home program on the Login Servers. Although
>it is for a good cause, the Login Servers do not have any spare CPU cycles
>to donate. Running Seti At Home interferes with other users getting their
>work done.
> * * * * *
>
>This illustrates the importance of getting permission before running
>processor-intensive programs on machines that are not entirely your own.
>There are only about thirty people logged in on the machine that I'm using
>right now, and as usual almost all of them are running Pine; even with
>this comparatively light load the slowdown was apparently bad enough to be
>a problem. I suspect that people trying to run Seti on these machines at a
>peak time of year would create a big performance drag, and force the
>administrators to monitor individual users' processor usage more closely
>to prevent such abuses. It is easy to forget about such consequences in
>the quest for CPU time.
>
>I'd like to think that GIMPS members, on the whole, do not deserve
>warnings like the one above. Let's keep it that way.
>
>
>David A. Miller
>[EMAIL PROTECTED]
>
>________________________________________________________________
>Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
>
________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
