archive: Re: SETI@home - Windows + Mac Platforms

Re: SETI@home - Windows + Mac Platforms

Markus Landgren ( marla252@student.liu.se )
Sat, 15 May 1999 08:24:12 +0200

At 18:31 1999-05-14 -0700, you wrote:
>
>--- Jas <jas@optonline.net> wrote:
>> movement. 'Bout time somebody
>> figured out that computer idle=CPU idle.
>
>I haven't been able to find the details I'd like, but I think this is
>what it does if you tell it to run all the time.
>
>This is how D.Net & PrimeNet works. (not to mention the batch of CPU
>cooler programs like CPUidle.)
>

That's true, more or less. However, the SETI@home client is a bit
more agressive when hunting for CPU time. It has a noticeable impact
on system performance, at least when I play mpeg video files or do
something else that requires a lot of CPU time. That doesn't happen
with the D.Net or PrimeNet clients. They run at the lowest possible
priority, and only use the CPU cycles that would otherwise be truly
idle.

Most of the time I use less than 5% of the CPU for my own work, and
the SETI@home client runs just fine in the background without causing
any trouble. I'll be able to run it at least 20 hours per day.

--Markus Landgrenmarla252@student.liu.se