From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Christopher Li <chrisl@gnuchina.org>,
"Stephen C. Tweedie" <sct@redhat.com>,
Alexander Viro <viro@math.psu.edu>, DervishD <raul@pleyades.net>,
Linux-kernel <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: Shrinking ext3 directories
Date: Thu, 20 Jun 2002 00:54:52 +0100 [thread overview]
Message-ID: <20020620005452.M5119@redhat.com> (raw)
In-Reply-To: <20020619234340.A24016@redhat.com>; from sct@redhat.com on Wed, Jun 19, 2002 at 11:43:40PM +0100
Hi,
On Wed, Jun 19, 2002 at 11:43:40PM +0100, Stephen C. Tweedie wrote:
> Well, it has some interesting properties, such as the hash function
> being a constant:
>
> + return 80; /* FIXME: for test only */
>
> which I assume was an artifact of some testing Christopher was doing.
> :)
>
> I'm checking out a proper hash function at the moment.
Done, checked into ext3 cvs (features-branch again.)
Deleting and recreating 100,000 files with this kernel:
[root@spock test0]# time xargs rm -f < /root/flist.100000
real 0m14.305s
user 0m0.750s
sys 0m5.430s
[root@spock test0]# time xargs touch < /root/flist.100000
real 0m16.244s
user 0m0.530s
sys 0m6.660s
that's an average of 160usec per create, 140usec per delete elapsed
time, and 66/54usec respectively system time.
I assume the elapsed time is greater only because we're starting to
wrap the journal due to the large amount of metadata being touched
(we're touching a lot of inodes doing the above, which I could avoid
by making hard links instead of new files.) Certainly, limiting the
test to 10,000 files lets it run at 100% cpu.
--Stephen
next prev parent reply other threads:[~2002-06-19 23:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 16:08 Shrinking ext3 directories DervishD
2002-06-18 16:10 ` Austin Gonyou
2002-06-18 16:39 ` Andreas Dilger
2002-06-18 19:39 ` DervishD
2002-06-18 19:34 ` DervishD
2002-06-18 16:21 ` Padraig Brady
2002-06-18 16:54 ` David Lang
2002-06-18 19:35 ` DervishD
2002-06-18 21:50 ` Stephen C. Tweedie
2002-06-18 22:18 ` Alexander Viro
2002-06-19 9:38 ` DervishD
2002-06-19 10:37 ` Stephen C. Tweedie
2002-06-19 17:03 ` [Ext2-devel] " Christopher Li
2002-06-19 20:10 ` Stephen C. Tweedie
2002-06-19 20:34 ` Stephen C. Tweedie
2002-06-19 20:13 ` Andrew Morton
2002-06-19 22:43 ` Stephen C. Tweedie
2002-06-19 23:54 ` Stephen C. Tweedie [this message]
2002-06-21 3:28 ` Daniel Phillips
2002-06-21 7:03 ` Helge Hafting
2002-06-21 14:02 ` Daniel Phillips
2002-06-24 7:12 ` Helge Hafting
2002-06-21 16:23 ` Daniel Phillips
2002-06-21 15:06 ` Stephen C. Tweedie
2002-07-04 4:48 ` Daniel Phillips
2002-07-04 14:15 ` jlnance
2002-07-05 2:11 ` Daniel Phillips
2002-06-22 5:53 ` Andreas Dilger
2002-06-22 20:59 ` Daniel Phillips
2002-06-23 0:01 ` Daniel Phillips
2002-06-23 7:57 ` Daniel Phillips
2002-06-19 22:49 ` Daniel Phillips
2002-06-20 0:24 ` Andreas Dilger
2002-06-20 9:34 ` Stephen C. Tweedie
2002-06-20 10:18 ` Andreas Dilger
2002-06-20 13:45 ` Daniel Phillips
2002-06-21 14:54 ` Ville Herva
2002-06-21 15:08 ` Stephen C. Tweedie
2002-06-21 15:38 ` Ville Herva
2002-06-21 16:15 ` Stephen C. Tweedie
2002-06-21 18:44 ` Ville Herva
2002-06-20 16:26 ` Bill Davidsen
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=20020620005452.M5119@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=chrisl@gnuchina.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@pleyades.net \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.