From owner-freebsd-chat Mon Apr 19 7: 5:56 1999 Delivered-To: freebsd-chat@freebsd.org Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (Postfix) with ESMTP id 5E572150A4 for ; Mon, 19 Apr 1999 07:05:44 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id KAA02752; Mon, 19 Apr 1999 10:04:23 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma002743; Mon, 19 Apr 99 14:04:05 GMT Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id KAA23796; Mon, 19 Apr 1999 10:02:45 -0400 (EDT) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.3/8.8.8) id KAA01526; Mon, 19 Apr 1999 10:02:45 -0400 (EDT) Date: Mon, 19 Apr 1999 10:02:45 -0400 (EDT) Message-Id: <199904191402.KAA01526@jabberwock.rstcorp.com> From: "Viren R. Shah" To: John Baldwin Cc: Donald Wilde , freebsd-chat@freebsd.org, Dave Rossow , jgrosch@mooseriver.com Subject: Re: SETI on FreeBSD In-Reply-To: References: <3719DFF0.DD15987@thuntek.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "John" == John Baldwin writes: John> I asssume that if you set it to run at an idle priority ( man John> idprio ) it has virtually no impact on the system. OTOH, if John> you run it at a niceness of 20, it can still have some impact John> because it always runs at least a little. With idprio it seems John> to only run when the system is truly idle. Granted, my John> experience is with the RC5 client, but the concepts should be John> the same for seti@home as well. 74 processes: 3 running, 70 sleeping, 1 zombie CPU states: % user, % nice, % system, % interrupt, % idle Mem: 73M Active, 28M Inact, 14M Wired, 7808K Cache, 8028K Buf, 632K Free Swap: 256M Total, 256M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 1001 vshah 105 1 14776K 14380K RUN 13:02 58.15% 58.15% setiatho 285 nobody 105 20 904K 380K RUN 22:36 33.74% 33.74% rc5des 722 vshah 2 0 13884K 12940K select 1:10 2.00% 2.00% xemacs-1 583 vshah 2 0 23232K 21236K select 0:45 1.27% 1.27% XF86_SVG 611 vshah 2 0 1924K 1280K select 0:01 0.05% 0.05% fvwm2 735 vshah 2 0 23644K 18848K select 0:09 0.00% 0.00% communic 620 vshah 10 0 2444K 1736K nanslp 0:05 0.00% 0.00% xearth I have both rc5 and seti running on my work machine. It does slow down big compiles, but just give the compile a higher priority. rc5 is running nice'd, but seti is running at normal priority. It doesn't affect "normal" interactive response. If I run x11amp on the, the sound output is as good as ever. This is on a PIi 400 w/ 128M RAM. Viren -- Viren R. Shah {viren @ rstcorp . com} Names : Vanadium(23) Iodine(53) RhEnium(75) Nitrogen(7) Density(g/mL): 5.8 4.92 21 0.0001251 Average Density: 7.93003 g/mL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message