From: Eugen Leitl (eugen@leitl.org)
Date: Sun Apr 07 2002 - 23:52:13 MDT
On Sun, 7 Apr 2002, Adrian Tymes wrote:
> At which point, with Kazaa taking excessive CPU power (unless the AI
> part is rigged only to run in an @home style manner, which would make
> parts of the AI run while others did not, basically at random - and
> fixing it would slow it to the point of unusability), Kazaa users
> simply switch to something that doesn't tie up their box. Potential
Have you researched the issue for a moment before commenting? A typical
computer idles 98..99% of the time. A task running at low priority makes
use of those idle cycles. Nice tasks are invisible on OSses with decent
multitasking (NT is not one of them, but then Folding@HOME doesn't even
run nice there). Further, you can measure CPU load dynamically and go to
sleep when high-priority tasks become visible. You could also go to sleep
whenever a user is active (keystrokes and mouse events take zero CPU to
detect), similiarly to a screenblanker (only minus the screenblanker).
Users typically have to sleep sometime, which is visible that there's been
a time of activity approximating the length of a working day, which then
stops. And if you've got a multi-CPU box, only one will handle the UI, so
you can hog the rest. And scooby-dooby-doo.
Same applies to network load.
> for hacking is one thing, which many people ignore; *actually doing it*
> is something else entirely. (For instance: few people complained about
> the possibility of spam in the pre-Cantor-&-Siegel days.)
You're wrong. The only way you could detect something is going on is from
the network activity on blinkenlights and somewhat higher power bill (a
computer might draw some 10% more power under full load).
This archive was generated by hypermail 2.1.5 : Sat Nov 02 2002 - 09:13:19 MST