public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 behaviour when large number of files are created.
Date: Wed, 20 Oct 2004 13:23:29 +0400	[thread overview]
Message-ID: <41762E91.8060204@yandex.ru> (raw)
In-Reply-To: <1098211369.3872.14.camel@baythorne.infradead.org>

I also don't see any other reason why the mount is much slower if there 
are directories with many files in the file system. The only reason I 
see is (what David said) that direntries are stored (in RAM) in the 
lists, and it is relatively slow operation to find/insert/delete 
direntries from the list. Instead, nodes are stored in RB-tees. So, in 
case of slow CPU, there may be significant difference.

David, If you mean inode checkpoints saying "snapshots", I don't think 
they help to increase the mount time (But! They will increase the first 
directory access delay!). If you mean what Ferenc is implementing, this 
will increase the mount speed, but file system with "large" directories 
will be mounted slower anyway ( IMHO, of course :-) ).


David Woodhouse wrote:
> On Tue, 2004-10-19 at 20:16 +0200, Jan Vestby wrote:
> 
>>I have seen startup time is quite nonlinear with respect to the number of 
>>files per directory. You could try to restrict the size of directories.
> 
> 
> Hm. Should we be using rbtrees for dirents too? Or will the snapshots
> fix this anyway?

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

      reply	other threads:[~2004-10-20  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18 16:28 JFFS2 behaviour when large number of files are created David Ho
2004-10-19 13:22 ` Pantelis Antoniou
2004-10-19 18:16 ` Jan Vestby
2004-10-19 18:42   ` David Woodhouse
2004-10-20  9:23     ` Artem B. Bityuckiy [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=41762E91.8060204@yandex.ru \
    --to=abityuckiy@yandex.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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