linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Landman <joe.landman@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Krzysztof Adamski <k@adamski.org>,
	Stefan Ring <stefanrin@gmail.com>,
	linux-raid <linux-raid@vger.kernel.org>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: very slow file deletion on an SSD
Date: Sun, 27 May 2012 13:14:41 -0400	[thread overview]
Message-ID: <4FC26101.2050003@gmail.com> (raw)
In-Reply-To: <4FC25126.7070002@sandeen.net>

On 05/27/2012 12:07 PM, Eric Sandeen wrote:
> On 5/27/12 9:59 AM, joe.landman@gmail.com wrote:
>> This is going to be a very fragmented file.  I am guessing that this
>> is the reason for the long duration delete.   I'll do some more
>> measurements before going to 3.4.x as per Eric's note.
>
> filefrag -v should also tell you how many fragments, and because it
> uses fiemap it probably won't run into the same problems.
>
> But it sounds like we can just assume very high fragmentation.
>

[root@siFlash test]# filefrag  1.r.48.0
1.r.48.0: 1364 extents found


> It's not addressing the exact issue, but why are the files so fragmented?
> Are they very hole-y or is it just an issue with how they are written?
> Perhaps preallocation would help you here?

Possibly.  We are testing the system using fio, and doing random reads 
and writes.  I'll see if we can do a preallocation scheme 
(before/during) for the files.

So to summarize, the delete performance will be (at least) in part a 
function of the fragmentation?  A directory full of massively fragmented 
files will take longer to delete than a directory of contiguous and 
larger extents?  And I did some experimentation using xfs_repair, and it 
seems to be the case there as well ... the higher level of 
fragmentation, the longer the repair seems to take.



>
> -Eric


  reply	other threads:[~2012-05-27 17:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 10:37 very slow file deletion on an SSD Joe Landman
2012-05-25 10:45 ` Bernd Schubert
2012-05-25 10:49   ` Joe Landman
2012-05-25 14:48     ` Roberto Spadim
2012-05-25 16:57 ` Ben Myers
2012-05-25 16:54   ` Joe Landman
2012-05-25 16:59   ` Christoph Hellwig
2012-05-26 16:00     ` David Brown
2012-05-26 19:56 ` Stan Hoeppner
2012-05-26 23:18 ` Dave Chinner
2012-05-26 23:25   ` Joe Landman
2012-05-27  0:07     ` Dave Chinner
2012-05-27  0:10       ` joe.landman
2012-05-27  1:49       ` Joe Landman
2012-05-27  2:40         ` Eric Sandeen
2012-05-27  2:43           ` Eric Sandeen
2012-05-27  7:34           ` Stefan Ring
2012-05-27 13:15             ` Krzysztof Adamski
2012-05-27 14:59               ` joe.landman
2012-05-27 16:07                 ` Eric Sandeen
2012-05-27 17:14                   ` Joe Landman [this message]
2012-05-27 17:17                   ` Joe Landman
2012-05-26 23:55   ` Joe Landman
2012-05-27  0:07     ` Jon Nelson

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=4FC26101.2050003@gmail.com \
    --to=joe.landman@gmail.com \
    --cc=k@adamski.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=stefanrin@gmail.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;
as well as URLs for NNTP newsgroup(s).