From owner-freebsd-geom@FreeBSD.ORG Fri Jan 30 17:07:26 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 651F01065674 for ; Fri, 30 Jan 2009 17:07:26 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id 39E208FC12 for ; Fri, 30 Jan 2009 17:07:26 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.storspeed.com (mail.storspeed.com [209.163.168.123]) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id n0UGEI4A003831 for ; Fri, 30 Jan 2009 10:14:19 -0600 (CST) (envelope-from anderson@freebsd.org) Message-Id: <6612C205-C346-4493-9DA4-3B5A73E9A4F7@freebsd.org> From: Eric Anderson To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 30 Jan 2009 10:40:46 -0600 X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: ClamAV 0.94.1/8923/Fri Jan 30 04:49:06 2009 on ns.trinitel.com X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ns.trinitel.com Subject: Performance numbers? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 17:07:26 -0000 Hi GEOMers! Does anyone have any benchmarks or numbers relating to GEOM performance? I tried doing some on my own, but I didn't get very satisfactory results, so I'm curious what others have seen or used. My hardware is a Core 2 Quad, with 4GB of ram. First, I made an mdconfig'ed malloc backed 'disk' of 1.5GB. Then, I tried running such tools as rawio, and diskinfo. rawio fails with input/output errors, and diskinfo wants a larger device to give the full stats. I ended up using purely dd since that worked. Interestingly enough, dd'ing to the malloc device results in about 1000 operations per second, regardless of a blocksize of 512bytes or 1MB. Do you all expect this 1000 operations per second to be limited by the mdconfig'ed device, GEOM, both, all, none, ?? I'm looking for pointers here mostly. I really would like to see how many operations (512byte really) the GEOM infrastructure can do on a particular piece of hardware, so if there is a simpler way to do this test, give me a hint. :) Thanks! Eric