public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: xfs@oss.sgi.com
Subject: slow xfs writes on loopback mounted xfs with dd + seek
Date: Tue, 11 Sep 2012 10:48:24 +0100	[thread overview]
Message-ID: <504F08E8.6020500@canonical.com> (raw)

Hi,

I've seeing really slow I/O writes on xfs when doing a dd with a seek 
offset to a file on an xfs file system which is loop mounted.

Reproduced on Linux 3.6.0-rc5 and 3.4

How to reproduce:

dd if=/dev/zero of=xfs.img bs=1M count=1024
mkfs.xfs -f xfs.img
sudo mount -o loop -t xfs xfs.img /mnt/test

First create a large file, write performance is excellent:

sudo dd if=/dev/zero of=/mnt/test/big bs=1M count=500
500+0 records in
500+0 records out
524288000 bytes (524 MB) copied, 1.69451 s, 309 MB/s

..next seek and write some more blocks, write performance is poor:

sudo dd if=/dev/zero of=/mnt/test/big obs=4K count=8192 seek=131072
8192+0 records in
1024+0 records out
4194304 bytes (4.2 MB) copied, 47.0644 s, 89.1 kB/s

Using blktrace and seektracer I've captured the I/O on the block device 
containing the xfs.img and I'm seeing ~55-70 seeks per second during the 
slow writes, which seems excessive.

I can reproduce this on hardware with 1, 4 or 8 CPUs.

I've testing this with other file systems I and don't see this issue, so 
it looks like an xfs + loop mounted issue.

Is this a known performance "feature"?

Colin

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2012-09-11  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11  9:48 Colin Ian King [this message]
2012-09-11 14:52 ` slow xfs writes on loopback mounted xfs with dd + seek Brian Foster
2012-09-11 20:50   ` Dave Chinner
2012-09-11 21:00     ` Colin Ian King

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=504F08E8.6020500@canonical.com \
    --to=colin.king@canonical.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