Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756513AbYKUQIB (ORCPT ); Fri, 21 Nov 2008 11:08:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752692AbYKUQHt (ORCPT ); Fri, 21 Nov 2008 11:07:49 -0500 Received: from mailoutltc.fnis.com ([199.200.24.190]:12064 "EHLO mailoutltc.fnis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752418AbYKUQHs (ORCPT ); Fri, 21 Nov 2008 11:07:48 -0500 X-Greylist: delayed 465 seconds by postgrey-1.27 at vger.kernel.org; Fri, 21 Nov 2008 11:07:48 EST Message-ID: <4926DAFC.5070006@fnis.com> Date: Fri, 21 Nov 2008 10:59:56 -0500 From: "K.S. Bhaskar" Reply-To: "K.S. Bhaskar" Organization: Fidelity National Information Services, Inc. User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Jeff Moyer CC: James Bottomley , linux-scsi , linux-kernel , linux-fsdevel@vger.kernel.org Subject: Re: Enterprise workload testing for storage and filesystems References: <1226962063.3403.13.camel@localhost.localdomain> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Nov 2008 15:59:57.0373 (UTC) FILETIME=[336D26D0:01C94BF2] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2173 Lines: 45 On 11/20/2008 04:37 PM, Jeff Moyer wrote: > James Bottomley writes: [KSB] <...snip...> > > Let's see how our storage and filesystem tuning measures up to this. > > This is indeed great news! The tool is very flexible, so I'd like to > know if we can get some sane configuration options to start testing. > I'm sure I can cook something up, but I'd like to be confident that what > I'm testing does indeed reflect a real-world workload. [KSB] Here are numbers for some tests that we ran recently: io_thrash -o 4 4 testdb 4000000 100000 12 8192 512 1000 90 90 10 512 io_thrash -o 4 4 testdb 4000000 100000 12 8192 512 10000 90 90 10 512 io_thrash -o 4 4 testdb 4000000 100000 12 8192 512 100000 90 90 10 512 io_thrash -o 4 4 testdb 4000000 100000 12 8192 512 200000 90 90 10 512 Note that these are relatively modest tests (4x32GB database files, all on one file system, 12 processes). To simulate bigger loads, allow the journal file sizes to grow to 4GB, use a configuration file to spread the database and journal files on different file systems, take the number of processes up into the hundreds and database sizes into the hundreds of GB. To keep test times reasonable, use the smallest numbers that give insightful results (after a point, making things bigger adds more time, but does not yield additional insights into system behavior, which is what we are trying to achieve). Regards -- Bhaskar _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/