From owner-freebsd-chat Tue May 25 13: 2:18 1999 Delivered-To: freebsd-chat@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 02A0B15467 for ; Tue, 25 May 1999 13:02:15 -0700 (PDT) (envelope-from dpilgrim@uswest.net) Received: (qmail 24698 invoked by alias); 25 May 1999 20:02:12 -0000 Delivered-To: fixup-freebsd-chat@FreeBSD.ORG@fixme Received: (qmail 24645 invoked by uid 0); 25 May 1999 20:02:11 -0000 Received: from cdsl201.ptld.uswest.net (HELO uswest.net) (209.180.170.201) by ptldpop2.ptld.uswest.net with SMTP; 25 May 1999 20:02:11 -0000 Message-ID: <374B01BC.EBD00301@uswest.net> Date: Tue, 25 May 1999 13:02:04 -0700 From: Darren Pilgrim Organization: Neatly stacked heaps of digital chaos X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jamie Bowden Cc: "Mark S. Reichman" , "Viren R. Shah" , freebsd-chat@FreeBSD.ORG Subject: Re: SETI@home has teams now! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Crist J. Clark" wrote: > Darren Pilgrim wrote, >> idprio seems to have the effect I was aiming for--there's hardly any >> performance hit on the rest of the system/software--but the load is >> considerably higher than I had wanted for running it during business >> hours. I think idprio has a good chance of working. Thanks. > > Load does not tell you a whole lot about performance if processes are > prioritized appropriately. Who cares if setiathome is waiting for > processor cycles (adding to load), but not taking any time away from > processes in the "foreground" (not really impacting CPU usage of > work-related stuff)? Just because your load is always >1 when > setiathome is quietly waiting to take otherwise unused CPU cycles does > not mean other processes are losing any. > > That all said, I do kill setiathome during work hours (on work > machines). However, it has nothing to do with CPU usage. setiathome > eats about 14 MB of memory. On my 64 MB RAM PC here at work, that's > enough to cause some swapping, and _that_ can hit performance. Perhaps that's the problem then. Whatever the problem is, I began running into performance problems while s@h was running. > -- > Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message