From owner-freebsd-questions@FreeBSD.ORG Mon Jan 2 18:07:05 2006 Return-Path: X-Original-To: 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 8F1B416A41F for ; Mon, 2 Jan 2006 18:07:05 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [65.75.192.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84CF943D5E for ; Mon, 2 Jan 2006 18:07:04 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.13.4/8.13.4) with ESMTP id k02I72cm081165 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Mon, 2 Jan 2006 10:07:02 -0800 (PST) (envelope-from james@umpquanet.com) Received: (from james@localhost) by ns.museum.rain.com (8.13.4/8.13.4/Submit) id k02I6qeb081164; Mon, 2 Jan 2006 10:06:52 -0800 (PST) (envelope-from james) Date: Mon, 2 Jan 2006 10:06:52 -0800 From: James Long To: freebsd-questions@freebsd.org Message-ID: <20060102180652.GA81087@ns.museum.rain.com> References: <20060102105418.EA25316A433@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060102105418.EA25316A433@hub.freebsd.org> User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-101.4 required=5.0 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ns.museum.rain.com Cc: Gary Kline Subject: Re: STressing a new server... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 18:07:05 -0000 A buildworld is indeed an excellent test of memory, CPU, drives and cabling. The memory tester is sysutils/memtest. It's not a very scientific test, but one thing I do is a make -j8 buildworld whilst I do a large tar operation, optionally with compression. Just anecdotally it appears that tar likes to use lots of memory. I usually do some sort of file system move, ala: tar jcf - original | tar xpvf - -C copy Make sure you have enough disk space to burn. This has caught dodgy memory on servers in the past. Jim