From owner-freebsd-questions@FreeBSD.ORG  Fri Sep  5 10:48:57 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 21DAC16A4BF
	for <freebsd-questions@freebsd.org>;
	Fri,  5 Sep 2003 10:48:57 -0700 (PDT)
Received: from main.gmane.org (main.gmane.org [80.91.224.249])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EF07743FF9
	for <freebsd-questions@freebsd.org>;
	Fri,  5 Sep 2003 10:48:55 -0700 (PDT)
	(envelope-from freebsd-questions@m.gmane.org)
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 19vKi3-0004Ii-00
	for <freebsd-questions@freebsd.org>; Fri, 05 Sep 2003 19:49:23 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-questions@freebsd.org
Received: from sea.gmane.org ([80.91.224.252])
	by main.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 19vKi2-0004Ia-00	for <gmane-os-freebsd-questions@m.gmane.org>;
	Fri, 05 Sep 2003 19:49:22 +0200
Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian))
	id 19vKha-0001RW-00	for <gmane-os-freebsd-questions@m.gmane.org>;
	Fri, 05 Sep 2003 19:48:54 +0200
From: Jesse Guardiani <jesse@wingnet.net>
Date: Fri, 05 Sep 2003 13:48:53 -0400
Organization: WingNET
Lines: 40
Message-ID: <bjaia5$5da$1@sea.gmane.org>
References: <bj5rdn$3r5$5@sea.gmane.org> <44fzjb72wk.fsf@be-well.ilk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet@sea.gmane.org
User-Agent: KNode/0.7.2
X-Mail-Copies-To: never
Sender: news <news@sea.gmane.org>
Subject: Re: process memory peak recording
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: jesse@wingnet.net
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2003 17:48:57 -0000

Lowell Gilbert wrote:

> Jesse Guardiani <jesse@wingnet.net> writes:
> 
>> During a recent programming/installation
>> project, I found myself wanting to know
>> the peak memory usage of a given command/process.
>> 
>> Is there any way to gather this information
>> without recompiling an application with a
>> sleep or wait statement at the (assumed)
>> point of peak memory usage and then looking
>> at the process with 'ps'?
> 
> Running under a debugger is one typical way of doing this.
> For strictly malloc(3)'d memory, a memory profiler will be an easier
> option.  If I remember correctly, there is a choice of them in the
> ports system.

These are generally things you have to compile into your
applications, right? I'm specifically dealing with Perl
and Python scripts that I did not write.

However, I do some C programming from time to time, and
learning how to use a memory profiler/leak detector is
extremely appealing to me.

Which is your favorite?
Which works the best?


Thanks!

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net