From owner-freebsd-hackers Fri Sep 29 12:54:48 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA29491 for hackers-outgoing; Fri, 29 Sep 1995 12:54:48 -0700 Received: from netcom22.netcom.com (bakul@netcom22.netcom.com [192.100.81.136]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA29486 for ; Fri, 29 Sep 1995 12:54:47 -0700 Received: from localhost by netcom22.netcom.com (8.6.12/Netcom) id MAA05143; Fri, 29 Sep 1995 12:54:29 -0700 Message-Id: <199509291954.MAA05143@netcom22.netcom.com> To: "Jordan K. Hubbard" cc: hackers@freefall.freebsd.org Subject: Re: A moment in the life of ftp.cdrom.com In-reply-to: Your message of "Fri, 29 Sep 95 11:54:30 PDT." <8554.812400870@time.cdrom.com> Date: Fri, 29 Sep 95 12:54:26 -0700 From: Bakul Shah Sender: owner-hackers@FreeBSD.org Precedence: bulk > 18896 root 85 0 684K 584K run 0:33 4.20% 4.20% compress > 14212 root 86 0 568K 332K run 2:12 4.33% 4.16% gzip > 1449 root 85 0 568K 332K run 6:51 4.16% 4.16% gzip > 13231 root 85 0 568K 332K run 2:30 4.16% 4.16% gzip > 8302 root 85 0 568K 328K run 2:21 3.74% 3.74% gzip > 11383 root 2 0 98M 12M sleep 15:04 3.09% 3.09% perl > 84 root 2 0 180K 136K sleep 318:39 2.71% 2.71% syslogd Caching compressed/gzipped files for a while may be a win. It'd be interesting to know where majority of that 98M is going. Memory leak? profligate memory use? or just a huge amount of data? It is probably spending half its time paging. 318:39 for syslogd? Hmm... It'd also be interesting to know who waits for how long and why. Performance tuning can be an interesting and rewarding exercise! -- bakul