public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: David Chinner <dgc@sgi.com>
Cc: Andi Kleen <ak@suse.de>, xfs@oss.sgi.com
Subject: Re: XFS thread inflation in 2.6.23rc
Date: Fri, 10 Aug 2007 14:34:10 -0500	[thread overview]
Message-ID: <46BCBDB2.6070703@sandeen.net> (raw)
In-Reply-To: <20070809110322.GA12413810@sgi.com>

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.

See for example:
http://article.gmane.org/gmane.linux.redhat.fedora.testers/50480

quoting:

"One of the biggest power problems is apps that wake up the CPU
unnecessarily. With the tickless kernel for x86 (and soon x86_64),
every time this happens it's a chance for power savings lost.

HOW YOU CAN HELP
----------------

We'd like to get as many reports of misbehaving apps as possible.

1) Install the 'powertop' package

2) Run it in a terminal window on a reasonably idle system with your
   normal combination of apps. (If you run it when you're actively
   compiling a kernel, watching a movie, or doing other CPU-intensive
   things, the results aren't as useful.)

3) Note the results..."

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

...

looks like having this running (note: i'm not using filestreams on this
mounted filesystem) may be impacting the power usage of the CPU?  Or
maybe SGI doesn' care about that, if the goal is 100% utilization of
these machines on altixes etc... but still - something to consider I think.

Thanks,
-Eric

  reply	other threads:[~2007-08-10 19:34 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 [this message]
2007-08-10 23:49             ` David Chinner
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=46BCBDB2.6070703@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=ak@suse.de \
    --cc=dgc@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