From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] [XFSQA] Reduce the number of processes forked
Date: Mon, 16 Mar 2009 02:23:13 -0400 [thread overview]
Message-ID: <20090316062313.GA30641@infradead.org> (raw)
In-Reply-To: <1237114181-18431-2-git-send-email-david@fromorbit.com>
On Sun, Mar 15, 2009 at 09:49:39PM +1100, Dave Chinner wrote:
> One of the big cpu time consumers when running xfsqa on UML
> is forking of new processes. when looping lots of times,
> using 'expr' to calculate the loop counter increment means
> we fork at least once every loop. using shell builtins means
> that we don't fork and many tests run substantially faster.
>
> Some tests are even runnable with this modification. e.g. 110
> went from taking 4500s to run down to 9s with the loop iterators
> changed to avoid forking.
Looks good.
Care to see if any tests should be added to the quick group after this?
The above 110 sounds like a candidate for that.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-16 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 10:49 [PATCH 0/3] [XFSQA] Optimisations and ENOSPC tests Dave Chinner
2009-03-15 10:49 ` [PATCH 1/3] [XFSQA] Reduce the number of processes forked Dave Chinner
2009-03-16 6:23 ` Christoph Hellwig [this message]
2009-03-15 10:49 ` [PATCH 2/3] [XFSQA] Add simple delayed allocation ENOSPC test Dave Chinner
2009-03-16 6:23 ` Christoph Hellwig
2009-03-15 10:49 ` [PATCH 3/3] [XFSQA] Test writing to ENOSPC Dave Chinner
2009-03-16 6:27 ` Christoph Hellwig
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=20090316062313.GA30641@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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