linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Cc: "K.S. Bhaskar" <ks.bhaskar@fnis.com>
Subject: Enterprise workload testing for storage and filesystems
Date: Tue, 18 Nov 2008 07:47:42 +0900	[thread overview]
Message-ID: <1226962063.3403.13.camel@localhost.localdomain> (raw)

Hi all,

High on our list at the recent Linux Foundation end user summit was
obtaining a method of obtaining enterprise workloads (or simulators) we
can run in our own testing environments.  The main problem being that
the data sets used by the systems are usually secret or under regulatory
embargo and thus unobtainable.  However, several participants noted that
regulatory prohibitions also extended to their own in-house IT team,
thus they had had to develop simulators for the workloads which, since
they contained no customer data, might be more widely distributable.

Fidelity National Information Service were the first to try this.
They've kicked off a sourceforge site for their stress testing tool
(which is the same tool they use in their own qualification labs).  The
source for the tool is available here:

http://sourceforge.net/project/showfiles.php?group_id=11026&package_id=298597

And it comes with a fairly detailed readme explaining what it's trying
to simulate and why.  Hopefully this will give us all a much better
insight into both enterprise workloads and the way enterprise IT
departments conduct testing.

Let's see how our storage and filesystem tuning measures up to this.

James



             reply	other threads:[~2008-11-17 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 22:47 James Bottomley [this message]
2008-11-20 21:37 ` Enterprise workload testing for storage and filesystems Jeff Moyer
2008-11-21 15:59   ` K.S. Bhaskar
2008-11-21 16:18     ` Alan D. Brunelle
2008-11-21 16:42       ` K.S. Bhaskar
2008-11-21  4:42 ` Grant Grundler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1226962063.3403.13.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ks.bhaskar@fnis.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).