From: Paulo Marques <pmarques@grupopie.com>
To: sankarshana rao <san_wipro@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Inode question
Date: Tue, 27 Jul 2004 12:18:30 +0100 [thread overview]
Message-ID: <1090927110.11604.7.camel@pmarqueslinux> (raw)
In-Reply-To: <20040727012807.96145.qmail@web50901.mail.yahoo.com>
On Tue, 2004-07-27 at 02:28, sankarshana rao wrote:
> Thx for the inputs..
> I am trying this thing on Mips processor and creating
> 500 folders itself takes about 1.6 seconds. That's why
> I was wondering if using inodes would make it any
> faster..
> pls guide...
I really think the name lookup is not your bottleneck.
I did some more tests to check where the time to create a dir came from
and, as expected, it depends a lot on the filesystem.
Using ext3, creating 1000 dirs on my machine (P4 2.8GHz) takes about 100
ms. Using tmpfs, takes only 6 ms. Even a machine 20 times slower would
take at most 60ms to do the 500 lookups.
Both tests have to do the same lookup on the dentry cache and check for
duplicate names, etc.
So the real difference is the time *the filesystem* takes to create a
dir.
You're probably using JFFS2 or something like that, which is almost
synchronous (I don't know for sure if it is really synchronous), and
writes the updates to flash on every dir creation.
I hope this helps,
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
prev parent reply other threads:[~2004-07-27 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 18:39 Inode question sankarshana rao
2004-07-21 20:25 ` Dave Kleikamp
2004-07-21 20:46 ` sankarshana rao
2004-07-21 20:56 ` Dave Kleikamp
2004-07-21 21:09 ` Richard B. Johnson
2004-07-21 22:57 ` sankarshana rao
2004-07-22 12:36 ` Dave Kleikamp
2004-07-22 14:23 ` Paulo Marques
2004-07-27 1:28 ` sankarshana rao
2004-07-27 11:18 ` Paulo Marques [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=1090927110.11604.7.camel@pmarqueslinux \
--to=pmarques@grupopie.com \
--cc=linux-kernel@vger.kernel.org \
--cc=san_wipro@yahoo.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