From owner-freebsd-geom@FreeBSD.ORG Wed Jan 10 04:12:14 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BD1316A40F; Wed, 10 Jan 2007 04:12:14 +0000 (UTC) (envelope-from unixtools@hotmail.com) Received: from bay0-omc2-s23.bay0.hotmail.com (bay0-omc2-s23.bay0.hotmail.com [65.54.246.159]) by mx1.freebsd.org (Postfix) with ESMTP id 14D7213C45A; Wed, 10 Jan 2007 04:12:14 +0000 (UTC) (envelope-from unixtools@hotmail.com) Received: from hotmail.com ([65.54.161.81]) by bay0-omc2-s23.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Tue, 9 Jan 2007 20:00:14 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 9 Jan 2007 20:00:13 -0800 Message-ID: Received: from 203.199.109.165 by BAY106-DAV9.phx.gbl with DAV; Wed, 10 Jan 2007 04:00:09 +0000 X-Originating-IP: [203.199.109.165] X-Originating-Email: [unixtools@hotmail.com] X-Sender: unixtools@hotmail.com From: To: "Fluffles" , , References: <45A38D38.3020407@fluffles.net> Date: Wed, 10 Jan 2007 09:59:51 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-OriginalArrivalTime: 10 Jan 2007 04:00:13.0749 (UTC) FILETIME=[D4AB4E50:01C7346B] Cc: Subject: Re: Capturing I/O traces 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: Wed, 10 Jan 2007 04:12:14 -0000 Hi, To capture appication IO, the best option on freebsd is ktrace. I have no idea how to trace all the io calls triggered by the kernel. Sunil Sunder Raj http://daemon.in ----- Original Message ----- From: "Fluffles" To: ; Sent: Tuesday, January 09, 2007 6:10 PM Subject: Capturing I/O traces > Hello list, > > I was wondering if any method is known to "capture" I/O traces. My goal > is to be able to simulate I/O access patterns generated by applications > such as MySQL or KDE and compare these to other storage systems. This > way i can provide more realistic benchmarks (not synthetic) without > actually running the application i'm testing. For example, I would like > to capture the I/O that occurs when KDE boots, and then be able to > reproduce this I/O access on say a gmirror and graid3. This way i can > gather more realistic benchmark results. On Windows several commercial > applications exist that 'simulate' access patterns used by applications, > i was wondering if any BSD/Linux equivalent exists. > > One thought that comes to mind is the gnop geom class; with verbose mode > this provides a text log of all the I/O accesses. But it does not > provide the exact time/concurrency etc, only the offset, length, I/O > action (read/write) and the serial order of those requests. And even > with this information it's not easy to reproduce them; i would have to > write an application that reads this log and then be able to reproduce > it. I was hoping to find a more elegant solution. If you guys know of > any, please share it with me. :) > > Regards, > > Veronica > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >