public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: ext3 metadata performace
Date: Thu, 11 May 2006 18:46:07 +0000 (UTC)	[thread overview]
Message-ID: <e400pf$ens$1@news.cistron.nl> (raw)
In-Reply-To: 44635BA8.9060002@argo.co.il

In article <44635BA8.9060002@argo.co.il>,
Avi Kivity  <avi@argo.co.il> wrote:
>Dieter Stuken wrote:
>> after I switched from from ext2 to ext3 i observed some severe 
>> performance degradation. Most discussion about this topic deals
>> with tuning of data-io performance. My problem however is related to 
>> metadata updates. When cloning (cp -al) or deleting directory trees I 
>> find, that about 7200 files are created/deleted per minute. Seems
>> this is related to some ex3 strategy, to wait for each metadata to be
>> written to disk. Interestingly this occurs with my new hw-raid
>> controller (3ware 9500S), which even has an battery buffered disk cache.
>> Thus there is no need for synchronous IO anyway. If I disable the
>> disk cache on my plain SATA disk using ext3, I also get this behavior.
>>
>Try increasing the journal size (mkfs -t ext3 -J size=20000) and see if 
>that improves things.

Also, with 3ware, look in /sys/block/sd* and set queue_depth to
254/(nr_arrays), and nr_requests to at least 2*queue_depth. Also
try another I/O scheduler (deadline instead of as).

Mike.


  reply	other threads:[~2006-05-11 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 14:11 ext3 metadata performace Dieter Stüken
2006-05-11 15:43 ` Avi Kivity
2006-05-11 18:46   ` Miquel van Smoorenburg [this message]
2006-05-12  0:36 ` Hua Zhong
2006-05-12  6:35 ` Helge Hafting
2006-05-12 10:11   ` Dieter Stüken
     [not found] <6bkbC-4V9-27@gated-at.bofh.it>
2006-05-12  0:12 ` Robert Hancock

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='e400pf$ens$1@news.cistron.nl' \
    --to=miquels@cistron.nl \
    --cc=linux-kernel@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