public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: "Peter J . Braam" <braam@clusterfilesystem.com>
Cc: Andrew Morton <akpm@zip.com.au>, Steve Lord <lord@sgi.com>,
	Ben Israel <ben@genesis-one.com>,
	linux-kernel@vger.kernel.org
Subject: Re: File System Performance
Date: Tue, 13 Nov 2001 13:46:53 -0700	[thread overview]
Message-ID: <20011113134653.O1778@lynx.no> (raw)
In-Reply-To: <3BF02702.34C21E75@zip.com.au>, <00b201c16b81$9d7aaba0$5101a8c0@pbc.adelphia.net> <3BEFF9D1.3CC01AB3@zip.com.au> <00da01c16ba2$96aeda00$5101a8c0@pbc.adelphia.net> <3BF02702.34C21E75@zip.com.au> <1005595583.13307.5.camel@jen.americas.sgi.com> <3BF03402.87D44589@zip.com.au> <20011112171705.Z1778@lynx.no> <20011112174005.N4281@lustre.dyn.ca.clusterfilesystem.com>
In-Reply-To: <20011112174005.N4281@lustre.dyn.ca.clusterfilesystem.com>; from braam@clusterfilesystem.com on Mon, Nov 12, 2001 at 05:40:05PM -0700

On Nov 12, 2001  17:40 -0700, Peter J . Braam wrote:
> The KML in fact doesn't record the writes.  I don't have a large KML,
> but it is easy to set one up.  Let me know if you need a hand.

We don't actually need to have the data contents, just the file sizes,
which I think the CLOSE records have, don't they?  The one thing I'm
unsure of is whether you zero the KML as it is "used", or does it keep
the data from past transactions?  At one time we were thinking about
using "punch" to reduce the actual file size, but I doubt that is in
place yet.

This is purely to measure the effects of repeated file creation, deletion,
updates in a real setting over a very long period (e.g. many months/years),
which is why setting something like this up today won't get us anywhere
(any large amount of activity would just be synthetic).

Do you think Ron Minnich or the folks at Tacitus would have a KML which
has been generated on a large server over a long period of time and not
erased?

> On Mon, Nov 12, 2001 at 05:17:05PM -0700, Andreas Dilger wrote:
> > On Nov 12, 2001  12:41 -0800, Andrew Morton wrote:
> > > BTW, I've been trying to hunt down a suitable file system aging tool.
> > > We're not very happy with Keith Smith's workload because the directory
> > > infomation was lost (he was purely studying FFS algorithmic differences
> > > - the load isn't 100% suitable for testing other filesystems / algorithms).
> > >   Constantin Loizides' tools are proving to be rather complex to compile,
> > >   drive and understand.
> > 
> > What _may_ be a very interesting tool for doing "real-world" I/O generation
> > is to use the InterMezzo KML (kernel modification log), which is basically
> > a 100% record of every filesystem operation done (e.g. create, write,
> > delete, mkdir, rmdir, etc).
> > 
> > Peter, do you have any very large KML files which would simulate the usage
> > of a filesystem over a long period of time, or would Tacitus have something
> > like that?

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-11-13 20:48 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 13:54 File System Performance Ben Israel
2001-11-12 16:33 ` Andrew Morton
2001-11-12 17:50   ` Ben Israel
2001-11-12 19:46     ` Andrew Morton
2001-11-12 19:59       ` Richard Gooch
2001-11-12 23:07         ` Mike Fedyk
2001-11-13  0:04           ` Richard Gooch
2001-11-13  0:08             ` Mike Fedyk
2001-11-13  0:26               ` Richard Gooch
2001-11-13  0:47                 ` Mike Castle
2001-11-13  1:28                 ` Mike Fedyk
2001-11-13  6:34                   ` Richard Gooch
2001-11-13 20:56                     ` Andreas Dilger
2001-11-13  7:45             ` Andreas Dilger
2001-11-12 20:06       ` Steve Lord
2001-11-12 20:41         ` Andrew Morton
2001-11-12 21:27           ` Steve Lord
2001-11-12 21:43             ` Andrew Morton
2001-11-12 21:45               ` Steve Lord
2001-11-12 21:48               ` Linus Torvalds
2001-11-12 22:11                 ` Lionel Bouton
2001-11-12 19:41                   ` Gérard Roudier
2001-11-12 22:14                   ` Linus Torvalds
2001-11-12 22:30                     ` Ragnar Kjørstad
2001-11-12 22:36                     ` Andrew Morton
2001-11-12 23:04                       ` Mike Castle
2001-11-13  9:56                         ` Peter Wächtler
2001-11-13  9:41                     ` Henning P. Schmiedehausen
2001-11-12 22:16                 ` Andrew Morton
2001-11-12 22:26                   ` Steve Lord
2001-11-12 22:32                   ` Lionel Bouton
2001-11-12 22:45                     ` Alan Cox
2001-11-12 22:39                   ` Alan Cox
2001-11-12 22:39                     ` Xavier Bestel
2001-11-12 22:46                   ` Mike Castle
2001-11-12 21:53             ` Lionel Bouton
2001-11-13  0:17           ` Andreas Dilger
2001-11-13  0:40             ` Peter J . Braam
2001-11-13 20:46               ` Andreas Dilger [this message]
2001-11-16 22:07                 ` Peter J . Braam
2001-11-16 23:14                   ` Mike Fedyk
2001-11-12 16:40 ` Ben Israel
2001-11-12 17:29 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2001-11-12 22:36 Grant Erickson

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=20011113134653.O1778@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=akpm@zip.com.au \
    --cc=ben@genesis-one.com \
    --cc=braam@clusterfilesystem.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.com \
    /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