From: Nigel Rantor <wiggly@wiggly.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Chris Wedgwood <cw@f00f.org>,
peter@chubb.wattle.id.au, viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: stat very inefficient
Date: Thu, 29 Jul 2004 12:42:18 +0100 [thread overview]
Message-ID: <4108E29A.5080609@wiggly.org> (raw)
In-Reply-To: <20040728171414.5de8da96.davem@redhat.com>
David S. Miller wrote:
> On Wed, 28 Jul 2004 17:08:37 -0700
> Chris Wedgwood <cw@f00f.org> wrote:
>
>
>>Just How bad is it for you? I just tested stat on my crapbox and for
>>a short path 1M stats takes 0.5s and for a longer path (30 bytes or
>>so) 2.8s.
>
>
> Run "time find . -type f" on the kernel tree, both before and
> after removing the third unnecessary copy. Many machines sit all
> day and stat files.
P2 350MHz 256Mb RAM circa 1998
bash$ time find . -type f
gives
real 0m16.142s
user 0m0.432s
sys 0m2.893s
I'd be interested to see what machine you have that takes all day.
N
next prev parent reply other threads:[~2004-07-29 11:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <233602095@toto.iv>
2004-07-28 22:33 ` stat very inefficient Peter Chubb
2004-07-28 22:45 ` David S. Miller
2004-07-29 0:08 ` Chris Wedgwood
2004-07-29 0:14 ` David S. Miller
2004-07-29 0:24 ` Chris Wedgwood
2004-07-29 0:29 ` viro
2004-07-29 7:26 ` Peter Chubb
2004-07-29 7:42 ` Andrew Morton
2004-07-29 8:49 ` Paul Jackson
2004-07-29 9:02 ` Andrew Morton
2004-07-29 9:17 ` Peter Chubb
2004-07-29 7:45 ` Ulrich Drepper
2004-07-29 11:42 ` Nigel Rantor [this message]
2004-07-29 1:07 ` Ulrich Drepper
2004-07-29 2:22 ` Paul Jackson
2004-07-29 4:10 ` Ulrich Drepper
2004-07-29 6:18 ` Paul Jackson
[not found] <2mN94-3MP-9@gated-at.bofh.it>
2004-07-28 10:16 ` Andi Kleen
2004-07-28 15:38 ` David S. Miller
2004-07-28 3:13 David S. Miller
2004-07-28 18:07 ` viro
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=4108E29A.5080609@wiggly.org \
--to=wiggly@wiggly.org \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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