From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Maximum files per Directory
Date: Wed, 2 May 2001 12:22:50 +0200 [thread overview]
Message-ID: <20010502122250.J3305@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <272800000.988750082@hades> <E14uhI2-0002NH-00@the-village.bc.nu> <9cnbs0$uk3$1@cesium.transmeta.com>
In-Reply-To: <9cnbs0$uk3$1@cesium.transmeta.com>; from hpa@zytor.com on Tue, May 01, 2001 at 03:03:44PM -0700
On Tue, May 01, 2001 at 03:03:44PM -0700, H. Peter Anvin wrote:
> > Bit of both. You exceeded the max link count, and your
> > performance would have been abominable too. cyrus should be
> > using heirarchies of directories for very large amounts of
> > stuff.
Right.
> But also showing, once again, that this particular scalability problem
> really is a headache for some people.
If you do ls on that directory as an admin, you'll see, what the
REAL cause of this headache is:
The application doing such stupid thing!
People (writing applications) building up such large directories
should be forced to read every entry of it aloud.
Then they'll learn[1] and the problem is solved.
Regards
Ingo Oeser
[1] If not, let them repeat until they do.
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-05-02 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 20:48 Andreas Rogge
2001-05-01 20:58 ` H. Peter Anvin
2001-05-01 22:57 ` Andreas Dilger
2001-05-04 13:49 ` Chris Mason
2001-05-04 19:15 ` Andreas Dilger
2001-05-04 20:08 ` Chris Mason
2001-05-05 13:49 ` Jamie Lokier
2001-05-05 16:16 ` Chris Mason
2001-05-01 21:02 ` Alan Cox
2001-05-01 22:03 ` H. Peter Anvin
2001-05-02 10:22 ` Ingo Oeser [this message]
2001-05-02 16:13 ` H. Peter Anvin
2001-05-02 13:33 ` Ketil Froyn
2001-05-02 9:21 ` Henning P. Schmiedehausen
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=20010502122250.J3305@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®