public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] xfsqa 008 takes too long on UML...
Date: Tue, 13 May 2008 16:24:11 +1000	[thread overview]
Message-ID: <4829340B.4090708@sgi.com> (raw)
In-Reply-To: <20080512110134.GH155679365@sgi.com>

Sounds reasonable to me.
Might be nice to have the description as a comment in the test
so it is easy to see the thought behind the calculations
in the future.

--Tim

David Chinner wrote:
> With the recent change for reliability with 64k page size
> made to test 008,the file sizes got much larger. It appears
> that randholes actually reads the entire file, so this has
> slowed the test down by a factor of ten (all file sizes
> were increased by 10x). This means the test is now taking
> about 18 minutes to run on a UML session, and all the time
> is spent reading the files.
> 
> Instead, scale the file size based on the page size. We know
> how many holes we are trying to produce and the I/O size
> being used to produce them, so the size of the files can be
> finely tuned. Assuming a decent random distribution, if the
> number of blocks in the file is 4x the page size and the
> I/O size is page sized, this means that every I/O should
> generate a new hole and we'll only get a small amount of
> adjacent extents. This has passed over 10 times on ia64
> w/ 64k page and another 15 times on UML with 4k page.
> 
> UML runtime is down from ~1000s to 5s, ia64 runtime is down from
> ~30s to 7s.
> 
> Cheers,
> 
> Dave.

      reply	other threads:[~2008-05-13  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 11:01 [patch] xfsqa 008 takes too long on UML David Chinner
2008-05-13  6:24 ` Timothy Shimmin [this message]

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=4829340B.4090708@sgi.com \
    --to=tes@sgi.com \
    --cc=dgc@sgi.com \
    --cc=xfs-dev@sgi.com \
    --cc=xfs@oss.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