From owner-freebsd-current@FreeBSD.ORG Fri Jun 6 16:27:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10D8837B401 for ; Fri, 6 Jun 2003 16:27:17 -0700 (PDT) Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.64.14.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FF5F43FA3 for ; Fri, 6 Jun 2003 16:27:16 -0700 (PDT) (envelope-from jstockdale@stanford.edu) Received: (from root@localhost) by smtp1.Stanford.EDU (8.12.9/8.12.9) id h56NR83C025503 for freebsd-current@freebsd.org; Fri, 6 Jun 2003 16:27:08 -0700 (PDT) Received: from stanford.edu (quenya.Stanford.EDU [128.12.44.61]) by smtp1.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h56NQuch025348 for ; Fri, 6 Jun 2003 16:26:57 -0700 (PDT) Message-ID: <3EE1233F.1030808@stanford.edu> Date: Fri, 06 Jun 2003 16:26:55 -0700 From: John Stockdale User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030530 Thunderbird/0.1a X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20030528071326.GA29506@gvr.gvr.org> <32216.1054109479@critter.freebsd.dk> <20030528104027.GD6015@survey.codeburst.net> <20030601145626.Q99813@12-234-22-23.pyvrag.nggov.pbz> In-Reply-To: <20030601145626.Q99813@12-234-22-23.pyvrag.nggov.pbz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: gbde Performance - 35Mb/s vs 5.2 MB/s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 23:27:17 -0000 Hey Everyone, I've been MIA with regards to the current list lately, but was checking the backlog for gbde stuff and came across this thread. Anyway, I've been running gbde (thanks to Poul for helping me out along the way) on a SMP (2x2.0ghz Xeon) box with a 3ware RAID 5 (8 drive ATA-133 array) with caching enabled (8MB per drive). Its been up nicely for about a month. Running bonnie (1024MB test file) to benchmark performance (as recommended by 3ware tech) gives the following results: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 1024 4845 13.7 4781 2.9 3796 2.3 12873 35.3 16287 5.9 648.3 4.3 Additionally, during the write portion of the test g_bde @ nice=-20 takes up 20-30% of one processor ( taken from top -S ) while bonnie takes 2-8%. I'm not quite sure what is limiting the cpu usage of gbde, but 30% is about as high as I ever can get it to stress any one processor during write. Still though not bad performance. During read I managed to get up to 75% processor usage on gbde and up to 45% on bonnie ( not at the same time, for some reason the two processes won't thread onto different processers ;) -John