From: erik quanstrom <quanstro@quanstro.net>
To: mirtchovski@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] Different representations of the same file/resource in a synthetic FS
Date: Tue, 9 Jun 2009 15:16:36 -0400 [thread overview]
Message-ID: <0ba7a2c75ada9aee91e80172ee7c3183@quanstro.net> (raw)
> still a hash. i'm not doing anything particularly clever for speed,
> and it shows in places. listing large directories is the slowest
> operation by far, as it would be for most cases where several thousand
> "stat" structures would have to be dynamically created for each entry
> in a directory. i'm not pre-generating anything however, so in daily
> use, where each client knows exactly where to go, i'm not seeing
> slowdowns.
thanks!
> not that i'm worried: we recently discovered a few misconfigured
> clusters around here (names withheld) that were using ldap and no
> local nameservice caching. each stat on those boxes would take 0.05 ms
> (instead of 0.005) to complete because it needed to contact a server
> for username lookup. the wait became unbearable above a number of
> thousands of files in a particular directory, so people finally
> started complaining after waiting for minutes for 'ls -l' to finish.
> things could be way worse, i guess :)
i suppose we could all be forced to reimplement vi for the
apollo landing computer.
- erik
next reply other threads:[~2009-06-09 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:16 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-09 19:41 erik quanstrom
[not found] <eed9f9e37182c89c3e8a9982844f9d0f@quanstro.net>
2009-06-09 19:31 ` andrey mirtchovski
2009-06-09 18:59 erik quanstrom
2009-06-09 18:15 Francisco J Ballesteros
2009-06-09 17:14 Roman V Shaposhnik
2009-06-09 17:27 ` andrey mirtchovski
2009-06-09 18:10 ` erik quanstrom
2009-06-09 19:01 ` andrey mirtchovski
2009-06-11 3:44 ` Roman V. Shaposhnik
2009-06-09 17:30 ` J.R. Mauro
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=0ba7a2c75ada9aee91e80172ee7c3183@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=mirtchovski@gmail.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;
as well as URLs for NNTP newsgroup(s).