From: Mark Goodwin <goodwinos@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: add "quick" group
Date: Mon, 16 Feb 2009 11:53:31 +1100 [thread overview]
Message-ID: <4998B90B.1000605@gmail.com> (raw)
In-Reply-To: <49986233.6050600@sandeen.net>
Eric Sandeen wrote:
> Christoph Hellwig wrote:
>>> Most are probably close enough, but 178 looks nasty - seems to be
>>> xfs_repair that's taking so long. These are running on 100G partitions,
>>> though :)
>> 178 only takes 16 seconds for me, running on 10G partitions.
>
> interesting that a 10x size growth makes a 22x time growth.
>
It would be interesting to see if Barry's "memory optimization"
patches (that I posted) improve the linearity here.
Cheers
-- Mark
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-16 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 16:42 [PATCH] xfstests: add "quick" group Christoph Hellwig
2009-02-14 19:58 ` Eric Sandeen
2009-02-15 18:21 ` Christoph Hellwig
2009-02-15 18:42 ` Eric Sandeen
2009-02-16 0:53 ` Mark Goodwin [this message]
2009-02-16 1:47 ` Eric Sandeen
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=4998B90B.1000605@gmail.com \
--to=goodwinos@gmail.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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