From: David Chinner <dgc@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: David Chinner <dgc@sgi.com>, Andi Kleen <ak@suse.de>, xfs@oss.sgi.com
Subject: Re: XFS thread inflation in 2.6.23rc
Date: Sat, 11 Aug 2007 09:49:41 +1000 [thread overview]
Message-ID: <20070810234940.GO12413810@sgi.com> (raw)
In-Reply-To: <46BCBDB2.6070703@sandeen.net>
On Fri, Aug 10, 2007 at 02:34:10PM -0500, Eric Sandeen wrote:
> David Chinner wrote:
>
> > Andi, you are complaining to the wrong person about thread counts. I
> > live in the world of excessive parallelism and multithreaded I/O. I
> > regularly see 4-8p boxes running hundreds to thousands of I/O
> > threads on a single filesystem. These are the workloads XFS is
> > designed for and we optimise for. A single extra thread is noise....
>
>
> The other thing this is doing, though, is having an impact on power
> usage, I think. Fedora is trying to identify things which wake the CPU
> in an effort to reduce power usage if possible.
Sure, but an idle thread doesn't use any power, and the workqueue
is now only used when there are streams active.
> and here are the results w/ xfs mounted:
>
> < Detailed C-state information is only available on Mobile CPUs (laptops) >
> P-states (frequencies)
> 2.21 Ghz 0.0%
> 2.00 Ghz 0.0%
> 1.80 Ghz 100.0%
> Wakeups-from-idle per second : 31.7
> no ACPI power usage estimate available
> Top causes for wakeups:
> 37.0% ( 20.0) mount : xfs_mru_cache_create
http://oss.sgi.com/archives/xfs/2007-08/msg00009.html
"On-demand reaping of the MRU cache
Instead of running the mru cache reaper all the time based on a
timeout, we should only run it when the cache has active objects.
This allows CPUs to sleep when there is no activity rather than
be woken repeatedly just to check if there is anything to do."
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-08-10 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 10:40 XFS thread inflation in 2.6.23rc Andi Kleen
2007-08-08 12:13 ` David Chinner
2007-08-08 12:22 ` Andi Kleen
2007-08-08 13:14 ` David Chinner
2007-08-08 13:26 ` Andi Kleen
2007-08-09 11:03 ` David Chinner
2007-08-10 19:34 ` Eric Sandeen
2007-08-10 23:49 ` David Chinner [this message]
2007-08-11 1:21 ` 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=20070810234940.GO12413810@sgi.com \
--to=dgc@sgi.com \
--cc=ak@suse.de \
--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