linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-delalloc - threaded?
Date: Tue, 22 Nov 2011 09:47:44 -0500	[thread overview]
Message-ID: <20111122144744.GI28259@shiny> (raw)
In-Reply-To: <slrnjcncff.cqt.stephane.chazelas@spam.is.invalid>

On Tue, Nov 22, 2011 at 02:30:07PM +0000, Stephane CHAZELAS wrote:
> 2011-09-6, 11:21(-05), Andrew Carlson:
> > I was doing some testing with writing out data to a BTFS filesystem
> > with the compress-force option.  With 1 program running, I saw
> > btfs-delalloc taking about 1 CPU worth of time, much as could be
> > expected.  I then started up 2 programs at the same time, writing data
> > to the BTRFS volume.  btrfs-delalloc still only used 1 CPU worth of
> > time.  Is btrfs-delalloc threaded, to where it can use more than 1 CPU
> > worth of time?  Is there a threshold where it would start using more
> > CPU?
> [...]
> 
> Hiya,
> 
> I observe the same here. The bottleneck when writing data
> sequencially seems to be that btrfs-delalloc using 100% of the
> time of one CPU.

The compression is spread out to multiple CPUs.  Using zlib on my 4 cpu
box, I get 4 delalloc threads working on two concurrent dds.

The thread hand off is based on the amount of work queued up to each
thread, and you're probably just below the threshold where it kicks off
another one.  Are you using lzo or zlib? 

What is the workload you're using?  We can make the compression code
more aggressive at fanning out.

-chris

  reply	other threads:[~2011-11-22 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 16:21 btrfs-delalloc - threaded? Andrew Carlson
2011-11-22 14:30 ` Stephane CHAZELAS
2011-11-22 14:47   ` Chris Mason [this message]
2011-11-22 17:01     ` Stephane CHAZELAS

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=20111122144744.GI28259@shiny \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).