public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Asdo <asdo@shiftmail.org>
To: xfs@oss.sgi.com
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Disappointing performance of copy (MD raid + XFS)
Date: Thu, 10 Dec 2009 02:16:35 +0100	[thread overview]
Message-ID: <4B204BF3.1000600@shiftmail.org> (raw)
In-Reply-To: <4B204783.7040109@shiftmail.org>

Asdo wrote:
> Asdo wrote:
>> and I think I have seen around 10MB/sec when they are of 500KB (this 
>> transfer at 10MB/sec was in parallel with another faster one however). 
> Yes I definitely confirm: right now I have just 1 rsync copy running, 
> it's in a zone where files are around 500KB on average, and it's going 
> at 9 MB/sec.
> Stack traces of the writer process conform to what I have posted in my 
> previous email, even now that the writer is the only process using the 
> destination array.
Excuse me, I am going nuts...
In this case of 9MB/sec for 500KB files, stack traces on the writer are 
indeed very similar to what I have posted, but the relative frequency of 
the two type of stack traces is different:
20%: waiting on the reader (this almost never happened when using 
multiple parallel rsyncs)
50%: xlog_state_get_iclog_space+0xed/0x2d0
30%: xfs_buf_lock+0x1e/0x60


The reader is waiting either on select (on the writer I guess) or on this:
  [<ffffffff810da74d>] sync_page+0x3d/0x50
  [<ffffffff810da769>] sync_page_killable+0x9/0x40
  [<ffffffff810da682>] __lock_page_killable+0x62/0x70
  [<ffffffff810db8be>] T.768+0x1ee/0x440            
  [<ffffffff810dbbc6>] generic_file_aio_read+0xb6/0x1d0
  [<ffffffffa031cd95>] xfs_read+0x115/0x2a0 [xfs]     
  [<ffffffffa031832b>] xfs_file_aio_read+0x5b/0x70 [xfs]
  [<ffffffff8111ec32>] do_sync_read+0xf2/0x130         
  [<ffffffff8111f215>] vfs_read+0xb5/0x1a0             
  [<ffffffff8111f81c>] sys_read+0x4c/0x80              
  [<ffffffff81012002>] system_call_fastpath+0x16/0x1b  
  [<ffffffffffffffff>] 0xffffffffffffffff              


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

  reply	other threads:[~2009-12-10  1:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10  0:39 Disappointing performance of copy (MD raid + XFS) Asdo
2009-12-10  0:57 ` Asdo
2009-12-10  1:16   ` Asdo [this message]
2009-12-10  4:16 ` Eric Sandeen
2009-12-11  1:41   ` Asdo
2009-12-11  3:20     ` Eric Sandeen
2009-12-11  3:26     ` Dave Chinner
     [not found]       ` <1260895872.7209.46.camel@localhost>
2009-12-15 16:53         ` Eric Sandeen
2009-12-10  7:28 ` Gabor Gombas
2009-12-10  9:44 ` Kristleifur Daðason

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=4B204BF3.1000600@shiftmail.org \
    --to=asdo@shiftmail.org \
    --cc=linux-raid@vger.kernel.org \
    --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