linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: linux-ext4@vger.kernel.org
Subject: Re: mkdir performance.
Date: Fri, 18 Mar 2011 11:49:11 -0500	[thread overview]
Message-ID: <4D838D07.2070607@redhat.com> (raw)
In-Reply-To: <20110318085742.GA20480@bitwizard.nl>

On 3/18/11 3:57 AM, Rogier Wolff wrote:
> 
> Hi Guys, 
> 
> I'm seeing more and more mkdir performance problems.
> 
> On the big partition where I most often NEED the performance an
> strace -tttT mkdir asdlkfj results in: 
> 
> 1300437461.968657 mkdir("asdklfj", 0777) = 0 <0.065133>
> 
> On my homedir (older machine) the same mkdir is a lot faster:
> 
> 1300437428.294018 mkdir("asdklfj", 0777) = 0 <0.003813>
> 
> Only 3 milliseconds. Ten times faster! That would be great!

Did you have a chance to play with that patch I flung onto
the list?  :)

-Eric

> On my local workstation I get: 
> 
> 1300437803.200227 mkdir("askldjf", 0777) = 0 <0.000092>
> 
> 92 microseconds. even 30 times faster than that!
> 
> That 65 milliseconds. For just one it's not that bad. Not even
> noticable. In my current (data-recovery) project I have (/ my client
> has) about 30000 directories. This means that to do the recovery I
> wait an additional 32 minutes just for all the mkdirs.
> 
> But I'm not waiting just once for "all the mkdirs". During the course
> of a datarecovery I reconstruct the tree many times over, making
> backups of the current state over and over again. In this project I've
> been waiting that half hour over ten times, so it's cost me over 5
> hours in productivity.
> 
> IIRC, a fix was available, right?
> 
> To "fix" this, all I need to do is to switch to the most recent
> kernel, right? Or was the fix not yet integrated with Linus?
> 
> 	Roger. 
> 


      reply	other threads:[~2011-03-18 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18  8:57 mkdir performance Rogier Wolff
2011-03-18 16:49 ` Eric Sandeen [this message]

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=4D838D07.2070607@redhat.com \
    --to=sandeen@redhat.com \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=linux-ext4@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).