From owner-freebsd-questions@FreeBSD.ORG Fri Oct 8 18:57:27 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B7C616A4CE for ; Fri, 8 Oct 2004 18:57:27 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E817243D41 for ; Fri, 8 Oct 2004 18:57:26 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-246-51.ny325.east.verizon.net [68.160.246.51]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id i98IvKQw052712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Oct 2004 14:57:22 -0400 (EDT) Message-ID: <4166E308.2050306@mac.com> Date: Fri, 08 Oct 2004 14:57:12 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Moran References: <416595F3.1030601@etherealconsulting.com> <4165A1FF.5080906@mac.com> <200410072322.42534.howells@kde.org> <20041007231356.GB12508@alex.lan> <20041007170026.S60351@celebrian.forsythia.net> In-Reply-To: <20041007170026.S60351@celebrian.forsythia.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pi.codefab.com cc: freebsd-questions@freebsd.org Subject: Re: benchmarking a process X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2004 18:57:27 -0000 Andrew Moran wrote: > This isn't specific to freebsd I suppose.. but does anyone know any good > programs to measure how long a process took, how much memory it > requested, and how much network traffic it send/received? See "man getrusage" and "man gprof" for the first two questions. Measuring how much network traffic something sends is more complicated: counters kept at the application-level see different numbers than what actually goes out on the wire, due to collisions, lost packets, etc. Using a network sniffer or IPFW rule to monitor the traffic is likely to give a more meaningful result, depending on what you want to do. -- -Chuck