public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: akorolev <alexey.korolev@intel.com>
To: havasi@inf.u-szeged.hu
Cc: linux-mtd@lists.infradead.org
Subject: Centralized summary as a way to speed up "ls" time
Date: Tue, 10 Apr 2007 20:53:52 +0400	[thread overview]
Message-ID: <461BC120.2080507@intel.com> (raw)

Hello Ferenc,

While using JFFS2 on NAND devices with large size and many files I faced 
the problem of very slow "ls" performance.
On folder which contains ~40 files and ~80MB ls could take ~25sec!

I'm thinking of the way to resolve somehow this issue.
Reasons of the very slow performance are more or less clean - JFFS2 
scans NAND to fill jffs2_node_frag and jffs2_full_dnode structures.
After first call of ls on some dir this data will be filled and next 
call will work fast.
If we have few RAM cache may be released and next ls will take long.

The question I have will it be possible to extend a little bit 
functionality of Centralized Summary to story these nodes as well.
Do you see any technical issues here?

IMHO if it is possible it make sense, because it will load node info 
into RAM for the most used data. So for most used data we will have 
preloaded node info fast  "ls" just after mount.

Do you have any updates of CS? Is the last version of CS placed here 
www.inf.u-szeged.hu/jffs2/mount.php?

Thanks,
Alexey

             reply	other threads:[~2007-04-10 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 16:53 akorolev [this message]
2007-04-10 17:24 ` Centralized summary as a way to speed up "ls" time Artem Bityutskiy
2007-04-12 12:16 ` Ferenc Havasi

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=461BC120.2080507@intel.com \
    --to=alexey.korolev@intel.com \
    --cc=havasi@inf.u-szeged.hu \
    --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