From owner-freebsd-questions@FreeBSD.ORG Tue Feb 24 17:55:16 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64907106564A for ; Tue, 24 Feb 2009 17:55:16 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 37A178FC13 for ; Tue, 24 Feb 2009 17:55:16 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.lan.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 9F517AFC1FF; Tue, 24 Feb 2009 08:55:12 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Tue, 24 Feb 2009 08:55:11 -0900 User-Agent: KMail/1.9.10 References: <49A41C56.3060000@itlegion.ru> In-Reply-To: <49A41C56.3060000@itlegion.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902240855.12279.fbsd.questions@rachie.is-a-geek.net> Cc: Artem Kuchin Subject: Re: Please, recommend CPU and RAM burn test 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: Tue, 24 Feb 2009 17:55:16 -0000 On Tuesday 24 February 2009 07:12:06 Artem Kuchin wrote: > Hello! > > I need to really heavily test a box with 8 cores and 16GB FBDIM RAM. > > Is there a suitable port for such task? > > I'd like to point out that i don't want to measure perfomance. I need to > really really > heavily load the server up to it's maximum. sysutils/stress, in your case: stress --vm 32 --vm-bytes 512M --cpu 8 will put it into swap, while cpu's are overloaded. Add --hdd 4 to write 4 1GB files in parallel, should be a nice test ;) Test can be run till interrupt or use -t 300 to timeout after 5 minutes. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.